CLAMP R1 Amsterdam Release - Release Sign-Off Milestone Checklist
- ChrisC
The following items are expected to be completed for the project to Pass Release Sign-Off Milestone.
Release Sign-Off Milestone overview is available in wiki.
Practice Area | Checkpoint | Yes/No | Evidences |
|---|---|---|---|
Product Management | Are committed Product Backlog Stories been coded and marked as "Done" in Jira? | Yes | |
Are all tasks associated with committed Product Backlog Stories been marked as "Done" in Jira? | Yes | ||
Provide the project features list under the form of a bulleted list. |
| See Release Note | |
Summarize any functionalities that were planned at Release planning and not delivered at Release Sign-Off | Yes | All functionalities are delivered but the vVOLTE interaction required some hard coding of values in Holmes due to a limitation in Policy and DCAE for the provisioning. The following Beijing Tickets were created to track the resolution of this : | |
Release Management | Have all issues pertaining to FOSS been addressed? | Yes | No open issues on CLAMP FOSS for Amsterdam Release |
Have all findings from previous milestones been addressed? | Yes | No finding from previous release | |
Development | Are all the Jenkins jobs successfully passed (verify + merge jobs)? | Yes | |
Are all binaries available in Nexus Release repository? | Yes | ||
Are all Docker images available In Nexus? | Yes | ||
Are the Java and Docker manifest updated with the same version as in Nexus Release repository? | Yes | Docker and Maven version set to release 1.1.0 in manifest | |
Integration and Testing | Have all CSIT Use Cases (created by each project team) passed? | Yes | |
Has the project code successfully passed the Daily Build process? | Yes | ||
Has the project done the integration testing with related dependent projects? | Yes | ||
Documentation | Has your team contributed and completed work in the following documentations in ReadTheDocs:
| Yes | Link to ReadTheDocs Release Notes |