View Source

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.

Use the "Copy" option (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 filled out in the protected Security Vulnerabilities wiki space?	Yes	Table in in the protected Security Vulnerabilities wiki space corresponds to the latest NexusIQ scan; all NexusIQ finding are marked as false positive or exploitable with the supporting analysis.	PTL reviews the NexusIQ scans for their project repos and fills out the vulnerability review table
	Are all Defects of priority Highest and High in status "Closed" in Jira? (this includes the Jira for Critical and Severe NexusIQ findings)	Yes	All Jira tickets for vulnerability elimination are complete.	Complete Jira tickets
	Did the project achieve the enablement of transport level encryption on all interfaces and the option of disabling transport level encryption?	Yes	All interfaces are exposed over TLS and the secure protocol can optionally be turned off
	Do all containers run as a non-root user and is documentation available for those containers that must run as root in order to enable ONAP features?	WIP	ONAP project containers do not run as the root ID with the exception of containers supporting ONAP features that require the container to run as the root ID. Project containers that run as the root ID have documented this in the release notes along with the functionality that requires the container to run as the root ID.	https://wiki.onap.org/display/DW/Best+Practices
	Provide the "% Achieved" on the CII Best Practices program.	100%	https://bestpractices.coreinfrastructure.org/zh-CN/projects/1540	As documented in CII Badging Program, teams have to fill out CII Best Practices
Product Management	Have all JIRA Stories supporting the release use case been implemented?	Yes		For each JIRA story that are implemented in Amsterdam Release, you have to setup in JIRA the JIRA fixVersion="Amsterdam Release"
	List the Stories that will not be implemented in this current Release.	Yes		For each JIRA story that will not be implemented in Amsterdam Release, you have to setup in JIRA the JIRA fixVersion="Beijing Release"
	Are committed Sprint Backlog Stories been coded and marked as "Closed" in Jira?	Yes	4 issues
	Are all tasks associated with committed Sprint Backlog Stories been marked as "Closed" in Jira?	Yes	CLI issues
Release Management	Have all issues pertaining to FOSS been addressed?	Yes
	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
Development	Are all Defects of priority Highest and High in status "Closed" 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	For evidences, provide link(s) to Gerrit repos by providing the URL as shown in this example Example
	Is there any binaries (jar, war, tar, gz, gzip, zip files) in Gerrit project repository?	No		Refer to CI Development Best Practices
	Is there any pending commit request older than 36 hours in Gerrit?	No
	Provide the "% Achived" on the CII Best Practices program.	100	Provide link to your project CII Best Practices page.	As documented in CII Badging Program, teams have to fill out CII Best Practices
	Is there any Critical and Severe 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: Critical is level 7 to 10 Severe is level 4 to 6 Moderate is level 1 to 3 which is complaint with CVSS V2.0 rating.	Yes	Nexus IQ report Documentation	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	Jenkins CLI Tab
	Have all OOM Staging Healtcheck related to your project passed?	Yes
	Are all snapshot binaries available in Nexus-staging?	Yes	link to evidence
	Do you have a clear plan to implement the Independent Versioning and Release Process by RC0?	Yes		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?	Yes	Jenkins CLI Tab
	Is there a Docker images available for your project deliverable?	Yes	Nexus 3 Docker repo
	Has the project code successfully passed the Daily Build process?	Yes	Jenkins CLI Tab	Goal is to ensure the latest project commit has not broken the Integration Daily Build
Doc	Has the team created a docs folder and Development and Release Notes documentation templates in Readthedocs?	Yes	Release Note link CLI ReadtheDocs link	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. Link to http://onap.readthedocs.io/en/latest/guides/onap-developer/how-to-use-docs/include-documentation.html#templates-and-examples How to setup the template for my project?
Doc	Is the API documentation section populated?	Yes	Documentation	Ensure there is at least a direct link toward the API documentation which may be already existing in the wiki.