...
M4 Release Code Freeze Milestone overview is available in wiki.
Practice Area | Checkpoint | Yes/No | Evidences | How to? |
---|
Product Management | Have all JIRA Stories supporting the release use case been implemented? |
InProgress Status |
---|
colour | Yellow |
---|
title | In-Progress |
---|
|
| Jira |
---|
server | ONAP JIRA |
---|
jqlQuery | project=portal and type=Story and fixversion="Beijing Release" |
---|
count | true |
---|
serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
---|
|
| 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. | No | Jira |
---|
server | ONAP JIRA |
---|
jqlQuery | project=portal and type=Story and fixversion="Casablanca Release" |
---|
count | true |
---|
serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
---|
|
| 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? |
InProgress | Status |
---|
colour | Yellow |
---|
title | In-Progress |
---|
|
| Link to Project backlog |
|
Are all tasks associated with committed Sprint Backlog Stories been marked as "Done" in Jira? |
InProgress | Status |
---|
colour | Yellow |
---|
title | In-Progress |
---|
|
|
|
|
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? | 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? |
InProgress | Status |
---|
colour | Yellow |
---|
title | In-Progress |
---|
|
| Jira |
---|
server | ONAP JIRA |
---|
jqlQuery | project=portal and type=bug and fixversion="Beijing Release" and priority in (Highest, High) |
---|
count | true |
---|
serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
---|
|
|
|
Has the project team reach the Automated Unit Test Code Coverage expectation? (Refer to artifacts available in Sonar) |
| Status |
---|
colour | Yellow |
---|
title | In-Progress |
---|
|
|
InProgress | Goal: 50% for Incubation project in Beijing portal line coverage is >50% - sonar link portal-sdk line coverage is > 50% - sonar link | For evidences, provide link(s) to Gerrit repos by providing the URL as shown in this example 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. | Yes | | 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: - 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. |
InProgress | Status |
---|
colour | Yellow |
---|
title | In-Progress |
---|
|
| Portal Platform Security/Vulnerability Threats | 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)? |
InProgress | Status |
---|
colour | Yellow |
---|
title | In-Progress |
---|
|
| Provide link to "Merge job" as evidence in Jenkins project tab |
|
Are all snapshot binaries available in Nexus? |
InProgress | Status |
---|
colour | Yellow |
---|
title | In-Progress |
---|
|
| 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? |
InProgressInProgress | Status |
---|
colour | Yellow |
---|
title | In-Progress |
---|
|
| Provide link to Nexus repos |
|
Has the project code successfully passed the Daily Build process? |
InProgress | Status |
---|
colour | Yellow |
---|
title | In-Progress |
---|
|
|
| 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? |
InProgress | Status |
---|
colour | Yellow |
---|
title | In-Progress |
---|
|
| 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. Link to Templates How to setup the template for my project? |
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. |