DRAFT PROPOSAL FOR COMMENTS
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.
Usage
- Use the "Copy" and "Move" options (available under the ..., top right of this page) to duplicate this template into your project wiki.
- Fill out the Yes/No column
- Provide link to evidence (when necessary)
| Practice Area | Checkpoint | Yes/No | Evidences | How to? |
|---|---|---|---|---|
| Product Management | Are all tasks associated with the release been marked as "Done" in Jira? | Yes | VF-C Backlog | |
| Release Management | (For RC0 only) As the project team identified the reduced set of Committers who will proceed with Code Merge after RC0? | Yes | Provide the name of committers. Recommendation is 3 committers max per project (1 per geographic area)? Jinhua Fu Xin Lu Guirong Wang Yufei Zhou | |
| Have all findings from previous milestones been addressed? | Yes | Provide link to JIRA findings | ||
| Development | Have all Defects of priority Highest and High been in status "Done" in Jira? | Yes | Provide link to JIRA issue (type bug) of priority Highest and High. Getting issues... | |
| Are all JIRA issues used as a reference in a commit in status "Done" in Jira? | Yes | Very often, some JIRA issue remains in status "Todo" in JIRA while the commit they are referenced to is successful. | ||
| Is there any pending commit request older than 24 hours in Gerrit? | No | |||
| Are all the Jenkins jobs successfully passed (verify + merge jobs)? | Yes | VF-C jenkins job | ||
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. | In processing | Refer to Independent Versioning and Release Process for procedure | ||
| Integration and Testing | Have all CSIT Use Cases (created by each project team) passed? | Yes | VF-C jenkins job | |
| Have all end-to-end CSIT (created by Integration Team) been identified (for RC0) and passed (for RC1)? | Provide link to evidence | |||
| Is there a Docker images available for each repository? | Yes | VF-C docker images list | ||
| Has the project code successfully passed the Daily Build process? | Yes | VF-C jenkins job | Goal is to ensure the latest project commit has not broken the Integration Daily Build | |
| Documentation | For RC0, has the team populated and validated all the sections in the Documentation template? These information must be useful for installation, configuration, and usage. For RC1, has the team addressed to issue (recorded in JIRA) provided by the Documentation team? For RC2, have all remaining issues been addressed? For RC2, has the Documentation Team provided the final approval for your project documentation? | In processing | Documentation Team is using ReadTheDocs for documenting user facing documentation. |