...
| Practice Area | Checkpoint | Yes/No | Evidences | How to? | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Product Management | Have all JIRA Stories supporting the release use case been implemented? | Yes |
| |||||||||
| List the Stories that will not be implemented in this current Release. | N/A | |||||||||||
| Are committed Sprint Backlog Stories been coded and marked as "Closed" in Jira? | Yes | https://jira.onap.org/secure/RapidBoard.jspa?projectKey=EXTAPI&rapidView=43&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?projectKey=EXTAPI&rapidView=43&view=planning | ||||||||||
| Release Management | Have all issues pertaining to FOSS been addressed? | Yes ( same as Beijing ) | ||||||||||
| Have all findings from previous milestones been addressed? | N/A | 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? | Yes |
| |||||||||
| Has the project team reach the Automated Unit Test Code Coverage expectation? (Refer to artifacts available in Sonar) | Yes | 76% https://sonar.onap.org/dashboard?id=org.onap.externalapi-nbi%3Anbi-rest-services | https://gerrit.onap.org/r/a/externalapi/nbi | |||||||||
| 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 | |||||||||||
| Provide the "% Achived" on the CII Best Practices program. | 95% | https://bestpractices.coreinfrastructure.org/en/projects/1771 | ||||||||||
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. | Yes ( 2 ) | 2 critical security vulnerability reported here | ||||||||||
| Are all the Jenkins jobs successfully passed (verify + merge jobs)? | Yes | https://jenkins.onap.org/view/externalapi/job/externalapi-nbi-master-merge-java/ | ||||||||||
| Have all OOM Staging Healtcheck related to your project passed? | No ( in progress ) | Fix waiting for merge here https://gerrit.onap.org/r/#/c/68129/In Progress | ||||||||||
| Are all snapshot binaries available in Nexus-staging? | Yes | https://nexus.onap.org/content/repositories/snapshots/org/onap/externalapi-nbi/nbi-rest-services/ | ||||||||||
| Do you have a clear plan to implement the Independent Versioning and Release Process by RC0? | N/A | NBI does not relies on binaries dependencies but on API through MSB gateway | ||||||||||
| Integration and Testing | Have 100% of Continuous System Integration Testing (CSIT) Use Cases been implemented successfully in Jenkins? | No ( in progress ) | Fix waiting for merge here https://gerrit.onap.org/r/#/c/68129/In Progress | |||||||||
| Is there a Docker images available for your project deliverable? | Yes | https://nexus3.onap.org/#browse/search=keyword%3Dnbi%20AND%20version%3D3.0.0:912d0fe7b819239203ac4d4072b644e1 | ||||||||||
| Has the project code successfully passed the Daily Build process? | Yes | https://jenkins.onap.org/view/externalapi/job/externalapi-nbi-master-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/externalapi/nbi.git/docs/offeredapis/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 | All links are provided from the ReadTheDoc page, to swagger, html and even plantuml diagram https://onap.readthedocs.io/en/latest/submodules/externalapi/nbi.git/docs/offeredapis/index.html | Ensure there is at least a direct link toward the API documentation which may be already existing in the wiki. |