The wiki is deprecated and due to be decommissioned by the end of September 2022.
The content is being migrated to other supports, new updates will be ignored and lost.
If needed you can get in touch with EGI SDIS team using operations @ egi.eu.
UMD 1.5.0 Contents
Jump to navigation
Jump to search
The printable version is no longer supported and may have rendering errors. Please update your browser bookmarks and please use the default browser print function instead.
| 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.5.0 on 30 January 2012. (Announcement)
Delivery slip
| No# | Action | Description | Responsible unit | Time Constraint | References | 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 | Done. | Michel, 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 | Before T -1 Week | Mapping | Michel, TSA1.1 |
| 3 | Compile a "Known issues" | In the Wiki, compile a "Known issues" page for the pertinent UMD release at UMD-1:UMD-1.5.0 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.3 | Before T -1 Week | UMD1.5.0 Release Notes | Alvaro, 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 | During T -1 Week | [RC1] | Michel, TSA2.1 |
| 5 | Release Candidate(s) | Produce release candidates as required based on feedback from EA.
|
TSA2.4 | ON T -1 Week | [RC1] | Michel, TSA2.1 |
| 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 | No feedback received. | Michel, TSA2.1 |
| 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 | SA2.3 tests | Michel, TSA2.1 |
| 8 | Final UMD release publication | Check the release metadata, the capabilities, and release contents before doing the release | TSA2.1 | on T | See notes. | Michel, 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 | After T | See notes. | Michel, TSA2.1 |
--Michel 13:48, 30 January 2012 (UTC)