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? | |||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| Security | Has the Release Security/Vulnerability table been updated in the protected Security Vulnerabilities wiki space? | logging n/a pomba 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? | logging n/a pomba 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. see bidirectional comments Logging Dublin M3 Architecture Review | ||||||||
| 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? | no | 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 | Provide Link to Project backlog | https://jira.onap.org/secure/RapidBoard.jspa?rapidView=143&useStoredSettings=true | |||||||
| Are all tasks associated with Sprint Backlog Stories been marked as "Closed" in Jira? | yes | ||||||||||
| Have all findings from previous milestones been addressed? | yex | Provide link to JIRA findings | |||||||||
| Development | Is there any pending commit request older than 36 Business hours in Gerrit? | yes | Gerrit Query: status:open label:verified -is:draft -label:Code-Review=-1 AND -label:Code-Review=-2 AND is:mergeable age:1week There are ongoing work items that will span multiple weeks - reviews are committed as we go - not just at the end | ||||||||
| Has the project team reach the Automated Unit Test Code Coverage expectation? (Refer to artifacts available in Sonar) | yes | Goal: 55% for Incubation project in the current release | Guidance on Code Coverage and Static Code Analysis around 80% | ||||||||
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? It should include at least 1 CSIT that will be run on Lab-xxx-OOM-Daily Jenkins Job | yes | Provide link to evidence | ||||||||
| 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 every 6 hours | |||||||||
Has the project passed the Integration Sanity Tests? | n/a | 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)? | n/a | It is a non-blocking item for M3 - The Modelling team is gathering information |
...