Practice AreaCheckpointYes/NoEvidencesHow to?
Product ManagementAre all tasks associated with the release been marked as "Done" in Jira?Yes

T Key Summary Assignee Reporter P Status Resolution Created Updated Due
Loading...
Refresh



Have all findings from previous milestones been addressed?Yes

DevelopmentHave 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.

Yeshttps://nexus.onap.org/content/repositories/staging/org/onap/music/Refer to Independent Versioning and Release Process for procedure
Integration and TestingHave 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
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

Being used internally within OOF and Portal, so no separate OOM deployment.


Has the Heat deployment passed?NABeing used internally within OOF and Portal, so no separate OOM deployment.
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.

http://docs.onap.org/en/latest/guides/onap-developer/developing/index.html#music

Section templates for music are referenced from these in the documentation index

http://docs.onap.org/en/latest/search.html?q=music&check_keywords=yes&area=default


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?

Yes

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

Yes

http://onap.readthedocs.io/en/latest/submodules/music.git/docs/release-notes.html


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