The following items are expected to be completed for the project to Pass the M3 API Freeze Milestone.
| Practice Area | Checkpoint | Yes/No | Evidences | How to? |
|---|
| Architecture
| Has the Project team reviewed the APIs with the Architecture Committee (ARC)? | No | No new APIs. No changes to existing 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? |
Link to plan| N/A |
| 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| By design. | In the case some changes are necessary, bring the request to the TSC for review and approval. |
Is Are there any changes in the scope, functionalities, deliverable, dependency, resources, API, repositories since M1 milestone? |
If Yes, please a link to the evidence of these changes | No | By design. | 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 | EELF, Logging providers like SLF4J, Elastic Search, and ONAP Application Logging Guidelines v1.1. |
|
| Release Management | Are committed Sprint Backlog Stories been marked as "Done" in Jira board? |
Provide Link to | Yes | Project backlog |
|
| Are all tasks associated with Sprint Backlog Stories been marked as "Done" in Jira? | ??? | Where used. Granular stories. |
|
| Have all findings from previous milestones been addressed? |
Provide link to JIRA findings| ??? |
|
|
| Development | Has the project team reach the Automated Unit Test Code Coverage expectation? (Refer to artifacts available in Sonar) |
Goal: 30-50% for Incubation projectProvide link to evidence| Yes, but really N/A | Configuration, documentation, and bugfixes across the ONAP codebase. |
|
| Are all binaries available in Nexus? |
Provide link to evidence| Yes, but really N/A | As above. |
|
Integration and Testing
| Have 50 % of System Integration Testing Use Cases been implemented successfully in Jenkins? |
Provide link to evidence | N/A | As above. |
|
| Has the project code successfully passed the Daily Build process? | N/A | As above. | Goal is to ensure the latest project commit has not broken the Integration Daily Build |