CheckList UMD Release Process
Jump to navigation
Jump to search
How to use this checklist
TBD
UMD Release process actions
No# | Action | Description | Responsible unit | Time Constrain | Status |
1 | Freeze UMD release contents | Using the UMD Composer add all products that are queued in the UMDStore to a new UMD release bundle. | TSA2.1 | Before T -1 Week | |
2 | Update UMD capabilities | Check that UMD Capabilities in UMD-1:Capabilities are up to date and in synch with the products in the UMD release. | TSA1.3, TSA2.2, TSA2.3 | Before T -1 Week | |
3 | Compile a "Known issues" | In the Wiki, compile a "Known issues" page for the pertinent UMD release at UMD-x:UMD-x.y.z using the major (x), minor (y) and revision(z) numbers of the UMD release. The page must contain one entry per Product contained in the UMD release. |
TSA1.3, TSA2.2, TSA2.3 | Before T -1 Week | |
4 | Compile UMD release metadata | UMD release metadata will be published in the UMD Repository and must cover the following sections:
|
TSA1.3, TSA2.2, TSA2.3 | During T -1 Week | |
5 | Release Candidate(s) | Produce release candidates as required based on feedback from EA.
|
TSA2.4 | ON T -1 Week | |
6 | Manage RC testing with StagedRollout EAs | Announce RC availability to EAs and document collected feedback, and inform TSA2.4 about the outcome. | TSA1.3 | ||
7 | Repeat (5) and (6) as required | For as long as there is feedback that stops publishing the UMD release, correct the reported issues and re-issue a new Release Candidate | TSA1.3, TSA2.4 | ||
8 | Final UMD release publication | Check the release matadata, the capabilities, and release contents before doing the release | TSA2.1 | on T | |
9 | Release post-processing | Update release plans in the Wiki, replacing the release contents plan with a link to the announcement. Set the announcement link in the Release Schedule overview, too. | TSA2.1 | After T |