Integration R2 M3 API Freeze Milestone Checklist
- Gary Wu
Practice Area | Checkpoint | Yes/No | Evidences | How to? |
|---|---|---|---|---|
Architecture | Has the Project team reviewed the APIs with the Architecture Committee (ARC)? | N/A | 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 | Link to plan | 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 | 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? | N/A | If Yes, please a link to the evidence of these changes. | 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 | |||
Release Management | Are committed Sprint Backlog Stories been marked as "Done" in Jira board? | No | https://jira.onap.org/secure/RapidBoard.jspa?rapidView=81&view=planning | |
Are all tasks associated with Sprint Backlog Stories been marked as "Done" in Jira? | Yes | |||
Have all findings from previous milestones been addressed? | Yes | https://jira.onap.org/secure/RapidBoard.jspa?rapidView=81&view=planning | ||
Development | Has the project team reach the Automated Unit Test Code Coverage expectation? (Refer to artifacts available in Sonar) | N/A | Goal: 50% for Incubation project in Beijing | |
Is there any pending commit request older than 36 Business hours in Gerrit? | Yes | |||
Do you have a plan to address by M4 the Critical vulnerabilities in the third party libraries used within your project? | Yes | 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 | https://jenkins.onap.org/view/integration/ https://jenkins.onap.org/view/demo/ | ||
Are all binaries available in Nexus? | Yes | https://nexus.onap.org/content/repositories/snapshots/org/onap/oparent/ | ||
Integration and Testing | Have 50 % of System Integration Testing Use Cases been implemented successfully in Jenkins? | N/A | Provide link to evidence | |
Has the project code successfully passed the Daily Build process? | Yes | Goal is to ensure the latest project commit has not broken the Integration Daily Build |