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.
Usage
- Use the "Copy" and "Move" options (available under the ..., top right of this page) to duplicate this template into your project wiki.
- Fill out the Yes/No column
- Provide link to evidence (when necessary)
| Practice Area | Checkpoint | Yes/No | Evidences | How to? |
|---|---|---|---|---|
| Architecture | Has the Project team reviewed the APIs with the Architecture Committee (ARC)? | Y | ONAPARC-104 - Getting issue details... STATUS | 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 | N/A | Responded to all questions raised during the review. No leftover issues to address from teh API review | |
| Does the team clearly understand that no changes in the API definition is allowed without formal TSC review and approval? | Y | 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? | Y | We will descope flink due to resource availability change. We will add PNF Registration Handler microservice for supporting PNF registration function of the 5G use case. | 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. | https://git.onap.org/dcaegen2/collectors/ves/plain/swagger_vescollector.yaml https://git.onap.org/dcaegen2/platform/deployment-handler/plain/deployment-handler-API.yaml https://git.onap.org/dcaegen2/platform/configbinding/plain/config_binding_service/swagger/swagger.yaml https://git.onap.org/dcaegen2/platform/inventory-api/plain/swagger_inventory.yaml | |||
| Release Management | Are committed Sprint Backlog Stories been marked as "Done" in Jira board? | Provide Link to Project backlog | ||
| Are all tasks associated with Sprint Backlog Stories been marked as "Done" in Jira? | ||||
| 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) | N | Goal: 50% for Incubation project in Beijing | Guidance on Code Coverage and Static Code Analysis |
| Is there any pending commit request older than 36 Business hours in Gerrit? | N | |||
Do you have a plan to address by M4 the Critical vulnerabilities in the third party libraries used within your project? | Y | The remaining security vulnerabilities concentrate on 2 external dependencies. We will try to upgrade to newer revisions that do not have | 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)? | Y* | Provide link to evidence | ||
| Are all binaries available in Nexus? | Y | Provide link to evidence | ||
| Integration and Testing | Have 50 % of System Integration Testing Use Cases been implemented successfully in Jenkins? | Provide link to evidence | ||
| Has the project code successfully passed the Daily Build process? | Y | Goal is to ensure the latest project commit has not broken the Integration Daily Build |