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 Process
| Technology | Software Component Delivery | Software Provisioning | UMD Middleware | Cloud Middleware Distribution | Containers Distribution | Technology Glossary |
| UMD Provisioning | | Software Provisioning Process | | UMD Release Process | | Software Provisioning Release descriptor tool | | Glossary |
EGI follows its own release schedule, publishing fixed UMD updates (monthly/quarterly). Accepted PPA (Product per Platform and Architecture) versions are stored into a staging area of the EGI Repository as delivered by the Technology Providers. When a new UMD release is to be created, the UMD Release building process collects the qualifying and compatible with each other Products from the EGI Repository and bundles them into UMD releases. That is, a UMD release is irrespective of the Technology Providers releases.
There are three types of UMD Releases:
- Base, a new major release
- Update, a subsequent minor release
- Security, an emergency release
Everything that concerns UMD Provisioning should go here:
- The main provisioning process
- The UMD release preparation process itself