Difference between revisions of "CheckList UMD Release Process"
Jump to navigation
Jump to search
Line 1: | Line 1: | ||
== How to use this checklist == | |||
TBD | |||
== UMD Release process actions == | |||
{| width="900" cellspacing="0" cellpadding="5" border="1" | |||
|- | |- | ||
| valign="top" | | valign="top" | No# | ||
| valign="top" | Action | |||
| valign="top" | Description | |||
| valign="top" | | valign="top" | Responsible unit | ||
| valign="top" | Status | |||
|- | |- | ||
| valign="top" | | valign="top" | 1 | ||
| valign="top" | Freeze UMD release contents | |||
| valign="top" | Using the UMD Composer add all products that are queued in the UMDStore to a new UMD release bundle. | |||
| valign="top" | | valign="top" | TSA2.1 | ||
| valign="top" | <br> | |||
| valign="top" | |||
a | |||
| valign="top" | |||
| valign="top" | |||
| | |||
<br> | |||
|- | |- | ||
| valign="top" | | valign="top" | 2 | ||
| valign="top" | Update UMD capabilities | |||
| valign="top" | Check that UMD Capabilities in [[UMD-1:Capabilities]] are up to date and in synch with the products in the UMD release. | |||
| valign="top" | | valign="top" | TSA1.3, TSA2.2, TSA2.3 | ||
| valign="top" | <br> | |||
|- | |- | ||
| valign="top" | | valign="top" | 3 | ||
| valign="top" | Compile a "Known issues" | |||
| valign="top" | 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.<br> | |||
The page must contain one entry per Product contained in the UMD release. | |||
| valign="top" | |||
<br> | |||
| valign="top" | TSA1.3, TSA2.2, TSA2.3 | |||
| valign="top" | <br> | |||
|- | |- | ||
| valign="top" | | valign="top" | 4 | ||
| valign="top" | Compile UMD release metadata | |||
| valign="top" | UMD release metadata will be published in the [http://repository.egi.eu UMD Repository] and must cover the following sections: | |||
| valign="top" | #Description | ||
#Contact Info | |||
#Technical Contact Info | |||
#Release Notes | |||
#Installation Notes | |||
#Known Issues | |||
#Change Log | |||
| valign="top" | TSA1.3, TSA2.2, TSA2.3 | |||
| valign="top" | <br> | |||
|- | |- | ||
| valign="top" | | valign="top" | 5 | ||
| valign="top" | Release Candidate(s) | |||
| valign="top" | | valign="top" | Produce release candidates as required based on feedback from EA. | ||
*Update the Capabilities tags according to the information produced in (2) | |||
*Add release notes etc. as produced and reviewed from step (4) | |||
| valign="top" | TSA2.4 | |||
| valign="top" | <br> | |||
| valign="top" | | |||
| valign="top" | | |||
|- | |- | ||
| valign="top" | | | valign="top" | 6 | ||
| valign="top" | | | valign="top" | Manage RC testing with StagedRollout EAs | ||
| valign="top" | | | valign="top" | Announce RC availability to EAs and document collected feedback, and inform TSA2.4 about the outcome. | ||
| valign="top" | TSA1.3 | |||
| valign="top" | <br> | |||
|- | |- | ||
| valign="top" | | | valign="top" | 7 | ||
| valign="top" | | | valign="top" | Repeat (5) and (6) as required | ||
| valign="top" | For as long as there is feedback that stops publishing the UMD release, correct the reported issues and re-issue a new Release Candidate | |||
| valign="top" | TSA1.3, TSA2.4 | |||
| valign="top" | | | valign="top" | | ||
|- | |- | ||
| valign="top" | | | valign="top" | 8 | ||
| valign="top" | | | valign="top" | Final UMD release publication | ||
| valign="top" | Check the release matadata, the capabilities, and release contents before doing the release | |||
| valign="top" | TSA2.1 | |||
| valign="top" | | | valign="top" | | ||
|- | |- | ||
| valign="top" | | | valign="top" | 9 | ||
| valign="top" | | | valign="top" | Release post-processing | ||
| valign="top" | 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. | |||
| valign="top" | TSA2.1 | |||
| valign="top" | | | valign="top" | | ||
|} | |} | ||
[[Category:WP5-SA2]] | [[Category:WP5-SA2]] |
Revision as of 12:10, 2 November 2011
How to use this checklist
TBD
UMD Release process actions
No# | Action | Description | Responsible unit | 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 | |
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 | |
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 | |
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 | |
5 | Release Candidate(s) | Produce release candidates as required based on feedback from EA.
|
TSA2.4 | |
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 | |
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 |