| 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 |
| 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? | NoYesIn | communication with Steve/Gildas regarding this. Steve Winsolow's scan cleared music:
| ||||||||||
| 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 "Done" in Jira? | Yes |
| ||||||||||
| Has the project team reach the Automated Unit Test Code Coverage expectation? (Refer to artifacts available in Sonar) | Yes | OSDF: optf.osdf%3Aoptf-osdf HAS: https://sonar.onap.org/dashboard?id=org.onap.optf.has%3Aoptf-has | 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 | https://gerrit.onap.org/r/#/q/project:music | |||||||||||
| 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:
which is complaint with CVSS V2.0 rating. No | Yes | We have two critical issues: https://nexus-iq.wl.linuxfoundation.org/assets/index.html#/reports/optf-hasmusic/ebdd5bafe94246cd8603240a7bec92b0 However, please note that we are a pure Python project, and there was a concern on these reports being inaccurate for Pythoncecf4c77af8646d882e29cd6968eecba We have documented the issues here: 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 | https://jenkins.onap.org/view/music/ | |||||||||||
| Are all snapshot binaries available in Nexus? | Yes | content/repositories/snapshots/org/onap/optf/ | |||||||||||
| 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? | All jobs pertaining to your project MUST passYes | |||||||||||
| Is there a Docker images available for your project deliverable? | Yes | https://nexus3.onap.org/#browse/repositorysearch/docker=attributes.docker.snapshot/v2/onap/optf-has/manifests/latestimageName%3Dmusic | |||||||||||
| 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?Add a link to your project documentation in ReadTheDocs. | 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 | Documentation Team is using Readthedocs for documenting user facing documentation. ReadTheDcos 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 Templates http://onap.readthedocs.io/en/latest/guides/onap-developer/how-to-use-docs/include-documentation.html#templates-and-examples | |||||||||
| Is the API documentation section populated?Link to evidence | 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. http://docs.onap.org/en/latest/submodules/music.git/docs/offeredapis.html | Ensure there is at least a direct link toward the API documentation which may be already existing in the wiki. |
Page Comparison
General
Content
Integrations