Tracking Milestones

RC0:

Practice Area	Checkpoint	Yes/No	Evidences	How to?

Practice Area	Checkpoint	Yes/No	Evidences	How to?
Product Management	Are all tasks associated with the release been marked as "Done" in Jira?	Yes
	Have all findings from previous milestones been addressed?	Yes
Development	Have all Defects of priority Highest and High been in status "Done" in Jira?	Yes
	Are all JIRA issues used as a reference in a commit in status "Done" in Jira?	Yes
	Is there any pending commit related to Highest and High priority issues older than 36 hours in Gerrit? In case there are messages going back and forth between authors and reviewers, it is acceptable to be above 36 hours.	No
	Are all the Jenkins jobs successfully passed (verify + merge jobs)?	Yes	https://jenkins.onap.org/view/music/
	Has the team delivered all their release artifacts in Nexus Release or Nexus Stagingrepo? There should be at least ONE version of each artifacts available in Nexus Release or Nexus Staging repo.	Yes	https://nexus3.onap.org/#browse/search=keyword%3DMusic:912d0fe7b8192392e1887a3511a7adba	Refer to Independent Versioning and Release Process for procedure
Integration and Testing	Have all CSIT Use Cases (created by each project team) passed?	Yes	https://jenkins.onap.org/view/music/
	Is there a Docker images available for each repository?	Yes	https://nexus3.onap.org/#browse/search=keyword%3DMusic:912d0fe7b8192392e1887a3511a7adba
	Has the project code successfully passed the Daily Build process?	Yes	https://jenkins.onap.org/view/music/job/music-distributed-kv-store-master-docker-golang-shell-daily/	Goal is to ensure the latest project commit has not broken the Integration Daily Build
	Has the OOM deployment passed?	N/A	Since MUSIC for cassablanca release is only used by Portal and OOF, the helm charts are under development.
	Has the Heat deployment passed?	N/A	Since MUSIC for cassablanca release is only used by Portal and OOF, the Heat template is under development.
Documentation	For RC0, for project delivering binaries, has the team populated and validated all the sections of either the Platform Component or SDK template?	N/A
	For RC1, has the team addressed any issue (recorded in JIRA) provided by the Documentation team?	N/A
	For RC2, for project delivering binaries, has the team populated and validated all the sections of the Release Notestemplate?	N/A
	For RC2, has the Documentation Team provided the final approval for your project documentation?	N/A

RC1:

Practice Area	Checkpoint	Yes/No	Evidences	How to?

Practice Area	Checkpoint	Yes/No	Evidences	How to?
Product Management	Are all tasks associated with the release been marked as "Done" in Jira?	Yes
	Have all findings from previous milestones been addressed?	Yes
Development	Have all Defects of priority Highest and High been in status "Done" in Jira?	Yes
	Are all JIRA issues used as a reference in a commit in status "Done" in Jira?	Yes
	Is there any pending commit related to Highest and High priority issues older than 36 hours in Gerrit? In case there are messages going back and forth between authors and reviewers, it is acceptable to be above 36 hours.	No
	Are all the Jenkins jobs successfully passed (verify + merge jobs)?	Yes	https://jenkins.onap.org/view/music/
	Has the team delivered all their release artifacts in Nexus Release or Nexus Staging repo? There should be at least ONE version of each artifacts available in Nexus Release or Nexus Staging repo.	Yes	https://nexus3.onap.org/#browse/search=keyword%3DMusic:912d0fe7b8192392e1887a3511a7adba	Refer to Independent Versioning and Release Process for procedure
Integration and Testing	Have all CSIT Use Cases (created by each project team) passed?		https://jenkins.onap.org/view/music/
	Is there a Docker images available for each repository?		https://nexus3.onap.org/#browse/search=keyword%3DMusic:912d0fe7b8192392e1887a3511a7adba
	Has the project code successfully passed the Daily Build process?			Goal is to ensure the latest project commit has not broken the Integration Daily Build
	Has the OOM deployment passed?		In Progress
	Has the Heat deployment passed?		In Progress
Documentation	For RC0, for project delivering binaries, has the team populated and validated all the sections of either the Platform Component or SDK template?		In Progress	Most teams have already created the high level file structures in readthedocs, and populated some actual documentation. However, the remaining sections of the appropriate teamplate must be completed. Platform: A&AI, APP-C, CLAMP, CLI, DCAE, DMaaP, Holmes, MSB, OOM, Policy, Portal, SDN-C SDC, SO, UseCase UI, VFC, VID SDKs: AAF, CCSDK, External API Framework, Multi VIM/Cloud, VNFSDK
	For RC1, has the team addressed any issue (recorded in JIRA) provided by the Documentation team?		In Progress
	For RC2, for project delivering binaries, has the team populated and validated all the sections of the Release Notestemplate?		In Progress
	For RC2, has the Documentation Team provided the final approval for your project documentation?

