Practice AreaCheckpointYes/NoEvidencesHow to?
Product ManagementHave 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

MUSIC will be run as a service in the next release. In this release it will be used internally by ONAP Portal and ONAP HAS.

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
Are all tasks associated with committed Sprint Backlog Stories been marked as "Done" in Jira?Yes
Release ManagementHave all issues pertaining to FOSS been addressed?Yes

Steve Winsolow's scan cleared music:

Have all findings from previous milestones been addressed?Yes 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?

YesNo license issues remain:
For both (a) and (b), have all high priority non-Project Licenses been either removed or escalated as likely exception requests?YesNo license issues remain:
DevelopmentAre all Defects of priority Highest and High in status "Done" in Jira?Yes
Has the project team reach the Automated Unit Test Code Coverage expectation? (Refer to artifacts available in Sonar)Yes

For evidences, provide link(s) to Gerrit repos by providing the URL as shown in this 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.100% on the passing badge.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.


We have two critical issues:

We have documented the issues here:

MUSIC Security/Vulnerability

In communication with LF to get TSC exception since these are necessary libraries.

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
Are all snapshot binaries available in Nexus?Yes;quick~music

Do you have a clear plan to implement the Independent Versioning and Release Process by RC0?NA
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 TestingHave 100% of Continuous System Integration Testing (CSIT) Use Cases been implemented successfully in Jenkins?Yes;quick~music

Is there a Docker images available for your project deliverable?Yes

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 
DocHas the team created a docs folder and Development and Release Notes documentation templates in Readthedocs?Yes

music.git docs folder exists with templates as shown here.

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

ReadTheDocs shall be considered as a starting point for someone new within ONAP.

The ReadTheDocs is the ONAP Documentation facade visible to users.

Link to

How to setup the template for my project?

Is the API documentation section populated?Yes

The offered APIs section is provided and API documentation is generated by Sphinx swaggerv2doc from a swagger.json file provided in the music.git repo.

Ensure there is at least a direct link toward the API documentation which may be already existing in the wiki.