Difference between revisions of "EGI Cloud Middleware Distribution process"
Jump to navigation
Jump to search
Line 28: | Line 28: | ||
|- | |- | ||
| 3 | | 3 | ||
| Quality Verification | | Quality Verification starts | ||
| QC Verifier | | QC Verifier | ||
| the QC verifier starts the verification process | | the QC verifier starts the verification process | ||
| '''one month'''; after a month with the verification not yet started: | | in '''one month''' after the creation of the RT ticket; after a month with the verification not yet started: | ||
* the RT ticket will be updated with an explanation for the delay | * the RT ticket will be updated with an explanation for the delay | ||
* the status will be changed to "Delayed" [*] | * the status will be changed to "Delayed" [*] |
Revision as of 11:35, 4 October 2016
CMD menu: | Overview | Products | Process | Release schedule |
Description of the process
Step | Action | Action on | Description | Timeline |
---|---|---|---|---|
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 SR Manager | inject the product release in the EGI SW provisioning infrastructure:
|
5 working days |
3 | Quality Verification starts | QC Verifier | the QC verifier starts the verification process | in one month after the creation of the RT ticket; after a month with the verification not yet started:
|
4 |
[*] Being in the "Delayed" status RT tickets can be identified as problematic by the UMD team and followed up more closely.
- The RT ticket is in "Verification" status
- This means that the UMD team is verifying the product in the testbed.
- An RT ticket cannot stay longer than one week in verification
- After one week, if it has not been verified it is moved to "Delayed" status, with an explanation of the reasons of the delay. PT to be informed as well.
- Product is in "Staged Rollout" Status
- The product is announced to the early adopters testing in staged rollout the product.
- #* RT cannot stay longer than one month in the "Staged Rollout" status
- After one month, if it has not been tested in staged rollout it is moved to "Delayed" status, with an explanation of the reasons of the delay. PT to be informed as well.
- After the staged rollout product is ready to be included in the next UMD release