MUSIC Deliverables for Release Sign-Off Milestone Checklist
- bharathb
Practice Area | Checkpoint | Yes/No | Evidences | How to? |
|---|---|---|---|---|
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. | Yes |
For Beijing this will be run as internal services to both Portal and OOF. | ||
Summarize any functionalities that were planned at Release planning and not delivered at Release Sign-Off | NA | |||
Release Management | Have all issues pertaining to FOSS been addressed? | Yes | ||
Have all findings from previous milestones been addressed? | Yes | |||
Development | Are all the Jenkins jobs successfully passed (verify + merge jobs)? | |||
Are all binaries available in Nexus Release repository? | ||||
Are all Docker images available In Nexus? | ||||
Are the Java and Docker manifest updated with the same version as in Nexus Release repository? | Work in progress with LF wherein it is showing a more recent version (2.5.6 rather than 2.5.5) | |||
Integration and Testing | Have all CSIT Use Cases (created by each project team) passed? | Goal is to incease our confidence the latest commit did not break the major functionality. Jenkins CSIT Jobs | ||
Has the project code successfully passed the Daily Build process? | Goal is to ensure the latest project commit has not broken the Integration Daily Build | |||
Has the project done the integration testing with related dependent projects? | Yes | We are being consumed internally both by ONAP HAS and ONAP Portal and we have passed testing within that scope. | ||
Documentation | Has your team contributed and completed work in the following documentations in ReadTheDocs:
|