Alert.png 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 Release Schedule

From EGIWiki
Jump to navigation Jump to search
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 UMD Release Schedule describes the planned release schedule for UMD major and minor releases. UMD major releases (such as UMD 1.x, UMD 2.x, etc.) will be supported and updated while EGI is provided with updates from it technology providers for at most two consecutive years from the date of their initial release. UMD major releases will be made when non-backwards compatible changes need to be made to the software components within it. Minor releases within a major series (i.e. UMD 1.0.x and UMD 1.1.y) may introduce new functionality but existing interfaces and behaviours will remain.

Note: While EGI aspires to follow this plan as closely as possible, the UMD Release Plan is dependent on the software provided by our external technology providers and the quality of information (if provided) and their ability to meet their announced release dates. Therefore there will be no guarantee on release dates and contents other than the timely communication of changes as they become apparent. In particular, the time taken to include a product into a certain UMD release greatly depends on diligent and volunteer based StagedRollout activity [R 4]. If no volunteer picks up this Product and exposes it to the Production Infrastructure then that given Product is in danger of not being included in the planned UMD release and will be shipped later.

Unified Middleware Distribution 1

The following provides a planned schedule of UMD 1. For the major, and each minor release, more detailed release plans are provided in subsequent sections.

UMD-1 will reach end of support at 30 April 2013.

Release Release date Supported OS Architecture Notes
1.0.0 11 July 2011 SL5 x86_64 Announcement
1.1.0 1 August 2011 SL5 x86_64 Announcement
1.2.0 12 September 2011 SL5 x86_64
1.3.0 31 October 2011 SL5 x86_64
1.4.0 30 Januar 2012 SL5 x86_64

UMD release timeline

The following proposed deadlines determine in ultimo which Product version will be included in the next upcoming UMD release (as opposed to being planned for inclusion - that's the release schedule's purpose). The timeline is defined relative to a UMD release publication date as defined in the UMD release schedule:

t-2 weeks Release date freeze.

The release date for the respective UMD release is fixated to the then set date. Before the release freeze date, the release date (and all dependent timeline dates) may change. While in theory this may mean that one can delay a given UMD release indefinitely, in practice that has never happened so far.

t-1 week Release contents cut-off.

Any product in the Software Provisioning process that did *not* get accepted by StagedRollout by that day, will be pushed to the subsequent UMD release (or perhaps even later as required). Technically, at that day, all products with an RT ticket in state "UMDStore" in the "sw-rel" queue will be taken into the UMD Composer, all at once. (see below)

t-1 week Compose the UMD release.

The products that made the cut-off date will be taken into the next UMD release in the UMD Composer. Verification and StagedRollout assemble the necessary documentation, such as Konwn issues, Installation notes, etc. for the release's Wiki page, and summaries for the UMD release itself that will be published in the repository later-on. 2 days are seen enough, particularly when the relevant information is pre-assembled in a temporary Wiki space etc.

t-3 days Prepare a release candidate.

A formal test release is prepared including all selected products - including(!) the release documentation (release notes etc). The point is to have a complete set for final reviews. Further test releases are prepared as required and documented.

t Publish the UMD release.

The UMD release is published for production. The aim is to publish UMD releases on a Monday, or in the first half of the week up to and including Wednesdays.

The UMD Release Schedule is updated as required: Changes in Technology Provider Release Schedules may trigger changes in the UMD Release Schedule.