Modeling Deliverables for Code Freeze Milestone Checklist Template
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" and "Move" options (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 | All all JIRA Stories supporting the release use case been implemented? | Yes |
|
|
List the Stories that will not be implemented in this current Release. | No | Provide link to JIRA Query listing the stories that will not be implemented in current stories. (Example for AAI project) | For each JIRA story that will not be implemented in Amsterdam Release, you have to setup in JIRA the JIRA fixVersion=Beijing | |
Are committed Sprint Backlog Stories been coded and marked as "Done" in Jira? | Yes | Provide Link to Project backlog |
| |
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? |
| Provide link to JIRA findings |
| |
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. |
|
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 |
|
| |
Are all the Jenkins jobs successfully passed (verify + merge jobs)? | Yes | Provide link to "Merge job" as evidence in Jenkins project tab |
| |
Are all snapshot binaries available in Nexus? | no | 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? | In Progress |
| |
Is there a Docker images available for each repositories? | In Progress |
|
| |
Has the project code successfully passed the Daily Build process? | no |
| Goal is to ensure the latest project commit has not broken the Integration Daily Build | |
Doc | Has the team created a documentation Template in ReadTheDocs? | Yes | Add a link toward the your project documention in ReadTheDocs. | Documentation Team is using ReadTheDocs for documenting user facing documentation. ReadTheDcos shall be considered as a starting pint for someone new withn ONAP. The ReadTheDcos is the ONAP Documentation facade visible to users. Link to Template |
Is the API documentation section poplulated? | Yes |
| Ensure there is at least a direct link toward the API documentation which may be already existing in the wiki. |