CLAMP R1 Amsterdam Release - RC2 Release Candidate Milestone Checklist
The following items are expected to be completed for the project to Pass the Release Candidate Milestone.
This template must be filled out for every Release Candidate Milestone (RC0, 1, 2, x)
RC Release Candidate Milestone overview is available in wiki.
Practice Area | Checkpoint | Yes/No | Evidences | Comments |
---|---|---|---|---|
Product Management | Are all tasks associated with the release been marked as "Done" in Jira? | Yes | Remaining Task is Delivered, waiting for originator to close | |
Have all findings from previous milestones been addressed? | Yes | No finding from previous release | ||
Development | Have all Defects of priority Highest and High been in status "Done" in Jira? | Yes | Getting issues... | No High or Highest Defects remaining |
Are all JIRA issues used as a reference in a commit in status "Done" in Jira? | Yes | |||
Is there any pending commit related to Highest and High priority issues older than 36 hours in Gerrit? In case there are messages going back and forth between authors and reviewers, it is acceptable to be above 36 hours. | No | |||
Are all the Jenkins jobs successfully passed (verify + merge jobs)? | Yes | |||
Has the team delivered all their release artifacts in Nexus Releases repo? There should be at least ONE version of each artifacts available in Nexus Releases repo. | Yes | Refer to Independent Versioning and Release Process for procedure | ||
Integration and Testing | Have all CSIT Use Cases (created by each project team) passed? | Yes | ||
Is there a Docker images available for each repository? | Yes | Docker Image moved to 1.1 | ||
Has the project code successfully passed the Daily Build process? | Yes | Goal is to ensure the latest project commit has not broken the Integration Daily Build | ||
Documentation | For RC2, for project delivering binaries, has the team populated and validated all the sections of the Release Notes template? | Yes | ||
For RC2, has the Documentation Team provided the final approval for your project documentation? | Yes | Approval from Doc team received on 11/8 |