The following describes the EGI Capabilities and the expected implementations from available EGI Technology Provider. 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 4

The following provides a planned schedule of UMD 4.The architecture of UMD4 is x86_64 only.

ReleaseRelease dateSupported OSAnnouncementNotes

4.16.2May 2022CentOS7
4.16.1April 2022CentOS7
4.16.0march 2022CentOS7
4.15.1November 2021CentOS7
4.15.0October 2021CentOS7PlannedRegular
4.14.0June 2021CentOS7PlannedRegular
4.13.1May 2021CentOS7
4.13.0April 2021CentOS7
4.12.5November 23rd, 2020CentOS7,SL6
4.12.4November 20th, 2020CentOS7,SL6
4.12.3November 18th, 2020CentOS7,SL6
4.12.2October 19th, 2020CentOS7,SL6
4.12.1October 15th, 2020CentOS7,SL6
4.12.0October 13rd, 2020CentOS7,SL6
4.11.2Aug 14th, 2020CentOS7,SL6 release
4.11.1July 21st, 2020CentOS7,SL6 release
4.11.0June 29th, 2020CentOS7,SL6
4.10.3April 16th, 2020CentOS7,SL6
4.10.2April 15th, 2020CentOS7,SL6 release
4.10.1April 6th, 2020CentOS7,SL6 release
4.10.0March 26, 2020CentOS7,SL6 release
4.9.2February 10, 2020CentOS7, SL6 fix for CERN Frontier
4.9.1December 12, 2019CentOS7 update
4.9.0November 11, 2019CentOS7,SL6 release
4.8.5September 10, 2019CentOS7,SL6
4.8.4July 24, 2019CentOS7,SL6
4.8.3July 22, 2019CentOS7,SL6
4.8.2March 11, 2019CentOS7,SL6
4.8.1December 12, 2018CentOS7 release
4.8.0November 29th, 2018CentOS7, SL6 release
4.7.2October 2nd, 2018CentOS7, SL6 fix
4.7.1July 27th, 2018CentOS7, SL6 fix
4.7.0July 11th, 2018CentOS7, SL6 release
4.6.1March 14th, 2018CentOS7, SL6 release
4.6.0December 18th, 2017CentOS7, SL6 release
4.5.0August 10th, 2017CentOS7, SL6 release
4.4.2April 4th, 2017CentOS7, SL6
4.4.1March 24th, 2017CentOS7, SL6 release
4.4.0March 23rd, 2017CentOS7, SL6 release
4.3.2December 5, 2016CentOS7, SL6 update
4.3.1November 23, 2016CentOS7, SL6 update
4.3.0November 10, 2016CentOS7, SL6 release
4.2.1September 21, 2016CentOS7, SL6 update
4.2.0August 4, 2016CentOS7, SL6 update
4.1.1June 27, 2016CentOS7, SL6 update
4.1.0May 25, 2016CentOS7, SL6 update
4.0.0January 15, 2016CentOS7 release

Unified Middleware Distribution 3 and before

All the product released in UMD-3 have been supported until May 2014. You can find UMD3 and UMD2 releases on the EGI Repository

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 weeksRelease 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 weekRelease 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 weekCompose 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-1 weekPrepare a release candidate.

At least one Release Candidate (RC) will be prepared for the currently provisioned UMD release including all accepted products.

  • EA sites that participated in the provisioning of this UMD release are approached to test this RC.
  • All StagedRollout EA sites are also invited to test this RC.
  • If the current RC is unacceptable, then another RC may be produced correcting the issues. This may affect the actual final release date, and is decided on a case-by-case basis.
  • If no more feedback is given for the current RC, then this RC will become the final release of the provisioned UMD release.
tPublish 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.

  • No labels