Difference between revisions of "UMD 1.5.0 Contents"
Line 88: | Line 88: | ||
|} | |} | ||
--[[User:Michel|Michel]] | |||
== Delivery slip == | |||
{| cellspacing="0" cellpadding="5" border="1" | |||
|- | |||
| valign="top" | No# | |||
| valign="top" | Action | |||
| valign="top" | Description | |||
| valign="top" | Responsible unit | |||
| valign="top" | Time Constraint | |||
| valign="top" | Status | |||
|- | |||
| 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" | TSA2.1 | |||
| valign="top" | Before T -1 Week | |||
| valign="top" | <br> | |||
|- | |||
| 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" | TSA1.3, TSA2.2, TSA2.3 | |||
| valign="top" | Before T -1 Week | |||
| valign="top" | <br> | |||
|- | |||
| 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" | TSA1.3, TSA2.2, TSA2.3 | |||
| valign="top" | Before T -1 Week | |||
| valign="top" | <br> | |||
|- | |||
| 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: | |||
#Description | |||
#Contact Info | |||
#Technical Contact Info | |||
#Release Notes | |||
#Installation Notes | |||
#Known Issues | |||
#Change Log | |||
| valign="top" | TSA1.3, TSA2.2, TSA2.3 | |||
| valign="top" | During T -1 Week | |||
| valign="top" | <br> | |||
|- | |||
| valign="top" | 5 | |||
| valign="top" | Release Candidate(s) | |||
| 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" | ON T -1 Week | |||
| valign="top" | <br> | |||
|- | |||
| valign="top" | 6 | |||
| valign="top" | Manage RC testing with StagedRollout EAs | |||
| valign="top" | Announce RC availability to EAs and document collected feedback, and inform TSA2.4 about the outcome. | |||
| valign="top" | TSA1.3 | |||
| valign="top" | During T -1 Week | |||
| valign="top" | <br> | |||
|- | |||
| valign="top" | 7 | |||
| 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" | During T -1 Week | |||
| valign="top" | | |||
|- | |||
| valign="top" | 8 | |||
| 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" | on T | |||
| valign="top" | | |||
|- | |||
| valign="top" | 9 | |||
| 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" | After T | |||
| valign="top" | | |||
|} | |||
--[[User:Michel|Michel]] 10:34, 23 January 2012 (UTC) |
Revision as of 12:34, 23 January 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 |
The following provides an overview of the planned contents of UMD 1.5.0
This release was initially planed as version 1.4.0; however the OMB requested an intermittent release in mid-December, which was announced as version 1.4.0 due to new functionality provided.
The release timeline will be as follows:
16 Jan 2012 | Release day freeze |
23 Jan 2012 | Release contents freeze |
30 Jan 2012 | Release day |
Further information on the provisioning progress is provided at the EGI Provisioning Dashboard; to get an outlook at what is scheduled for the next UMD release please have a look at the UMDStore
.
Release plan
The following provides an overview of the planned contents for UMD 1.5.0; the order of entries in the table indicate the relative priority with which the referenced products will be taken through the provisioning process.
Platform | EGI Capability | Product | available on | Provider release | Notes | ||
---|---|---|---|---|---|---|---|
SL5 | SL6 | Debian6
| |||||
gLite
| |||||||
Job Execution | CREAM 1.13.3 | {{{SL5}}} | {{{SL6}}} | {{{Debian6}}} | EMI 1 Update 10 |
| |
CEMon 1.13.3 | {{{SL5}}} | {{{SL6}}} | {{{Debian6}}} | EMI 1 Update 7 |
| ||
APEL parsers 1.0.1 | {{{SL5}}} | {{{SL6}}} | {{{Debian6}}} | EMI-1 Update 8 |
| ||
GE module 1.0.0 | {{{SL5}}} | {{{SL6}}} | {{{Debian6}}} | EMI-1 Update 10 |
| ||
BLAH 1.16.4 | {{{SL5}}} | {{{SL6}}} | {{{Debian6}}} | EMI-1 Update 12 |
| ||
Storage Management, File Access, File Transfer |
DPM 1.8.2 | {{{SL5}}} | {{{SL6}}} | {{{Debian6}}} | EMI-1 Update 10 |
| |
Metadata Catalogue | LFC/MySQL 1.8.2 | {{{SL5}}} | {{{SL6}}} | {{{Debian6}}} | EMI-1 Update 12 |
| |
Storage Management, File Access, File Transfer |
StoRM 1.8.1 | {{{SL5}}} | {{{SL6}}} | {{{Debian6}}} | EMI-1 Update 11 |
| |
Job Scheduling | WMS 3.3.4 | {{{SL5}}} | {{{SL6}}} | {{{Debian6}}} | EMI 1 Update 11 |
| |
L&B 3.1.0 | {{{SL5}}} | {{{SL6}}} | {{{Debian6}}} | EMI-1 Update 9 |
| ||
Parallel Job | EMI MPI 1.2.0 | {{{SL5}}} | {{{SL6}}} | {{{Debian6}}} | EMI 1 Update 11 |
|
Delivery slip
No# | Action | Description | Responsible unit | Time Constraint | 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 | During T -1 Week | |
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 | During T -1 Week | |
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 |
--Michel 10:34, 23 January 2012 (UTC)