Difference between revisions of "UMDQualityCriteria"
Line 3: | Line 3: | ||
All the software included in the Unified Middleware Distribution (UMD) must meet a set of Quality Criteria defined by EGI. The Quality Criteria can be classified into generic criteria, i.e. criteria which sould hold for any component of the UMD, and specific criteria, i.e. criteria valid for a particular component only. | All the software included in the Unified Middleware Distribution (UMD) must meet a set of Quality Criteria defined by EGI. The Quality Criteria can be classified into generic criteria, i.e. criteria which sould hold for any component of the UMD, and specific criteria, i.e. criteria valid for a particular component only. | ||
Any Technology Provider (TP) willing to have their software verified by the SA2 team should carefully read them. | |||
=== QC Documents === | |||
The Quality Criteria (QC) is written following the classification of capabilities defined in can the [https://documents.egi.eu/secure/ShowDocument?docid=100 UMD RoadMap], one document for each type of capability: | |||
* Generic QC, for all software | * Generic QC, for all software | ||
* Functional Capabilities QC | * Functional Capabilities QC | ||
Line 9: | Line 13: | ||
* Operational Capabilities QC | * Operational Capabilities QC | ||
Take into account that a software component may cover QC specified in more than one of those documents. | |||
== QC Roadmap == | |||
QC definition is a continuous process driven by the requirements of users and operations communities, however the verification of new software releases will be done against fixed releases of the QC documents. At least every 6 months a new version of the QC will be released, although more frequent releases may occur if necessary. Each new release of the QC will be announced in this page and through the TCB mailing list. Along with the announcement of each release of QC specification, a date for its use in verification will be specified. It is expected that verification will use new releases of the QC within 2 to 4 weeks from the release date. | |||
* | Each QC release will contain documentation with: | ||
* major changes introduced in the version. | |||
* deprecated criteria, if there is any. | |||
* criteria to be deprecated in next release of the QC, if any. | |||
=== Current QC Specification === | |||
<blockquote style="border-width:1px; border-style:solid; padding:0.2em;background-color:#FFFFCC"> | |||
: | In the current stage, a first complete version of Quality Criteria that covers for UMD software is undergoing. It is expected that this comprehensive QC for all components will be available on '''early February 2011'''. Drafts of these QC is available at DocDB: [https://documents.egi.eu/public/ShowDocument?docid=240 QC document]. | ||
</blockquote> | |||
=== Future Releases === | |||
==== | {| class="wikitable sortable" style="border:1px solid black" cellspacing="0" cellpadding="3" border="1" | ||
|- style="background:Lightgray" align="left" | |||
: | ! DocDB link | ||
! Expected Release Date | |||
! Expected Verification Date | |||
! More information | |||
|- | |||
| [https://documents.egi.eu/public/ShowDocument?docid=240 240] | |||
| 01. 02. 2011 | |||
| 01. 02. 2011 | |||
| [[EGI-InSPIRE:UMDQualityCriteria:QC1 | release notes]] | |||
|- | |||
| - | |||
| 01. 08. 2011 | |||
| 15. 08. 2011 | |||
| - | |||
|} | |||
=== Past QC releases === | |||
There are no past QC releases. | |||
[[Category:WP5-SA2]] | [[Category:WP5-SA2]] |
Revision as of 13:47, 9 December 2010
UMD Quality Criteria
All the software included in the Unified Middleware Distribution (UMD) must meet a set of Quality Criteria defined by EGI. The Quality Criteria can be classified into generic criteria, i.e. criteria which sould hold for any component of the UMD, and specific criteria, i.e. criteria valid for a particular component only.
Any Technology Provider (TP) willing to have their software verified by the SA2 team should carefully read them.
QC Documents
The Quality Criteria (QC) is written following the classification of capabilities defined in can the UMD RoadMap, one document for each type of capability:
- Generic QC, for all software
- Functional Capabilities QC
- Security Capabilities QC
- Operational Capabilities QC
Take into account that a software component may cover QC specified in more than one of those documents.
QC Roadmap
QC definition is a continuous process driven by the requirements of users and operations communities, however the verification of new software releases will be done against fixed releases of the QC documents. At least every 6 months a new version of the QC will be released, although more frequent releases may occur if necessary. Each new release of the QC will be announced in this page and through the TCB mailing list. Along with the announcement of each release of QC specification, a date for its use in verification will be specified. It is expected that verification will use new releases of the QC within 2 to 4 weeks from the release date.
Each QC release will contain documentation with:
- major changes introduced in the version.
- deprecated criteria, if there is any.
- criteria to be deprecated in next release of the QC, if any.
Current QC Specification
In the current stage, a first complete version of Quality Criteria that covers for UMD software is undergoing. It is expected that this comprehensive QC for all components will be available on early February 2011. Drafts of these QC is available at DocDB: QC document.
Future Releases
DocDB link | Expected Release Date | Expected Verification Date | More information |
---|---|---|---|
240 | 01. 02. 2011 | 01. 02. 2011 | release notes |
- | 01. 08. 2011 | 15. 08. 2011 | - |
Past QC releases
There are no past QC releases.