| Practice Area | Checkpoint | Yes/No | Evidence - Comment | How to? | |
|---|---|---|---|---|---|
| Product Management | Are all provisional APIs interface (stub) been defined (at beta-quality level)? | YesOur code already has support for swagger. We are working with Gildas to figure out how to expose this. | https://gerrit.onap.org/r/#/c/31127/2/swagger.json | ||
| Is there a final list of externally consumable APIs available? | YesOur code already has support for swagger. We are working with Gildas to figure out how to expose this. | https://gerrit.onap.org/r/#/c/31127/2/swagger.json | |||
For all completed Sprints, have Sprint Backlog Stories been marked as "Done" in Jira? | Provide Link to Project backlog | Difference between a Product and Sprint BacklogYes | |||
Are all tasks associated with the completed Sprint Backlog Stories been marked as "Done" in Jira? | Yes | https://jira.onap.org/secure/RapidBoard.jspa?rapidView=113&view=detail&selectedIssue=MUSIC-9&quickFilter=273 | |||
| If applicable to your project, has your team been able to clear the project' blockers? If not provide status on the plan to close the blocker(s). | Yes | ||||
| What new features or changes to existing features in this project scope need to be communicated to VNF Providers? List the changes in the Evidence tab. | NA | ||||
| If yes to the previous question, have these been communicated to the VNF Requirements project? | NA | ||||
| Release Management | Have all source code files been updated with License Apache 2 header? | Yes | Had the initial approval from Steve Winslow and followed all his suggestions. However, the CLM job is still pending: https://jenkins.onap.org/view/music/job/music-maven-clm-master/. Working with Linux foundation fix this. | Specific rules and instruction are available in ONAP wiki. | |
| Has the year format in copyright header of all source code files been updated? (Rules for new files created in 2018 and existing files modified in 2018 are different) | NA | Guidance on year format | |||
| In case source code can't be edited, has a "License.txt" file been placed at the root directory for which the license is applicable? | NA | Guidance for source code file that can't be edited | |||
| (a) Has the Project Team added appropriate license and copyright notices to all ONAP source code and documentation files, where possible for the particular file format? | Yes | Had the initial approval from Steve Winslow and followed all his suggestions. However, the CLM job is still pending: https://jenkins.onap.org/view/music/job/music-maven-clm-master/. Working with Linux foundation fix this. | |||
| (b) 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 | Had the initial approval from Steve Winslow and followed all his suggestions. However, the CLM job is still pending: https://jenkins.onap.org/view/music/job/music-maven-clm-master/. Working with Linux foundation fix this. | |||
| For both (a) and (b) questions, have all high priority non-Project Licenses been either removed, planned for removal before code freeze, or escalated as likely exception requests? | Yes | Had the initial approval from Steve Winslow and followed all his suggestions. However, the CLM job is still pending: https://jenkins.onap.org/view/music/job/music-maven-clm-master/. Working with Linux foundation fix this. | |||
Have all API projects dependencies been captured? | Provide link to the "API Incoming Dependency" section within your project M1 Release Planning deliverable. | The source of information for the API dependency is the "API Incoming Dependency" of the M1 Release Planning deliverable. Please update the source accordingly, and let The Release Manager aware of the changes. | Yes | https://gerrit.onap.org/r/#/c/31127/2/swagger.json | |
| Development | For new projects approved for this release, have all defined repositories source code been placed into Gerrit?Provide link to evidence | Yes | For evidences, provide link(s) to Gerrit repos by providing the URL as shown in this example | ||
| Has the project team reach the Automated Unit Test Code Coverage expectation? (Refer to artifacts available in Sonar)Goal: 50% for Incubation project in Beijing | In progress. | We now are showing up in SONAR but there are still errors that need to be resolved: https://jenkins.onap.org/view/01-all-sonar/job/music-sonar/ While we believe we have the requisite coverage, we are working with LF for to resolve this. | |||
| Is there any binaries (jar, war, tar, gz, gzip, zip files) in Gerrit project repository? | No | Refer to CI Development Best Practices | |||
| Could you ensure that all proprietary trademarks, logos, product names, company name, etc. have been removed? All ONAP deliverables must comply with this rule and be agnostic of any proprietary symbols. | Yes | ||||
| Is there any pending commit request older than 36 business hours in Gerrit? | No | ||||
| Have all the Jenkins jobs successfully passed (Merge-Jobs)?Provide link as evidence to Jenkins project tab | Yes | https://jenkins.onap.org/view/music/job/music-master-merge-java/ | |||
| Are all snapshot binaries available in Nexus?Provide link to evidence in Nexus project folder | Yes | https://nexus.onap.org/#nexus-search;quick~music | |||
| Integration and Testing | Have functional test cases been documented in wiki?Provide link to evidence | Yes | https://lf-onap.atlassian.net/wiki/download/attachments/16262103/ONAP-Music-Functional-Test-Cases.pdf?version=1&modificationDate=1518222158055&api=v2 | ||
| Have you implemented in Jenkins at least 1 functional test case for each of the project repository?As an evidence, provide a link to Jenkins (CSIT Jobs) that shows a sample test case implemented (1 job for each repo). | In progress | As an example (provided by Integration Team) | |||
| Has the project code successfully passed the Build process? | Yes | https://jenkins.onap.org/view/music/job/music-master-verify-java/ | Goal is to ensure your project latest commits have not broken the build. | ||
| Documentation | Has the team identified and outlined the set of documentations to be delivered in this Release? | Yes |
Page Comparison
General
Content
Integrations