The following items are expected to be completed for the project to Pass the M3 API Freeze Milestone.
- 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?|
|Security||Has the Release Security/Vulnerability table been updated in the protected Security Vulnerabilities wiki space?||Yes||Table in in the protected Security Vulnerabilities wiki space corresponds to the latest NexusIQ scan||PTL reviews the NexusIQ scans for their project repos and fills out the vulnerability review table|
|Has the project committed to enabling transport level encryption on all interfaces and the option to turn it off?||Yes||Requirements and test cases for transport layer encryption have been created for all interfaces not currently supporting encryption.|
|Has the project documented all open port information?||Yes||Update OOM NodePort List|
|Has the project provided the communication policy to OOM and Integration?||Yes||Recommended Protocols|
|Do you have a plan to address by M4 the Critical and High vulnerabilities in the third party libraries used within your project?||Yes|
|Architecture||Has the Project team reviewed the APIs with the Architecture Committee (ARC)?||Yes|
Architecture walk through to understand how each project contributes on Release Use Case. ARC to organize the walk through.
|Is there a plan to address the findings the API review?||Yes||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?||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?
|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.||Yes|
|Release Management||Are committed Sprint Backlog Stories been marked as "Closed" in Jira board?||Yes.|
|Are all tasks associated with Sprint Backlog Stories been marked as "Closed" in Jira?||Yes|
|Have all findings from previous milestones been addressed?||Yes|
|Development||Is there any pending commit request older than 36 Business hours in Gerrit?||No||status:open project:music label:verified -is:draft -label:Code-Review=-1 AND -label:Code-Review=-2 AND is:mergeable age:1week|
Gerrit Query: status:open label:verified -is:draft -label:Code-Review=-1 AND -label:Code-Review=-2 AND is:mergeable age:1week
|Has the project team reach the Automated Unit Test Code Coverage expectation? (Refer to artifacts available in Sonar)||Yes|
Are all the Jenkins jobs successfully passed ( Merge-Jobs)?
|Are all binaries available in Nexus?||Yes|
|Integration and Testing|
Have 50% of System Integration Testing Use Cases been implemented successfully in Jenkins?
It should include at least 1 CSIT that will be run on
Lab-xxx-OOM-Daily Jenkins Job
CSIT completed (18/18 tests)
OOM based CSIT is targeted for M4. Still awaiting instructions
|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|
Has the project passed the Integration Sanity Tests?
Integration sanity tests in Dublin Release cover:
No test failure reported on http://onapci.org/grafana/d/8cGRqBOmz/daily-summary?orgId=1
No Integration Blocking Issue with no workaround: Dublin Release Integration Test Blocking Issues
|Modeling||Has the Project team provided links to Data Models (e.g, JSON, YANG, Swagger, etc.) for all Shared Information (e.g., APIs, API Payload, Shared Design Model)?||Yes||https://gerrit.onap.org/r/#/c/31127/2/swagger.json||It is a non-blocking item for M3 - The Modeling team is gathering information|