...
| Practice Area | Checkpoint | Yes/No | Evidences | How to? | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Product Management | Have all JIRA Stories supporting the release use case been implemented? | By using the macro JIRA Issue/Filter, provide a link to JIRA in listing the stories that are implemented in Amsterdam Release. (Example
| CLAMP was not involved in specific Beijing committed use case, but focused on Maturity improvements. All of the committed Maturity improvements have been delivered | 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. | By using the macro JIRA Issue/Filter, provide a link to JIRA in listing the stories that are NOT implemented in Amsterdam Release. (Example
| Yes | All committed stories are implemented, only remaining ones are about documentation that we plan to complete before Beijing 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 "Done" in Jira?Provide Link to Project backlog | Yes | JIRA Backlog for Beijing Release | ||||||||||||||
| Are all tasks associated with committed Sprint Backlog Stories been marked as "Done" in Jira? | Yes | |||||||||||||||
| Release Management | Have all issues pertaining to FOSS been addressed? | Yes | ||||||||||||||
| Have all findings from previous milestones been addressed?List previous milestone issues that have not been addressed | Yes | No Specific findings. | 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 | Nexus IQ report | ||||||||||||||
| Development | Are all Defects of priority Highest and High in status "Done" in Jira?Provide link to JIRA issue (type bug) of priority Highest and High. | Yes |
| |||||||||||||
| Has the project team reach the Automated Unit Test Code Coverage expectation? (Refer to artifacts available in Sonar) | Yes | Goal: 50% for Incubation project in Beijing is achieved : sonar link | 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 | |||||||||||||||
| Provide the "% Achived" on the CII Best Practices program.Provide link to your project | 98% | CLAMP CII Best Practices page. The only item not passed is the fix of severe and high security issues of which only the severe have been fixed or documented in the security issue page of CLAMP | 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. In the case critical known vulnerability are still showing in the report, fill out the Security/Vulnerability Threat Template in your project. | Yes | Only Jackson Databind is left in CLAMP, which has been addressed, see the security issue page of CLAMP | 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)?Provide link to "Merge job" as evidence in Jenkins project tab | Yes | Jenkins CLAMP Tab | ||||||||||||||
| Are all snapshot binaries available in Nexus? | Yes | Provide link to evidence | ||||||||||||||
| 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?All jobs pertaining to your project MUST pass | No | Being fixed today | |||||||||||||
| Is there a Docker images available for your project deliverable? | Yes | Provide link to Nexus reposNexus 3 Docker repo | ||||||||||||||
| Has the project code successfully passed the Daily Build process? | Yes | Jenkins CLAMP Tab | 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?Add a link to your project documentation in ReadTheDocs. | No | An updated Release note is ready in Read the docs, we still plan to further improve the release documentation in the coming weeks. Read the docs RLN link to be added | 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? | Link to evidenceYes | Note that CLAMP is now integrated with SWAGGER and MSB | Ensure there is at least a direct link toward the API documentation which may be already existing in the wiki. |