M4 Checklist - Code Freeze Milestone

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.

Usage

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?

Practice Area	Checkpoint	Yes/No	Evidences	How to?
Product Management	Have all JIRA Stories supporting the release use case been implemented?	Yes	Doc Project JIRA issues	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.	None		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 "Done" in Jira?	Yes	Doc Project JIRA issues
	Are all tasks associated with committed Sprint Backlog Stories been marked as "Done" in Jira?	Yes	Doc Project JIRA issues
Release Management	Have all issues pertaining to FOSS been addressed?	Yes
Release Management	Have all findings from previous milestones been addressed?	Yes		For M2 and M3 Milestones, ensure all findings have been closed.
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.
	Is there any binaries (jar, war, tar, gz, gzip, zip files) in Gerrit project repository?	N/A		Refer to CI Development Best Practices
	Is there any pending commit request older than 36 hours in Gerrit?	No	Doc Project Gerrit status
	Are all the Jenkins jobs successfully passed (verify + merge jobs)?	Yes	Doc Project - Jenkins jobs
	Are all snapshot binaries available in Nexus?	N/A	Provide 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	Doc Project - Jenkins jobs
	Is there a Docker images available for your project deliverable?	N/A	Provide link to Nexus repos
	Has the project code successfully passed the Daily Build process?	N/A		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	Doc Project Documentation	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 Templates How to setup the template for my project?
Doc	Is the API documentation section populated?	Yes	API Template	Ensure there is at least a direct link toward the API documentation which may be already existing in the wiki.