...
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. (ExampleWIP |
| For each JIRA story that are implemented in Amsterdam Release, you have to setup in JIRA the JIRA fixVersion="Amsterdam Release"work on testing and some non functional is still in progress | |||||||||||||||||||||||||||||
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
| For each JIRA story that will not be implemented in Amsterdam Release, you have to setup in JIRA the JIRA fixVersion="Beijing Release" no plans to remove planed content at the moment | |||||||||||||||||||||||||||||||
Are committed Sprint Backlog Stories been coded and marked as "Done" in Jira? | Provide Link to Project backlogYes | ||||||||||||||||||||||||||||||||
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? | 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? | WIP |
| |||||||||||||||||||||||||||||||
For both (a) and (b), have all high priority non-Project Licenses been either removed or escalated as likely exception requests? | WIP | ||||||||||||||||||||||||||||||||
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. WIP | |||||||||||||||||||||||||||||||
Has the project team reach the Automated Unit Test Code Coverage expectation? (Refer to artifacts available in Sonar) | WIP | Goal: 50% for Incubation project in Beijing | repos: sdc 29.9% coverage sdc-tosca 73.2% coverage sdc-distribution-client 51.4% coverage sdc-workflow-designer 68.9% coverage sdc-jtosca 48.1% coverage sdc plans to reach 50% cross repos thsi work will progress with the realse process and will be complet untill the relase. 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 | the only zip files in sdc are vnf s that are packaged as zip files and are used for executing unit tests.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 CII Best Practices page. | WIP | https://bestpractices.coreinfrastructure.org/en/projects/1629 SDC is corently at 92% 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. | WIP | SDC In the case critical known vulnerability are still showing in the report, fill out the Security/Vulnerability Threat Template 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. | SDC is in the process of documanting and solving the issues that we find. there is new input provided by the integration team that now needs to be adresssed | ||||||||||||||||||||||||||||||
Are all the Jenkins jobs successfully passed (verify + merge jobs)? | Provide link to "Merge job" as evidence in Jenkins project tab | https://jenkins.onap.org/view/sdc/job/sdc-master-sdc-merge-java/ `https://jenkins.onap.org/view/sdc-sdc-workflow/job/sdc-sdc-workflow-designer-master-merge-java/ https://jenkins.onap.org/view/sdc-sdc-tosca/job/sdc-sdc-tosca-master-merge-java/ https://jenkins.onap.org/view/sdc-sdc-titan/job/sdc-sdc-titan-cassandra-master-merge-java/ https://jenkins.onap.org/view/sdc-jtosca/job/sdc-jtosca-master-merge-java/ | |||||||||||||||||||||||||||||||
Are all snapshot binaries available in Nexus? | Provide link to evidenceYes | ||||||||||||||||||||||||||||||||
Do you have a clear plan to implement the Independent Versioning and Release Process by RC0? | 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.Yes | ||||||||||||||||||||||||||||||||
Integration and Testing | Have 100% of Continuous System Integration Testing (CSIT) Use Cases been implemented successfully in Jenkins? | Yes | All jobs pertaining to your project MUST pass | ||||||||||||||||||||||||||||||
Is there a Docker images available for your project deliverable? | Provide link to Nexus reposYes | ||||||||||||||||||||||||||||||||
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 | |||||||||||||||||||||||||||||||
Doc | Has the team created a docs folder and Development and Release Notes documentation templates in Readthedocs? | Yes | Add a link to your project documentation in ReadTheDocs. | 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 | Link to evidence | Ensure there is at least a direct link toward the API documentation which may be already existing in the wiki. |