Difference between revisions of "UMD 1.6.0 Contents"
Jump to navigation
Jump to search
(6 intermediate revisions by 2 users not shown) | |||
Line 1: | Line 1: | ||
{{Tech menubar}} {{Tech Roadmap submenu}} {{TOC_right}} | {{Tech menubar}} {{Tech Roadmap submenu}} {{TOC_right}} | ||
EGI has released UMD 1.6.0 on 2 April 2012. ([http://repository.egi.eu/2012/04/02/release-umd-1-6-0/ Announcement]) | |||
== Delivery slip == | == Delivery slip == | ||
Line 181: | Line 36: | ||
| RespUnit = TSA2.4 | | RespUnit = TSA2.4 | ||
| DueOn = T - 7 | | DueOn = T - 7 | ||
| Ref = | | Ref = [[UMD-1:UMD-1.6.0]] | ||
| SignedOff = Kostas }} | | SignedOff = Kostas }} | ||
Line 189: | Line 44: | ||
| RespUnit = TSA2.3 | | RespUnit = TSA2.3 | ||
| DueOn = T - 7 | | DueOn = T - 7 | ||
| Ref = | | Ref = [[UMD-1:UMD-1.6.0]] | ||
| SignedOff = Mario, Alvaro}} | | SignedOff = Mario, Alvaro}} | ||
Line 197: | Line 52: | ||
| RespUnit = TSA1.3 | | RespUnit = TSA1.3 | ||
| DueOn = T - 7 | | DueOn = T - 7 | ||
| Ref = | | Ref = [[UMD-1:UMD-1.6.0]] | ||
| SignedOff = Mario}} | | SignedOff = Mario}} | ||
Line 214: | Line 69: | ||
| RespUnit = TSA2.1 | | RespUnit = TSA2.1 | ||
| DueOn = T - 3 | | DueOn = T - 3 | ||
| Ref = | | Ref = http://repository.egi.eu/2012/04/02/release-umd-1-6-0/ | ||
| SignedOff = }} | | SignedOff = Michel}} | ||
{{UMD:DeliverySlipAction | No = 5 | {{UMD:DeliverySlipAction | No = 5 | ||
Line 238: | Line 93: | ||
| RespUnit = TSA2.3 | | RespUnit = TSA2.3 | ||
| DueOn = T - 5 | | DueOn = T - 5 | ||
| Ref = | | Ref = https://mailman.egi.eu/mailman/private/inspire-sa2/2012-March/001923.html | ||
| SignedOff = }} | | SignedOff = Michel (on behalf of A. Simon}} | ||
{{UMD:DeliverySlipAction | No = | {{UMD:DeliverySlipAction | No = | ||
Line 254: | Line 109: | ||
| RespUnit = TSA2.1 | | RespUnit = TSA2.1 | ||
| DueOn = T | | DueOn = T | ||
| Ref = | | Ref = http://repository.egi.eu/2012/04/02/release-umd-1-6-0/ | ||
| SignedOff = }} | | SignedOff = Michel}} | ||
{{UMD:DeliverySlipAction | No = 7 | {{UMD:DeliverySlipAction | No = 7 | ||
Line 267: | Line 122: | ||
| RespUnit = TSA2.1 | | RespUnit = TSA2.1 | ||
| DueOn = after T | | DueOn = after T | ||
| Ref = | | Ref = [[UMD_1.6.0_Contents]] | ||
| SignedOff = }} | | SignedOff = Michel}} |
Latest revision as of 21:40, 1 December 2012
Technology | Software Component Delivery | Software Provisioning | UMD Middleware | Cloud Middleware Distribution | Containers Distribution | Technology Glossary |
Roadmap and Technology | | Technology insertion plans | UMD Release Schedule Overview | | Glossary |
EGI has released UMD 1.6.0 on 2 April 2012. (Announcement)
Delivery slip
No. | Action | Description | Responsible unit | due on | References | signed off by
|
---|---|---|---|---|---|---|
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 - 7 | [UMD 1.6.0 RC1] | Michel
|
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. | TSA2.1 | Before T - 7 | [UMD 1.6.0 RC1] | Michel
|
3 | "Known Issues & Installation notes" | Check that sub-actions are finished according to requirements | TSA2.1 | T - 4 | see below | Michel
|
3.1 - Create Wiki entry | Create a Wiki entry for the release at UMD-1:UMD-1.6.0 using the major (x), minor (y) and revision (z) numbers of the UMD release. Create sections for each product that is included in the documented UMD release. |
TSA2.4 | T - 7 | UMD-1:UMD-1.6.0 | Kostas
| |
3.2 - Document Verification findings | Add all findings (bugs, workarounds, etc.) collected in the QC Verification reports to the "Known Issues & Installation notes" wiki entry. | TSA2.3 | T - 7 | UMD-1:UMD-1.6.0 | Mario, Alvaro
| |
3.3 - Document Staged Rollout findings | Collect all issues, warnings, workarounds etc. to the "Known issues & Installation notes" wiki entry. | TSA1.3 | T - 7 | UMD-1:UMD-1.6.0 | Mario
| |
4 | Compile UMD release documentation | UMD release metadata will be published in the UMD Repository and must cover the following sections:
TSA1.3, TSA2.3 will contribute. TSA1.3 and all SA2 tasks review drafts and give comments. |
TSA2.1 | T - 3 | http://repository.egi.eu/2012/04/02/release-umd-1-6-0/ | Michel
|
5 | Produce and test release candidate(s) | Produce as many Release Candidates as required based on the feedback given. If no feedback is given assume the Release Candidate working correctly. For each Release Candidate round new sub-actions need to be created for the delivery slip. | TSA2.1 | T - 7 | http://repository.egi.eu/category/umd_release_candidates/umd_1_rc2/ | Kostas
|
5.1 - Produce first release candidate | From the list of included products in (1) generate a Release Candidate. Notify TSA2.4 and TSA1.3 of the existence and location of the Release Candidate. | TSA2.4 | T - 7 | http://repository.egi.eu/category/umd_release_candidates/umd_1_rc2/ | Kostas
| |
5.2 - Test first Release Candidate (Verification) | Test the first release candidate for errors and advise TSA2.4 whether to create another Release Candidate. Testing is mandatory for TSA2.3. | TSA2.3 | T - 5 | https://mailman.egi.eu/mailman/private/inspire-sa2/2012-March/001923.html | Michel (on behalf of A. Simon
| |
5.3 - Test the first Release Candidate (SR) | Call for volunteers for RC testing among the EAs in Staged Rollout. Collect feedback from participating sites and advise TSA2.4 whether to create another Release Candidate. Testing is optional for TSA1.3. | TSA1.3 | T - 5 |
| ||
6 | Publish UMD release | Only when all previous actions are signed off, publish the UMD release. | TSA2.1 | T | http://repository.egi.eu/2012/04/02/release-umd-1-6-0/ | Michel
|
7 | Post-release cleanup | Post-release actions perform some housekeeping in the UMD release management area, including:
|
TSA2.1 | after T | UMD_1.6.0_Contents | Michel |