...
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.
| Practice Area | Checkpoint | Yes/No | Evidences | How to? |
|---|---|---|---|---|
| Architecture | Has the Project team reviewed the APIs with the Architecture Committee (ARC)? | N/A | VNFRQTS does not create APIs | 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 | VNFRQTS does not create APIs | 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? | N/A | VNFRQTS does not create APIs | 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? | No If Yes, please a link to the evidence of these changes. | Clarification:PNF functionality starts to be introduced in Beijing release for management functions only. Additional aspects expected in future releases. | 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. | N/A | VNFRQTS does not create APIs | ||
| Release Management | Are committed Sprint Backlog Stories been marked as "Done" in Jira board? | YES | Provide Link to Project backlog | |
| Are all tasks associated with Sprint Backlog Stories been marked as "Done" in Jira? | YES | |||
| Have all findings from previous milestones been addressed? | YESProvide link to JIRA findings | release planning project status: M1 pass M2 pass | ||
| Development | Has the project team reach the Automated Unit Test Code Coverage expectation? (Refer to artifacts available in Sonar) | N/A | VNFRQTS does not generate code | Guidance on Code Coverage and Static Code Analysis |
| Is there any pending commit request older than 36 Business hours in Gerrit? | NO | gerrit open issues: | ||
Do you have a plan to address by M4 the Critical vulnerabilities in the third party libraries used within your project? | N/A | VNFRQTS does not generate code | Ensure by M4 the Nexus-IQ report from “Jenkins CLM” shows 0 critical security vulnerability. Open the Nexus-IQ report for the details on each repo. | |
| Are all the Jenkins jobs successfully passed ( Merge-Jobs)? | Yes | Gerrit Merged issues: | ||
| Are all binaries available in Nexus? | Yes | onap.readthedocs.io | VNFRQTS produces documentation rather than code binaries. All documentation is published on onap.readthedocs.io rather than Nexus | |
| Integration and Testing | Have 50 % of System Integration Testing Use Cases been implemented successfully in Jenkins? | N/A | VNFRQTS does not generate code | |
| Has the project code successfully passed the Daily Build process? | N/A | NFRQTS does not generate code for daily build. it does publish dpocumentation to onap.readthedocs.io | Goal is to ensure the latest project commit has not broken the Integration Daily Build |