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.
DRAFT
| Practice Area | Checkpoint | Yes/No | Evidences |
|---|
How to? |
|---|
| Product Management | Have all JIRA Stories supporting the release use case been implemented? | Yes |
| For each JIRA story that are implemented in Amsterdam Release, you have to setup in JIRA the JIRA fixVersion="Amsterdam Release" each JIRA story that will not be implemented in Amsterdam Release, you have to setup in JIRA the JIRA fixVersion="Beijing Release"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. |
None | For | Yes | Support for DCAE is moved to next release. |
| Are committed Sprint Backlog Stories been coded and marked as "Done" in Jira? | Yes |
Doc Project JIRA issues| Jira Legacy |
|---|
| server | System Jira |
|---|
| jqlQuery | project = "Command Line Interface" and fixVersion = "Beijing Release" AND issuetype = Story |
|---|
| count | true |
|---|
| serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
|---|
|
|
| Are all tasks associated with committed Sprint Backlog Stories been marked as "Done" in Jira? | Yes |
Doc Project JIRA issues | | Jira Legacy |
|---|
| server | System Jira |
|---|
| jqlQuery | project = "Command line interface" and fixVersion = "Beijing Release" |
|---|
| count | true |
|---|
| serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
|---|
|
|
| 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 |
M2 and M3 Milestones, ensure all findings have been closed.| both (a) and (b), have all high priority non-Project Licenses been either removed or escalated as likely exception requests? | Yes | Nexus IQ report Documentation |
| Development | Are all Defects of priority Highest and High in status "Done" in Jira? | Yes |
Provide link to JIRA issue (type bug) of priority Highest and High. Refer to CI Development Best PracticesRemaining High and Highest Defects : | Jira Legacy |
|---|
| server | System Jira |
|---|
| jqlQuery | project = "Command line interface" and (priority = high or priority = highest) and status = open |
|---|
| count | true |
|---|
| serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
|---|
|
|
| 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? |
N/A | Doc Project Gerrit status
|
| 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: - Critical is level 7 to 10
- Severe is level 4 to 6
- Moderate is level 1 to 3
which is complaint with CVSS V2.0 rating. | Yes | Nexus IQ report Documentation |
| Are all the Jenkins jobs successfully passed (verify + merge jobs)? | Yes |
Doc Project - jobs| CLI Tab |
| Are all snapshot binaries available in Nexus? |
N/AProvide 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? | Yes |
Doc Project - jobs Provide link to Nexus reposCLI Tab |
| Is there a Docker images available for your project deliverable? |
N/A | Goal is to ensure the latest project commit has not broken the Integration Daily Build N/A | How to setup the template for my project?| Yes | Jenkins CLI Tab |
| Doc | Has the team created a docs folder and Development and Release Notes documentation templates in Readthedocs? | Yes |
Doc Project Documentation | 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.
Link to Templates
Ensure there is at least a direct link toward the API documentation which may be already existing in the wiki.An updated Release note is ready in Read the docs, we still plan to further improve the release documentation in the coming weeks. Release Note link CLI ReadtheDocs link |
| Is the API documentation section populated? | Yes |
API Template |