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)? | Yes | 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 | No findings | 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 | 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 | Traffic Migration DistrubuteTraffic meeting notes | 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 | APPC LCM API Guide | |||||||||||||||||||||||||
| Release Management | Are committed Sprint Backlog Stories been marked as "Done" in Jira board? | Yes | APPC Board | ||||||||||||||||||||||||
| Are all tasks associated with Sprint Backlog Stories been marked as "Done" in Jira? | Yes | APPC Board | |||||||||||||||||||||||||
| Have all findings from previous milestones been addressed? | N/A | No previous findings | |||||||||||||||||||||||||
| Development | Has the project team reach the Automated Unit Test Code Coverage expectation? (Refer to artifacts available in Sonar) | Yes | Goal: 50% for Casablanca Release | Guidance on Code Coverage and Static Code Analysis | |||||||||||||||||||||||
| 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 vulnerabilities in the third party libraries used within your project? | Yes | Below are the JIRAs to track the Nexus-IQ issue for APPC's three repos
| 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 | Provide link to evidence | |||||||||||||||||||||||||
| Are all binaries available in Nexus? | Yes | Provide link to evidence | |||||||||||||||||||||||||
| Integration and Testing | Have 50 % of System Integration Testing Use Cases been implemented successfully in Jenkins? | Yes | https://jenkins.onap.org/view/CSIT/job/appc-master-verify-csit-healthcheck/ | Some CSIT tests are still failing Plan: APPC needs the ODL Oxygen SR3 docker to be built, Upgrading to ODL Oxygen is APPC's highest priority goal in R3. We knew the cause why some cases are failing in APPC CSIT. We tracked on https://jira.onap.org/browse/APPC-1141 . but will be fixing after ODL Oxygen SR3 docker build is done. | |||||||||||||||||||||||
| Has the project code successfully passed the Daily Build process? | No | two jenkins are failing randomly. appc-deployment-{master|beijing}-docker-java-daily due to nexus3 is not stableYes | Goal is to ensure the latest project commit has not broken the Integration Daily Build |