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.

By using the macro JIRA Issue/Filter, provide a link to JIRA in listing the stories that are implemented in Amsterdam Release. (Example Getting issues... for AAI project, edit for your project)

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.

NA since we were not present in the Amsterdam release.

By using the macro JIRA Issue/Filter, provide a link to JIRA in listing the stories that are NOT implemented in Amsterdam Release. (Example Getting issues... for AAI project, edit for your project)

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 "Closed" 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 "Closed" 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

Steve Winsolow's scan cleared music: onap-2018-03-codebase.xlsx

Have all findings from previous milestones been addressed?

Yes

https://jira.onap.org/secure/RapidBoard.jspa?rapidView=119&view=planning

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

No license issues remain: https://nexus-iq.wl.linuxfoundation.org/assets/index.html#/reports/music/e024135f292f44cfbf452de32b60f1e0

For both (a) and (b), have all high priority non-Project Licenses been either removed or escalated as likely exception requests?

Yes

No license issues remain: https://nexus-iq.wl.linuxfoundation.org/assets/index.html#/reports/music/e024135f292f44cfbf452de32b60f1e0

Development

Are all Defects of priority Highest and High in status "Closed" 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

https://sonar.onap.org/dashboard?id=org.onap.music%3AMUSIC

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

Provide the "% Achived" on the CII Best Practices program.

100%

https://bestpractices.coreinfrastructure.org/en/projects/1722

As documented in CII Badging Program, teams have to fill out CII Best Practices

Is there any Critical and Severe 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.

Yes

We have two critical issues:

https://nexus-iq.wl.linuxfoundation.org/assets/index.html#/reports/music/cecf4c77af8646d882e29cd6968eecba

We have documented the issues here:

Casablanca MUSIC Security/Vulnerability Report

Obtained 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

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

Have all OOM Staging Healtcheck related to your project passed?

Yes

Are all snapshot binaries available in Nexus-staging?

Yes

https://nexus.onap.org/#nexus-search;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 Testing

Have 100% of Continuous System Integration Testing (CSIT) Use Cases been implemented successfully in Jenkins?

Yes

https://nexus.onap.org/#nexus-search;quick~music

Is there a Docker images available for your project deliverable?

Yes

https://nexus3.onap.org/#browse/search/docker=attributes.docker.imageName%3Dmusic

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

Doc

Has the team created a docs folder and Development and Release Notes documentation templates in Readthedocs?

Yes

https://onap.readthedocs.io/en/latest/submodules/music.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 http://onap.readthedocs.io/en/latest/guides/onap-developer/how-to-use-docs/include-documentation.html#templates-and-examples

How to setup the template for my project?

Is the API documentation section populated?

Yes

https://gerrit.onap.org/r/#/c/31127/2/swagger.json

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

Browser not supported