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.
Info |
---|
|
- 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? |
By using the macro JIRA Issue/Filter, provide a link to JIRA in listing the stories that are implemented in Amsterdam Release. (ExampleYes | Jira Legacy |
---|
server | System Jira |
---|
jqlQuery | project= |
---|
|
|
aai optfra and type=Story and fixversion=" |
|
|
Amsterdam Casablanca Release" | count | true |
---|
serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
---|
|
|
for AAI project, edit for your project) | 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.By using the macro JIRA Issue/Filter, provide a link to JIRA in listing the stories that are NOT implemented in Amsterdam (Example |
| Jira Legacy |
---|
server | System Jira |
---|
jqlQuery | project= |
---|
|
|
aai optfra and type=Story and fixversion=" |
|
|
Beijing Dublin Release" | count | true |
---|
serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
---|
|
|
for AAI project, edit for your project) | 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 "Closed" in Jira? |
Provide Link to Project backlogYes | Jira Legacy |
---|
server | System Jira |
---|
jqlQuery | project = OPTFRA AND fixVersion = "Casablanca Release" and status in (closed, Delivered) and type in (Story) |
---|
count | true |
---|
serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
---|
|
|
|
Are all tasks associated with committed Sprint Backlog Stories been marked as "Closed" in Jira? | Yes | Jira Legacy |
---|
server | System Jira |
---|
jqlQuery | project = OPTFRA AND fixVersion = "Casablanca Release" and status in (Closed, Delivered) and type in (Sub-task, Task) |
---|
count | true |
---|
serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
---|
|
|
|
Release Management | Have all issues pertaining to FOSS been addressed? | Yes | There were no issues raised for the project. |
|
Have all findings from previous milestones been addressed? |
List previous milestone issues that have not been addressed.NA |
| 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 "Closed" in Jira? |
Provide link to JIRA issue (type bug) of priority Highest and High. | No | Jira Legacy |
---|
server | System Jira |
---|
jqlQuery | affectedVersion = "Casablanca Release" and issuetype = Bug and project="Optimization Framewok" and priority in (High, Highest) and status not in (closed) |
---|
count | true |
---|
serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
---|
| in progress Jira Legacy |
---|
server | System Jira |
---|
jqlQuery | affectedVersion = "Casablanca Release" and issuetype = Bug and project="Optimization Framewok" and priority in (High, Highest) and status in (closed) |
---|
count | true |
---|
serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
---|
| closed |
|
Has the project team reach the Automated Unit Test Code Coverage expectation? (Refer to artifacts available in Sonar) |
Goal: 50% for Incubation project in Beijing | For evidences, provide link(s) to Gerrit repos by providing the URL as shown in this example
ExampleRefer to CI Development Best PracticesProvide link to your project CII Best Practices page. | | 100% on Passing badge | | As documented in CII Badging Program, teams have to fill out CII Best Practices |
Is there any Critical and Severe 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. |
In the case critical known vulnerability are still showing in the report, fill out the Security/Vulnerability Threat Template in your project.Provide link to "Merge job" as evidence in Jenkins project tab HealtcheckHealthcheck related to your project passed? | No* | - We noticed a failure for one of our repos earlier today in SB04 - our team is trying to fix it as we speak. The other repos are passing their health check.
|
|
Are all snapshot binaries available in Nexus-staging? |
Provide link to evidenceAll jobs pertaining to your project MUST passProvide link to Nexus reposAdd a link to your project documentation in ReadTheDocs.Link to evidence