RC0:

Practice Area	Checkpoint	Yes/No	Evidences	How to?

Practice Area

Checkpoint

Yes/No

Evidences

How to?

Product Management

Are all tasks associated with the release been marked as "Done" in Jira?

Yes

Have all findings from previous milestones been addressed?

Yes

Development

Have all Defects of priority Highest and High been in status "Done" in Jira?

Yes

Are all JIRA issues used as a reference in a commit in status "Done" in Jira?

Yes

We believe our team has marked tasks as Done when the commit is made - not sure how to verify this though.

Is there any pending commit related to Highest and High priority issues older than 36 hours in Gerrit? In case there are messages going back and forth between authors and reviewers, it is acceptable to be above 36 hours.

No

Are all the Jenkins jobs successfully passed (verify + merge jobs)?

Yes

https://jenkins.onap.org/view/music/

Has the team delivered all their release artifacts in Nexus Release or Nexus Staging repo?

There should be at least ONE version of each artifacts available in Nexus Release or Nexus Staging repo.

Yes

https://nexus.onap.org/content/repositories/staging/org/onap/music/

Refer to Independent Versioning and Release Process for procedure

Integration and Testing

Have all CSIT Use Cases (created by each project team) passed?

Yes

https://jenkins.onap.org/view/music/

Is there a Docker images available for each repository?

Yes

https://nexus3.onap.org/#browse/search=keyword%3Dmusic:912d0fe7b8192392e1887a3511a7adba

Has the project code successfully passed the Daily Build process?

Yes

https://jenkins.onap.org/view/music/

Goal is to ensure the latest project commit has not broken the Integration Daily Build

Has the OOM deployment passed?

NA

Has the Heat deployment passed?

NA

Documentation

For RC0, for project delivering binaries, has the team populated and validated all the sections of either the Platform Component or SDK template?

Yes

music.git docs folder exists with templates as shown here: https://git.onap.org/doc/tree/docs/submodules/music

https://git.onap.org/music/distributed-kv-store/tree/docs

Most teams have already created the high level file structures in readthedocs, and populated some actual documentation. However, the remaining sections of the appropriate teamplate must be completed.

Platform: A&AI, APP-C, CLAMP, CLI, DCAE, DMaaP, Holmes, MSB, OOM, Policy, Portal, SDN-C SDC, SO, UseCase UI, VFC, VID

SDKs: AAF, CCSDK, External API Framework, Multi VIM/Cloud, VNFSDK

For RC1, has the team addressed any issue (recorded in JIRA) provided by the Documentation team?

NA

For RC2, for project delivering binaries, has the team populated and validated all the sections of the Release Notes template?

NA

For RC2, has the Documentation Team provided the final approval for your project documentation?

NA

M4:

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?	NA since we were not present in the Amsterdam release		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	Integration with OOM will be done next release. https://jira.onap.org/projects/MUSIC/issues/MUSIC-60?filter=allopenissues	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	https://jira.onap.org/secure/RapidBoard.jspa?rapidView=119&view=planning
	Are all tasks associated with committed Sprint Backlog Stories been marked as "Done" in Jira?	Yes	https://jira.onap.org/secure/RapidBoard.jspa?rapidView=119&view=planning
Release Management	Have all issues pertaining to FOSS been addressed?	Yes	eet
	Have all findings from previous milestones been addressed?	Yes		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?	Yes	https://jira.onap.org/projects/MUSIC/issues
	Has the project team reach the Automated Unit Test Code Coverage expectation? (Refer to artifacts available in Sonar)	Yes	Look for "go test -cover ./..." in the Jenkins logs to see coverage information. https://jenkins.onap.org/view/music/job/music-distributed-kv-store-master-merge-golang/lastBuild/consoleText	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	https://gerrit.onap.org/r/#/q/project:music/distributed-kv-store
	Provide the "% Achived" on the CII Best Practices program.	NA	Nexus-IQ not supported for Golang.	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.	NA	Nexus-IQ not supported for Golang.	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	https://jenkins.onap.org/view/music/ Waiting for a fix to get merged: https://gerrit.onap.org/r/#/c/39247/
	Are all snapshot binaries available in Nexus?	Yes	https://nexus3.onap.org/#browse/search=keyword%3Dmusic:912d0fe7b8192392e1887a3511a7adba