For each product to be included in CMD, the Technology Provider is asked to:
- provide a complete Product ID Card description, which will be used to contact the Technology Provider in case of requests for information, security related events/issues, proposals, and any other issues
- create GGUS Support Unit to receive and handle incidents (define level of quality of support)
- agree on Technical Provider Underpinning Agreement (TP UA) with EGI.eu, for a single product or for a group of products
After performing the steps above, your product can be added to CMD releases following the middleware distribution process.
If you need details on the EGI Software Provisioning process, please find them at the following link: https://wiki.egi.eu/wiki/EGI_Software_Component_Delivery
If you need information or details on CMD, please write to operations at egi.eu.
Plans and roadmaps
|1||Submission||Technology Provider||submit a GGUS ticket, assigned to Support Unit "EGI Software provisioning support", providing them with the following information:||at TP convenience|
|2||Injection||UMD Team SR Manager||inject the product release in the EGI SW provisioning infrastructure:||5 working days|
|3||Quality Verification starts||UMD Team QC Verifier||the QC verifier starts the verification process, switching the status of the RT ticket from "Unverified" to "Verification"||the QC verification must start in one month after the creation of the RT ticket; after a month with the verification not yet started:|
|4||Quality Verification execution||UMD Team QC Verifier||the UMD team is verifying the product in the testbed; after the verification process is completed, the RT ticket status is switched from "Verification" to "Staged Rollout"||an RT ticket cannot stay longer than one week in verification; after one week with the verification not yet completed:|
|5||Staged Rollout||UMD Team Staged Rollout manager||The product is announced to the early adopters testing the product in staged rollout.||RT tickets cannot stay longer than one month in the "Staged Rollout" status; after a month with the staged rollout not yet completed:|
|6||Inclusion in the next release||Release manager||include the product in the next release||see the CMD release schedule|