[vnfrqts] M3 Deliverables for API Freeze Milestone Checklist Template
- Steven wright
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? | YES | VNFRQTS <> Documentation Project Workflow VNFRQTS <> Integration Project Workflow | Focus on creating VNF Requirements as prototype RFP text for release 1. Amsterdam release deliverables are VNF guidelines and VNF Requirements available at onap.readthedocs.io other deliverables delayed to future releases | |
Release Management | Are committed Sprint Backlog Stories been marked as "Done" in Jira board? | YES | ||
Are all tasks associated with Sprint Backlog Stories been marked as "Done" in Jira? | YES | |||
Have all findings from previous milestones been addressed? | YES | Provide link to JIRA findings | No blockers from previous milestonee | |
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 Goal: 30-50% for Incubation project |
Is there any pending commit request older than 36 Business hours in Gerrit? | NO | gerrit open issues: | ||
Are all the Jenkins jobs successfully passed ( Merge-Jobs)? | YES | Gerrit Merged issues: | ||
Are all binaries available in Nexus? | YES | 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 | Provide link to evidence |
Have you reviewed all the Test Case with Integration Team? | N/A | VNFRQTS does not generate code | Schedule a meeting with Integration Team to review the deliverable. | |
Has the project code successfully passed the Daily Build process? | N/A | VNFRQTS 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 | |