Copy of Portal R3 M4 for Code Freeze Milestone Checklist

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?	In-Progress	Getting 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.	Yes	PORTAL-151 - Getting issue details... STATUS	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	Link to Project backlog
	Are all tasks associated with committed Sprint Backlog Stories been marked as "Done" in Jira?	Yes	Getting 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 "Done" in Jira?	IN-PROGRESS	Getting issues... Team is working on the ETAs and planning close them in next week.
	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 Dublin portal line coverage is greater than 50% - sonar link portal-sdk line coverage is greater than 50% - sonar link	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.	Yes		As documented in CII Badging Program, teams have to fill out CII Best Practices
	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: 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.	IN-PROGRESS	Portal Platform Security/Vulnerability Threats	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	Portal-SDK artifacts version 2.4.0 are released. - https://nexus.onap.org/#nexus-search;quick~portal-sdk
	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 Two verify csit jobs are very old, they are not needed. Team is working on removing them.
	Is there a Docker images available for your project deliverable?	Yes	We use "latest" version for docker images for integration testing.
	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
Doc	Has the team created a docs folder and Development and Release Notes documentation templates in Readthedocs?	In-Progress	Add a link to your project documentation in ReadTheDocs. http://onap.readthedocs.io/en/latest/submodules/portal.git/docs/index.html	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	http://onap.readthedocs.io/en/latest/submodules/portal.git/docs/platform/offeredapis.html	Ensure there is at least a direct link toward the API documentation which may be already existing in the wiki.