Beijing-M4-Checklist-Code Freeze Milestone
- Former user (Deleted)
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.
Practice Area | Checkpoint | Yes/No | Evidences |
|---|---|---|---|
Product Management | Have all JIRA Stories supporting the release use case been implemented? | Yes | support for appc is in progress and working with AT&T to complete it by RC0. |
List the Stories that will not be implemented in this current Release. | Yes | Support for DCAE is moved to next release. | |
Are committed Sprint Backlog Stories been coded and marked as "Done" in Jira? | Yes | Getting issues... | |
Are all tasks associated with committed Sprint Backlog Stories been marked as "Done" in Jira? | Yes | Getting issues... | |
Release Management | Have all issues pertaining to FOSS been addressed? | Yes | |
Have all findings from previous milestones been addressed? | Yes | No Specific findings. | |
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? | Yes | Remaining High and Highest Defects : Getting issues... |
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 | |
Is there any binaries (jar, war, tar, gz, gzip, zip files) in Gerrit project repository? | No | ||
Is there any pending commit request older than 36 hours in Gerrit? | No | ||
Provide the "% Achived" on the CII Best Practices program. | 100% | ||
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. | Yes | ||
Are all the Jenkins jobs successfully passed (verify + merge jobs)? | Yes | ||
Are all snapshot binaries available in Nexus? | Yes | link to evidence | |
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? | Yes | ||
Doc | Has the team created a docs folder and Development and Release Notes documentation templates in Readthedocs? | Yes | An updated Release note is ready in Read the docs, we still plan to further improve the release documentation in the coming weeks. |
Is the API documentation section populated? | Yes |