...
| 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 |
| ||||||||||||
Summarize any functionalities that were planned at Release planning and not delivered at Release Sign-Off | N/A | |||||||||||||
| Release Management | Have all issues pertaining to FOSS been addressed? | Yes | ||||||||||||
| Have all findings from previous milestones been addressed? | Yes | Provide link to JIRA findings | ||||||||||||
| Development | Are all the Jenkins jobs successfully passed (verify + merge jobs)? | Yes | ||||||||||||
| Are all binaries available in Nexus Release repository? | Yes | Provide link to evidence | ||||||||||||
| Are all Docker images available In Nexus? | Yes | Provide link to evidence | ||||||||||||
| Are the Java and Docker manifest updated with the same version as in Nexus Release repository? | ||||||||||||||
| Integration and Testing | Have all CSIT Use Cases (created by each project team) passed? | Provide link to evidence | 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? | Provide link to evidence | 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? | ||||||||||||||
| Documentation | Has your team contributed and completed work in the following documentations in ReadTheDocs:
| Provide Link to ReadTheDocs Release Notes Provide Link to ReadTheDocs Project Documentation |