...
| Info | ||
|---|---|---|
| ||
|
| Practice Area | Checkpoint | Yes/No | Evidences | How to? |
|---|---|---|---|---|
| Product Management | Have all JIRA Stories supporting the release use case been implemented? | No |
By using the macro JIRA Issue/Filter, provide a link to JIRA in listing the stories that are implemented in Amsterdam Release. (Example
| Jira | ||||||||
|---|---|---|---|---|---|---|---|---|
|
https://jira.onap.org/projects/OOM/versions/10341 202/253 stories done | 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. |
| Jira | ||||||||
|---|---|---|---|---|---|---|---|---|
|
| We intend to finish during the integration period | https://jira.onap.org/projects/OOM/versions/10341 30/253 in progress, 21/253 to do Do to late requirement changes and code drops from the project teams some stories will be completed during the integration period | 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? |
| Not all stories are done | https://jira.onap.org/secure/RapidBoard.jspa?projectKey=OOM&rapidView=41&view=planning | |||
| Are all tasks associated with committed Sprint Backlog Stories been marked as "Done" in Jira? | Not all tasks are done | |||
| Release Management | Have all issues pertaining to FOSS been addressed? | Yes | ||
| Have all findings from previous milestones been addressed? | Yes | List previous milestone issues that have not been addressed. | 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? |
| No | Many more defects are expected during the integration phase | ||
| Has the project team reach the Automated Unit Test Code Coverage expectation? (Refer to artifacts available in Sonar) | N/A | Goal: 50% for Incubation project in Beijing | 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? | https://gerrit.onap.org/r/#/q/project:oom+and+status:open+and+age:36h | ||
| Provide the "% Achived" on the CII Best Practices program. |
| 100% | https://bestpractices.coreinfrastructure.org/en/projects/1631 | 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 | In the case critical known vulnerability are still showing in the report, fill out the Security/Vulnerability Threat Template - Beijing, Casablanca, Dublin in your project. | 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)? | N/A | Provide link to "Merge job" as evidence in Jenkins project tab | ||
| Are all snapshot binaries available in Nexus? | N/A | Provide link to evidence | ||
| Do you have a clear plan to implement the Independent Versioning and Release Process by RC0? | ? | As a stretch goal for Beijing we're trying to setup an automated build environment but working with the LF has been slow. We'll implement this with versioning once the LF has setup a repository for us. | 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? | N/A | All jobs pertaining to your project MUST pass | |
| Is there a Docker images available for your project deliverable? | N/A | Provide link to Nexus repos | ||
| Has the project code successfully passed the Daily Build process? | N/A | 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 | http://onap.readthedocs.io/en/latest/submodules/oom.git/docs/oom_project_description.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? |
| N/A | Ensure there is at least a direct link toward the API documentation which may be already existing in the wiki. |