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.
|Release||Release date||Supported OS||Announcement||Notes|
|4.12.5||November 23rd, 2020||CentOS7,SL6||https://repository.egi.eu/UMD/4.12.5.html||Fix|
|4.12.4||November 20th, 2020||CentOS7,SL6||https://repository.egi.eu/UMD/4.12.4.html||Fix|
|4.12.3||November 18th, 2020||CentOS7,SL6||https://repository.egi.eu/UMD/4.12.3.html||Update|
|4.12.2||October 19th, 2020||CentOS7,SL6||https://repository.egi.eu/UMD/4.12.2.html||Fix|
|4.12.1||October 15th, 2020||CentOS7,SL6||https://repository.egi.eu/UMD/4.12.1.html||Fix|
|4.12.0||October 13rd, 2020||CentOS7,SL6||https://repository.egi.eu/UMD/4.12.0.html||Regular|
|4.11.2||Aug 14th, 2020||CentOS7,SL6||https://repository.egi.eu/UMD/4.11.2.html||Emergency release|
|4.11.1||July 21st, 2020||CentOS7,SL6||https://repository.egi.eu/UMD/4.11.1.html||Emergency release|
|4.11.0||June 29th, 2020||CentOS7,SL6||https://repository.egi.eu/UMD/4.11.0.html||Regular|
|4.10.3||April 16th, 2020||CentOS7,SL6||https://repository.egi.eu/UMD/4.10.3.html||Fix|
|4.10.2||April 15th, 2020||CentOS7,SL6||https://repository.egi.eu/UMD/4.10.2.html||Emergency release|
|4.10.1||April 6th, 2020||CentOS7,SL6||https://repository.egi.eu/UMD/4.10.1.html||Fix release|
|4.10.0||March 26, 2020||CentOS7,SL6||https://repository.egi.eu/UMD/4.10.0.html||Regular release|
|4.9.2||February 10, 2020||CentOS7, SL6||https://repository.egi.eu/UMD/4.9.2.html||Emergency fix for CERN Frontier|
|4.9.1||December 12, 2019||CentOS7||https://repository.egi.eu/UMD/4.9.1.html||HTCondor-CE update|
|4.9.0||November 11, 2019||CentOS7,SL6||https://repository.egi.eu/UMD/4.9.0.html||Regular release|
|4.8.5||September 10, 2019||CentOS7,SL6||https://repository.egi.eu/UMD/4.8.5.html||Update|
|4.8.4||July 24, 2019||CentOS7,SL6||https://repository.egi.eu/UMD/4.8.4.html||Fix|
|4.8.3||July 22, 2019||CentOS7,SL6||https://repository.egi.eu/UMD/4.8.3.html||Update|
|4.8.2||March 11, 2019||CentOS7,SL6||https://repository.egi.eu/UMD/4.8.2.html||Update|
|4.8.1||December 12, 2018||CentOS7||https://repository.egi.eu/UMD/4.8.1.html||Emergency release|
|4.8.0||November 29th, 2018||CentOS7, SL6||https://repository.egi.eu/UMD/4.8.0.html||Regular release|
|4.7.2||October 2nd, 2018||CentOS7, SL6||https://repository.egi.eu/UMD/4.7.2.html||Emergency fix|
|4.7.1||July 27th, 2018||CentOS7, SL6||https://repository.egi.eu/UMD/4.7.1.html||Emergency fix|
|4.7.0||July 11th, 2018||CentOS7, SL6||https://repository.egi.eu/UMD/4.7.0.html||Regular release|
|4.6.1||March 14th, 2018||CentOS7, SL6||https://repository.egi.eu/UMD/4.6.1.html||Fix release|
|4.6.0||December 18th, 2017||CentOS7, SL6||https://repository.egi.eu/UMD/4.6.0.html||Regular release|
|4.5.0||August 10th, 2017||CentOS7, SL6||https://repository.egi.eu/UMD/4.5.0.html||Regular release|
|4.4.2||April 4th, 2017||CentOS7, SL6||https://repository.egi.eu/UMD/4.4.2.html||Revision|
|4.4.1||March 24th, 2017||CentOS7, SL6||https://repository.egi.eu/UMD/4.4.1.html||Emergency release|
|4.4.0||March 23rd, 2017||CentOS7, SL6||https://repository.egi.eu/UMD/4.4.0.html||Regular release|
|4.3.2||December 5, 2016||CentOS7, SL6||https://repository.egi.eu/UMD/4.3.2.html||Revision update|
|4.3.1||November 23, 2016||CentOS7, SL6||https://repository.egi.eu/UMD/4.3.1.html||Revision update|
|4.3.0||November 10, 2016||CentOS7, SL6||https://repository.egi.eu/UMD/4.3.0.html||Regular release|
|4.2.1||September 21, 2016||CentOS7, SL6||https://repository.egi.eu/UMD/4.2.1.html||Emergency update|
|4.2.0||August 4, 2016||CentOS7, SL6||https://repository.egi.eu/UMD/4.2.0.html||Regular update|
|4.1.1||June 27, 2016||CentOS7, SL6||https://repository.egi.eu/UMD/4.1.1.html||Revision update|
|4.1.0||May 25, 2016||CentOS7, SL6||https://repository.egi.eu/UMD/4.1.0.html||Regular update|
|4.0.0||January 15, 2016||CentOS7||https://repository.egi.eu/UMD/4.0.0.html||Major 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 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-1 week||Prepare a release candidate.|
At least one Release Candidate (RC) will be prepared for the currently provisioned UMD release including all accepted products.
|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.