...
Info | ||
---|---|---|
| ||
|
Practice Area | Checkpoint | Yes/No | Evidences | How to? | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Product Management | Have all JIRA Stories supporting the release use case been implemented? | Yes |
| 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. |
| 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 |
| ||||||||||||
Are all tasks associated with committed Sprint Backlog Stories been marked as "Closed" in Jira? | Yes |
| ||||||||||||
Release Management | Have all issues pertaining to FOSS been addressed? | Yes | There were no issues raised for the project. | |||||||||||
Have all findings from previous milestones been addressed? | NA | 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 "Closed" in Jira? | No |
|
in progress
| |||||||||||
Has the project team reach the Automated Unit Test Code Coverage expectation? (Refer to artifacts available in Sonar) | Yes | optf/osdf: > 60% optf/has: > 50% |
For evidences, provide link(s) to Gerrit repos by providing the URL as shown in this example
https://sonar.onap.org/dashboard?id=org.onap.optf.has%3Aoptf-has https://sonar.onap.org/dashboard?id=org.onap.optf.osdf%3Aoptf-osdf |
Is there any binaries (jar, war, tar, gz, gzip, zip files) in Gerrit project repository? |
No | |||
Is there any pending commit request older than 36 hours in Gerrit? | No | ||
Provide the "% Achived" on the CII Best Practices program. |
100% on Passing badge | 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:
which is complaint with CVSS V2.0 rating. |
No | There are not identified security vulnerability for all repos | 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/optf/job/optf-has-master-conductor-merge-java/ https://jenkins.onap.org/view/optf/job/optf-osdf-master-osdf-merge-java/ | ||
Have all OOM Staging |
Healthcheck related to your project passed? | No* |
| |
Are all snapshot binaries available in Nexus-staging? |
Yes | OSDF: https://nexus.onap.org/content/repositories/snapshots/org/onap/optf/osdf/optf-osdf/1.2.1-SNAPSHOT/ | ||
Do you have a clear plan to implement the Independent Versioning and Release Process by RC0? | Yes | 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 | There are 37 functional test cases for the existing repo. https://jenkins.onap.org/view/optf/job/optf-has-master-csit-has/ Tests for the new repo (CMSO) are being added by the team. | |
Is there a Docker images available for your project deliverable? |
Yes | https://nexus3.onap.org/repository/docker.snapshot/v2/onap/optf-has/manifests/1.2.1-SNAPSHOT-latest https://nexus3.onap.org/repository/docker.snapshot/v2/onap/optf-osdf/manifests/1.2.1-SNAPSHOT-latest | ||
Has the project code successfully passed the Daily Build process? | Yes | https://jenkins.onap.org/view/optf/job/optf-osdf-master-osdf-release-version-java-daily/ https://jenkins.onap.org/view/optf/job/optf-has-master-conductor-release-version-java-daily/ | 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/optf/has.git/docs/index.html https://onap.readthedocs.io/en/latest/submodules/optf/osdf.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. | |
Is the API documentation section populated? |
Yes | https://onap.readthedocs.io/en/latest/submodules/optf/osdf.git/docs/sections/offeredapis.html https://onap.readthedocs.io/en/latest/submodules/optf/has.git/docs/sections/offeredapis.html | Ensure there is at least a direct link toward the API documentation which may be already existing in the wiki. |