...

If products are integrated in CMD, you will see them listed in the following page: https://wiki.egi.eu/wiki/EGI_Cloud_Middleware_Distribution_products CMD Products

If products are integrated in UMD, you will see them listed at https://wiki.egi.eu/wiki/UMD_products_ID_cardsin the Product ID Cards

...

Initial activities - Joining UMD Release Team

To be included in UMD Release Team (URT) the interested Technology Provider should provide following information:

1. Name of the Product team
2. Contacts (support email address, web site address)
3. Name and contact details of the Component Development Team Leader
4. Description of the Component/Product and its Purpose
5. Release channels for the product:
   • where to find the packages and their updates
   • components/products should be provided in the native packaging format of the OSs supported in UMD (i.e. as rpms for SL5 & SL6, and deb packages for Debian)
   • packages should have dependencies on packages provided by the respective OS and EPEL (for Fedora/SL family)
   • any other external dependencies should be also provided or referenced as being provided by other Technology Providers part of the URT team
6. Documentation references – installation & configuration guides, release notes, known issues and troubleshooting, reference cards
7. Which releases, versions, are going to be released in UMD and with which support calendar
8. Communicate if TP have information on sites already deploying the software that can be interested in acting as Early Adopters in the staged rollout phase.

All information will be included into UMD products ID card

To send join request please read: How to join

With the help of the EGI UMD Release Team (URT), the following steps need to be performed:

1. Create GGUS Support Unit to receive and handle incidents (define level of quality of support)
2. Agree on Technical Provider Underpinning Agreement (TP UA) with EGI.eu
3. Subscribe to the UMD Release team mailing list

First release

This section describe workflow of adding first release: 

1. First packages are pulled into the untested area of the UMD repositories
2. UMD team starts the first verification, involving the TP, in order to:
   • understand how deployment should be done
   • check the present Quality Criteria definitions and determine if the common criteria apply or not, if specific criteria are needed for the new products
   • update the Verification and Staged Rollout Reports template, if needed
   • provide workarounds or new versions of the packages if issues are discovered
3. after a successful verification packages are moved in the testing area of the UMD repos and the Early Adopter sites/sites are contacted for deploying the new release, and after a grace period of few days, to provide the Staged-Rollout report with the results of these testing phase.
   • If issues are discovered – if possible workarounds will be documented, otherwise the product is rejected and a new version should be provided (fixing the issues)
4. After a successful Staged-Rollout packages are moved in the UMD Store area, and will become part of the next available UMD release.

Ongoing activities

Once Technology Provider join UMD Release Team the following activities should be performed each time new version of product has been released.

Software Delivery

Goal: Submitting new software releases

...

• Send e-mail to URT team
• Update the information on the URT meeting agendas

...