Alert.png 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.

Difference between revisions of "EGI Core activities:2015-bidding UMD quality"

From EGIWiki
Jump to navigation Jump to search
(Created page with "{{Template:Op menubar}}{{Core_services_menubar}} {{TOC_right}} '''Go back to the EGI Core Activities Bidding page...")
 
Line 7: Line 7:


= Introduction =
= Introduction =
 
The quality criteria are the functional and nonfunctional requirements that a product must fulfill to be released in UMD; these include generic requirements applicable to every product, and specific requirements applicable to the capabilities supported by a component.
The Staged Rollout is a procedure by which certified updates of the supported middleware are first tested by Early Adopter (EA) sites before being made available to all sites through the production repositories. This procedure permits to test an update in a production environment that exposes the product to more heterogeneous use cases than the certification and verification phase. This allows the discovery of potential issues and the addition of corresponding mitigation information to the UMD release notes.


= Technical description =
= Technical description =

Revision as of 14:02, 1 July 2015

Main EGI.eu operations services Support Documentation Tools Activities Performance Technology Catch-all Services Resource Allocation Security


EGI Core services menu: Services PHASE I Services PHASE II Services PHASE III Bids Payments Travel procedure Performance



Go back to the EGI Core Activities Bidding page.

  • Service name:


Introduction

The quality criteria are the functional and nonfunctional requirements that a product must fulfill to be released in UMD; these include generic requirements applicable to every product, and specific requirements applicable to the capabilities supported by a component. The Staged Rollout is a procedure by which certified updates of the supported middleware are first tested by Early Adopter (EA) sites before being made available to all sites through the production repositories. This procedure permits to test an update in a production environment that exposes the product to more heterogeneous use cases than the certification and verification phase. This allows the discovery of potential issues and the addition of corresponding mitigation information to the UMD release notes.

Technical description

Coordination

Operations

Maintenance

Support

Service level targets

Effort