RC0:
| Practice Area | Checkpoint | Yes/No | Evidences | How to? |
|---|---|---|---|---|
| Product Management | Are all tasks associated with the release been marked as "Done" in Jira? | Yes | ||
| Have all findings from previous milestones been addressed? | Yes | |||
| Development | Have 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 | |||
| 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 Stagingrepo? There should be at least ONE version of each artifacts available in Nexus Release or Nexus Staging repo. | Yes | https://nexus3.onap.org/#browse/search=keyword%3DMusic:912d0fe7b8192392e1887a3511a7adba | Refer to Independent Versioning and Release Process for procedure | |
| Integration and Testing | Have 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 | https://nexus3.onap.org/#browse/search=keyword%3DMusic:912d0fe7b8192392e1887a3511a7adba | ||
| Has the project code successfully passed the Daily Build process? | Yes | https://jenkins.onap.org/view/music/job/music-distributed-kv-store-master-docker-golang-shell-daily/ | Goal is to ensure the latest project commit has not broken the Integration Daily Build | |
| Has the OOM deployment passed? | N/A | Since MUSIC for cassablanca release is only used by Portal and OOF, the helm charts are under development. | ||
| Has the Heat deployment passed? | N/A | Since MUSIC for cassablanca release is only used by Portal and OOF, the Heat template is under development. | ||
| Documentation | For RC0, for project delivering binaries, has the team populated and validated all the sections of either the Platform Component or SDK template? | N/A | ||
For RC1, has the team addressed any issue (recorded in JIRA) provided by the Documentation team? | N/A | |||
For RC2, for project delivering binaries, has the team populated and validated all the sections of the Release Notestemplate? | N/A | |||
| For RC2, has the Documentation Team provided the final approval for your project documentation? | N/A |
RC1:
| Practice Area | Checkpoint | Yes/No | Evidences | How to? |
|---|---|---|---|---|
| Product Management | Are all tasks associated with the release been marked as "Done" in Jira? | Yes | ||
| Have all findings from previous milestones been addressed? | Yes | |||
| Development | Have 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 | |||
| 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. | Yes | https://nexus3.onap.org/#browse/search=keyword%3DMusic:912d0fe7b8192392e1887a3511a7adba | Refer to Independent Versioning and Release Process for procedure | |
| Integration and Testing | Have all CSIT Use Cases (created by each project team) passed? | https://jenkins.onap.org/view/music/ | ||
| Is there a Docker images available for each repository? | https://nexus3.onap.org/#browse/search=keyword%3DMusic:912d0fe7b8192392e1887a3511a7adba | |||
| Has the project code successfully passed the Daily Build process? | Goal is to ensure the latest project commit has not broken the Integration Daily Build | |||
| Has the OOM deployment passed? | In Progress | |||
| Has the Heat deployment passed? | In Progress | |||
| Documentation | For RC0, for project delivering binaries, has the team populated and validated all the sections of either the Platform Component or SDK template? | In Progress | 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? | In Progress | |||
For RC2, for project delivering binaries, has the team populated and validated all the sections of the Release Notestemplate? | In Progress | |||
| For RC2, has the Documentation Team provided the final approval for your project documentation? |
RC0:
| Practice Area | Checkpoint | Yes/No | Evidences | How to? |
|---|---|---|---|---|
| Product Management | Are all tasks associated with the release been marked as "Done" in Jira? | Yes | ||
| Have all findings from previous milestones been addressed? | Yes | |||
| Development | Have 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 | |||
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. | Yes | https://nexus.onap.org/content/repositories/staging/org/onap/music/ | Refer to Independent Versioning and Release Process for procedure | |
| Integration and Testing | Have all CSIT Use Cases (created by each project team) passed? | Yes | ||
| Is there a Docker images available for each repository? | 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 | ||
| Has the OOM deployment passed? | NA |
| Has the Heat deployment passed? | NA |
| 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 |
: https:// |
Section templates for music are referenced from these in the documentation index
httpM4:
| 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 | Integration with OOM will be done next release. https://jira.onap.org/projects/MUSIC/issues/MUSIC-60?filter=allopenissues | 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? | Yes | ||
| Have all findings from previous milestones been addressed? | Yes | 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 | |||
| For both (a) and (b), have all high priority non-Project Licenses been either removed or escalated as likely exception requests? | Yes | |||
| 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 | Look for "go test -cover ./..." in the Jenkins logs to see coverage information. | 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/distributed-kv-store | ||
| Provide the "% Achived" on the CII Best Practices program. | NA | Nexus-IQ not supported for Golang. | 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. | NA | Nexus-IQ not supported for Golang. | 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/ Waiting for a fix to get merged: https://gerrit.onap.org/r/#/c/39247/ | ||
| Are all snapshot binaries available in Nexus? | Yes | |||
| 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 | ||
| Is there a Docker images available for your project deliverable? | Yes | https://nexus3.onap.org/#browse/search=keyword%3Dmusic:912d0fe7b8192392e1887a3511a7adba | ||
| 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? | Yes | Submodule commited in doc repo: https://git.onap.org/doc/tree/docs/submodules/music Docs present in project repo: https://git.onap.org/music/distributed-kv-store/tree/docs | Documentation Team is using Readthedocs for documenting user facing documentation. ReadTheDocs shall be considered as a starting point for someone new within ONAP. The ReadTheDocs is the ONAP Documentation facade visible to users. |
| Is the API documentation section populated? | Yes | Link to Swagger file: https://git.onap.org/music/distributed-kv-store/tree/swagger.yaml Link to API documentation for rendering in Readthedocs: https://git.onap.org/music/distributed-kv-store/tree/docs/offeredapis.rst Link to HTML render of Swagger API: https://wiki.onap.org/pages/viewpage.action?pageId=16010913&preview=/16010913/28379517/swagger%20API.html#DistributedKVStore(MUSICsub-project)-APIReference:: | Ensure there is at least a direct link toward the API documentation which may be already existing in the wiki. |
...
| Practice Area | Checkpoint | Yes/No | Evidence - Comment | How to? |
|---|---|---|---|---|
| Product Management | Are all provisional APIs interface (stub) been defined (at beta-quality level)? | Yes | https://git.onap.org/music/distributed-kv-store/tree/swagger.yaml | |
| Is there a final list of externally consumable APIs available? | Yes | https://git.onap.org/music/distributed-kv-store/tree/swagger.yaml | ||
For all completed Sprints, have Sprint Backlog Stories been marked as "Done" in Jira? | Yes | |||
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 | https://jenkins.onap.org/view/music/job/music-distributed-kv-store-master-verify-golang/ | ||
| 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 | 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 | |||
| (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 | |||
| 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 | |||
Have all API projects dependencies been captured? | Yes | https://git.onap.org/music/distributed-kv-store/tree/swagger.yaml | ||
| Development | For new projects approved for this release, have all defined repositories source code been placed into Gerrit? | Yes | https://gerrit.onap.org/r/gitweb?p=music/distributed-kv-store.git;a=summary | 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) | Yes | Automated coverage number not supported in Sonar for Golang, but it is documented on the project wiki: Distributed KV Store (MUSIC sub-project)#project)-TestingandIntegration: | ||
| 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)? | Yes | https://jenkins.onap.org/view/music/job/music-distributed-kv-store-master-verify-golang/ | ||
| Are all snapshot binaries available in Nexus? | In Progress | A ticket was submitted on this at the help desk to get info on how to upload binaries of Golang projects to nexus. | ||
| Integration and Testing | Have functional test cases been documented in wiki? | Yes | https://wikilf-onap.onapatlassian.orgnet/wiki/pages/viewpage.action?pageId=16010913#DistributedKVStore16258247#DistributedKVStore(MUSICsub-project)-TestingandIntegration: | |
| Have you implemented in Jenkins at least 1 functional test case for each of the project repository? | Yes | https://git.onap.org/music/distributed-kv-store/tree/src/dkv/api/configHandlers_test.go | 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-distributed-kv-store-master-merge-golang/ | 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 | Document API reference and have usage documentation. https://git.onap.org/music/distributed-kv-store/tree/README.md |
...