The following items are expected to be completed for the project to Pass the M3 API Freeze Milestone.
M3 Release Architecture Milestone overview is available in wiki.
Usage
- Use the "Copy" and "Move" options (available under the ..., top right of this page) to duplicate this template into your project wiki.
- Fill out the Yes/No column
- Provide link to evidence (when necessary)
| Practice Area | Checkpoint | Yes/No | Evidences | How to? |
|---|---|---|---|---|
| Architecture | Has the Project team reviewed the APIs with the Architecture Committee (ARC)? | Yes | ONAPARC-23 - Getting issue details... STATUS | Architecture walkthrough to understand how each project contributes on Release Use Case. ARC to organize the walkthrough. |
| Is there a plan to address the findings the API review? | N/A | no issues | The plan could be as simple as a Jira issue to track the implementation of findings or a documented plan within the wiki. | |
| Does the team clearly understand that no changes in the API definition is allowed without formal TSC review and approval? | Yes | NA | In the case some changes are necessary, bring the request to the TSC for review and approval. | |
Is there any changes in the scope, functionalities, deliverable, dependency, resources, API, repositories since M1 milestone? | Yes | SDC will query VNF SDK and pull VNFs from the marketplace. Originally, we considered pushing to SDC. | Critical point to understand is that change is inevitable, and that right timing and clear communication to the community will ease the process of accepting changes. | |
| Provide link to the API Documentation. | yes | API Documentation | ||
| Release Management | Are committed Sprint Backlog Stories been marked as "Done" in Jira board? | Yes | Sprint 2 | |
| Are all tasks associated with Sprint Backlog Stories been marked as "Done" in Jira? | yes | Sprint 2 | ||
| Have all findings from previous milestones been addressed? | Yes | in Sprint 2 | ||
| Development | Has the project team reach the Automated Unit Test Code Coverage expectation? (Refer to artifacts available in Sonar) | Yes | Goal: 30-50% for Incubation project | Guidance on Code Coverage and Static Code Analysis |
| Is there any pending commit request older than 36 Business hours in Gerrit? | No | |||
| Are all the Jenkins jobs successfully passed ( Merge-Jobs)? | Yes | VNFSDK Jenkins Job | ||
| Are all binaries available in Nexus? | Yes | VNFSDK Nexus Repo | ||
| Integration and Testing | Have 50 % of System Integration Testing Use Cases been implemented successfully in Jenkins? | in Progress | Provide link to evidence. https://gerrit.onap.org/r/#/c/6643/ Some test cases are already written but integrating with jenkins and other docker scripts is pending. Building the integration framework and test cases may need more time, as we are now focused on integration with SDC. We will complete 100% integration testing by Code freeze. | |
| Has the project code successfully passed the Daily Build process? | Yes | https://jenkins.onap.org/view/vnfsdk/job/vnfsdk-refrepo-master-release-version-java-daily/ | Goal is to ensure the latest project commit has not broken the Integration Daily Build |