VVP M4 Deliverable for Code Freeze Milestone Checklist
- Steven wright
The following items are expected to be completed for the project to Pass the M4 Code Freeze Milestone.
M4 Release Code Freeze Milestone overview is available in wiki.
Practice Area | Checkpoint | Yes/No | Evidences | How to? |
|---|---|---|---|---|
Product Management | Have all JIRA Stories supporting the release use case been implemented? | Yes | By using the macro JIRA Issue/Filter, provide a link to JIRA in listing the stories that are implemented in Beijing Release. (Example Getting issues... for AAI project, edit for your project) | For each JIRA story that are implemented in Beijing Release, you have to setup in JIRA the JIRA fixVersion="Beijing Release" No new functionality in Beijing release |
List the Stories that will not be implemented in this current Release. | Yes | By using the macro JIRA Issue/Filter, provide a link to JIRA in listing the stories that are NOT implemented in Beijing Release. Getting issues... | For each JIRA story that will not be implemented in Amsterdam Release, you have to setup in JIRA the JIRA fixVersion="Beijing Release" No new functionality in Beijing release | |
Are committed Sprint Backlog Stories been coded and marked as "Done" in Jira? | Yes | Provide Link to Project backlog | ||
Are all tasks associated with committed Sprint Backlog Stories been marked as "Done" in Jira? | Yes | Provide Link to Project backlog | ||
Release Management | Have all issues pertaining to FOSS been addressed? | Yes | Extend existing waivers from Amsterdam to Beijing release. | |
Have all findings from previous milestones been addressed? | Yes | List previous milestone issues that have not been addressed. | For M2 and M3 Milestones, ensure all findings have been closed. | |
Has the Project Team reviewed and understood the most recent license scan reports from the LF, for both (a) licenses within the codebase and (b) licenses for third-party build time dependencies? | Yes | |||
For both (a) and (b), have all high priority non-Project Licenses been either removed or escalated as likely exception requests? | Yes | No new exception requests renew waiver for external dependencies from Amsterdam release | ||
Development | Are all Defects of priority Highest and High in status "Done" in Jira? | Yes | Provide link to JIRA issue (type bug) of priority Highest and High. | |
Has the project team reach the Automated Unit Test Code Coverage expectation? (Refer to artifacts available in Sonar) | Yes | Goal: 50% for Incubation project in Beijing SONAR testing applies only to python repos:
| For evidences, provide link(s) to Gerrit repos by providing the URL as shown in this example
test-engine repo is not a run time component of vvp - this is a stand alone test framework to validate the rest of the VVP components. | |
Is there any binaries (jar, war, tar, gz, gzip, zip files) in Gerrit project repository? | no | |||
Is there any pending commit request older than 36 hours in Gerrit? | No | |||
Provide the "% Achived" on the CII Best Practices program. | 70% | Provide link to your project CII Best Practices page. | As documented in CII Badging Program, teams have to fill out CII Best Practices Helpdesk Ticket for creation of SONAR reports #53550 and CLM #53552 still outstanding | |
Is there any Critical level security vulnerabilities older than 60 days old in the third party libraries used within your project unaddressed? Nexus-IQ classifies level as the following:
which is complaint with CVSS V2.0 rating. | No | In the case critical known vulnerability are still showing in the report, fill out the Security/Vulnerability Threat Template - Beijing, Casablanca, Dublin in your project. | Ensure 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 (verify + merge jobs)? | Yes | Provide link to "Merge job" as evidence in Jenkins project tab | ||
Are all snapshot binaries available in Nexus? | yes | |||
Do you have a clear plan to implement the Independent Versioning and Release Process by RC0? | Yes | No upstream ONAP projects | Contact the upstream teams to make sure they will release their artifacts (in Nexus Release repo) so you can build by depending on these released artifacts by RC0. | |
Integration and Testing | Have 100% of Continuous System Integration Testing (CSIT) Use Cases been implemented successfully in Jenkins? | NA | VVP has run as a standalone project in the past. no direct data flow between VVP and other platform components. current E-E use cases do not include vvp No CSIT tests for VVP in place. - no HEAT build ofr VVP - native kubernetes - depends on OOM for build | |
Is there a Docker images available for your project deliverable? | Yes | Provide link to Nexus repos | ||
Has the project code successfully passed the Daily Build process? | yes | Link to Jenkins | Goal is to ensure the latest project commit has not VVP has run as a standalone project in the past. no direct data flow between VVP and other platform components. current E-E use cases do not include vvp No CSIT tests for VVP in place. broken the Integration Daily Build | |
Doc | Has the team created a docs folder and Development and Release Notes documentation templates in Readthedocs? | No | Add a link to your project documentation in ReadTheDocs. | Documentation Team is using Readthedocs for documenting user facing documentation. ReadTheDcos shall be considered as a starting point for someone new within ONAP. The ReadTheDocs is the ONAP Documentation facade visible to users. |
Is the API documentation section populated? | NA | No external APIs | Ensure there is at least a direct link toward the API documentation which may be already existing in the wiki. |