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.
| Info | ||
|---|---|---|
| ||
|
| Practice Area | Checkpoint | Yes/No | Evidences | How to? |
|---|---|---|---|---|
| Architecture | Has the Project team reviewed the APIs with the Architecture Committee (ARC)? | Planned For Tuesday 31 | Documen: | 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? |
| NA | 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 | 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 | 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 Design document & swagger are available | |
| Release Management | Are committed Sprint Backlog Stories been marked as "Done" in Jira board? |
| YES | All 6 stories are done | ||||||||||
| Are all tasks associated with Sprint Backlog Stories been marked as "Done" in Jira? | NA | ||||||||||
| Have all findings from previous milestones been addressed? | NA | Provide link to JIRA findings | |||||||||
| Development | Is there any pending commit request older than 36 Business hours in Gerrit? | NO | |||||||||
| Do you have a plan to address by M4 the Critical and High 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 | Sonar line coverage: 69% https://sonar.onap.org/dashboard?id=org.onap.externalapi-nbi%3Anbi-rest-services | ||
| Are all binaries available in Nexus? |
Docker in nexus | ||
| Integration and Testing | Have 50 % of System Integration Testing Use Cases been implemented successfully in Jenkins? |
| NA | No integration test | ||
| Has the project code successfully passed the Daily Build process? | YES | Both java an docker daily build | Goal is to ensure the latest project commit has not broken the Integration Daily Build |
https://wiki.onap.org/display/DW/calendars