SDC R3 M4 Deliverables for Code Freeze Milestone Checklist
The following items are expected to be completed for the project to Pass the M4 Code Freeze Milestone.
M4 Release Code Freeze Milestone overview is available in wiki.
Usage
Use the "Copy" option (available under the ..., top right of this page) to duplicate this template into your project wiki.
Fill out the Yes/No column
Provide link to evidence (when necessary)
Practice Area | Checkpoint | Yes/No | Evidences | How to? |
|---|---|---|---|---|
Product Management | Have all JIRA Stories supporting the release use case been implemented? | WIP |
work on testing and some non functional is still in progress |
|
List the Stories that will not be implemented in this current Release. |
| no plans to remove planed content at the moment |
| |
Are committed Sprint Backlog Stories been coded and marked as "Done" in Jira? | Yes |
|
| |
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 and 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? | In progress |
|
|
Has the project team reach the Automated Unit Test Code Coverage expectation? (Refer to artifacts available in Sonar) | In progress |
|
| |
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. | |
Is there any pending commit request older than 36 hours in Gerrit? | In progress |
|
| |
Provide the "% Achived" on the CII Best Practices program. | In progress |
| https://bestpractices.coreinfrastructure.org/en/projects/1629 SDC is corently at 92% | |
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 progress |
| 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)? | Yes | 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? | Yes |
|
| |
Do you have a clear plan to implement the Independent Versioning and Release Process by RC0? | Yes |
|
| |
Integration and Testing | Have 100% of Continuous System Integration Testing (CSIT) Use Cases been implemented successfully in Jenkins? | Yes |
| |
Is there a Docker images available for your project deliverable? | Yes |
|
| |
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? | No | 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. |