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 | Comment |
|---|---|---|---|---|
| Product Management | Have all JIRA Stories supporting the release use case been implemented? | Yes |
Getting issues...
| All Amsterdam release stories are implemented. |
| List the Stories that will not be implemented in this current Release. | Yes | Stories that are NOT implemented in Amsterdam Release.
Getting issues...
| All stories are marked for Beijing release, these were already planned for R2 during planning | |
| Are committed Sprint Backlog Stories been coded and marked as "Done" in Jira? | Yes | Link to Project backlog | Backlog only has Beijing stories | |
| 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? | Yes | For M2 and M3 Milestones, ensure all findings have been closed. | ||
| Development | Are all Defects of priority Highest and High in status "Done" in Jira? | Yes |
| |
| 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 | |||
| Are all the Jenkins jobs successfully passed (verify + merge jobs)? | Yes | Link to Merge Job | ||
| Are all snapshot binaries available in Nexus? | Yes | Link to Nexus artifacts | ||
| 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? | Yes | CSIT clamp jenkins jobs | Look for CLAMP tests |
| Is there a Docker images available for your project deliverable? | Yes | Link to CLAMP containers | ||
| Has the project code successfully passed the Daily Build process? | Yes | Daily build Job | 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 | Clamp Documentation | 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? | N/A | CLAMP doesn't expose any API | Ensure there is at least a direct link toward the API documentation which may be already existing in the wiki. |