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?
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.	No		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	VF-C Backlog
	Are all tasks associated with committed Sprint Backlog Stories been marked as "Done" in Jira?	Yes
Release Management	Have all issues pertaining to FOSS been addressed?	Yes
Release Management	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.
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?	No	(note: emsdriver include vesjavalibrary jar file)	Refer to CI Development Best Practices
	Is there any pending commit request older than 36 hours in Gerrit?	No
	Are all the Jenkins jobs successfully passed (verify + merge jobs)?	Yes	VF-C jenkins job
	Are all snapshot binaries available in Nexus?	Yes	VF-C binaries in Nexus
	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	All jobs pertaining to your project MUST pass VF-C jenkins job
	Is there a Docker images available for your project deliverable?	Yes	VF-C docker images list
	Has the project code successfully passed the Daily Build process?	Yes	VF-C jenkins job	Goal is to ensure the latest project commit has not broken the Integration Daily Build
Doc	Has the team created a documentation Template in ReadTheDocs?	Yes	VF-C documentation template	Documentation Team is using ReadTheDocs for documenting user facing documentation. ReadTheDcos shall be considered as a starting pint for someone new withn ONAP. The ReadTheDcos is the ONAP Documentation facade visible to users. Link to Template How to setup the template for my project?
Doc	Is the API documentation section poplulated?	Yes	VF-C API List	Ensure there is at least a direct link toward the API documentation which may be already existing in the wiki.