Production Release Criteria

Note that this twiki contains a new version of the Production Release Criteria which is still under preparation. The latest approved version is accesible in the PDF file. Check the Logbook for more details in the new version.

Latest version of this document

1. Introduction

The Producton Release criteria defines the minimum set of criteria considered to be mandatory for a new product version to be released in the EMI production repository. It summarises what it is described in each policy as a mandatory requirement.

The criteria will be checked by QC who will write a verification report informing about the compliance with the criteria. This check takes place once the associated release task [R1] for the new product version has been certified by the PT, as described in the Change Management Policy [R2].

In case some of the defined criteria is not met, PTs should clearly justify why in the Remarks sections of the Testing or Certification reports attached to the release task. QC will then evaluate the given explanations on a case by case basis.

2. Production Release Criteria

2.1. Change Management Criteria

New versions of a product must be tracked in a release task created by the release manager in the EMI release tracker [R1]. PTs must fill in the remaining fields not provided by the release manager.

All the changes included in the new version of the product must be tracked in an RfC in the PT tracking tool. All the RfCs must be specified in the List of RfCs field in the release task.

Other changes coming from development tasks [R10], must be also linked to the release task using the Dependencies field in Savannah.

All the details on how to fill in and use release tasks and RfCs must be followed as specified in the Change Management Policy [R2].

2.2. Integration and Configuration criteria

New versions of a product must have a corresponding ETICS component (and subsystem) configuration in ETICS. The component configuration must contain a tag of the code. The configuration must build without errors:

  • For EMI major releases: in the development project configuration emi_B_X_dev.
  • For EMI updates: in the project configurations emi_R_X_rc and emi_R_X_prod.

All the details on how to build with ETICS must be followed as specified in the Configuration and Integration Policy [R5].

2.3. Packaging criteria

New versions of a product must include all new packages in all supported packaging formats.

For SL5/x86_64, the mandatory package formats are: rpm, src.rpm, binary tarballs and source tarballs.

For Debian platforms, this section will be updated in the upcoming months.

All the details on packaging must be followed as specified in the Packaging Policy [R6].

2.4. Testing criteria

New versions of a product must run and report about the results of at least the following type of tests:

  • Unit Tests
  • Deployment Tests (Clean Installation and Upgrade)
  • Basic Functionality Tests
  • Any existing and automated Regression Tests

The results of the tests must be reported in the Test Report that must be attached to the release task. The release task must also contain a link to the Test Plan of the product.

All the details about testing must be followed as specified in the Testing Policy [R7].

2.5. Documentation criteria

At least the following documents must be provided by PTs:

  • General Documentation
    • Release Notes
    • Functional description
  • User Documentation
    • User guide
    • Client Installation and Configuration
  • System Administrator Documentation
    • System Administrator Guide
    • Service Reference Card

All the details about documentation must be followed as specified in the Documentation Policy [R8].

2.6. Certification criteria

New versions of a product must be certified and the certification report must be attached to the corresponding release task.

All the details about certification must be followed as specified in the Certification Policy [R9].

2.7. Testbed Deployment criteria

New versions of a product must be successfully deployed in the EMI Testbed. Nagios probes and any other tests must also run successfully to consider the Testbed deployment successful.

3. EMI QA Dashboard and QC Verification Report

The Production Release Criteria is checked by QC for every certified release task with the help of the EMI QA Monitoring Dashboard [R3]. The Dashboard presents the certification and test report answers and compares them to what has been actually found in ETICS and the release task. The Dashboard automatically generates the Verification Report. The Verification Report summarises the review of the Production Release Criteria. A template of the Verification Report can be found in the QC Verification twiki [R4].

4. Table of References

Reference URL
R1 EMI Release Tracker
R2 EMI Change Management Policy
Change Management Policy
R3 EMI QA Monitoring Dashboard
R4 EMI QC Verification
R5 EMI Integration and Configuration Policy
R6 EMI Packaging Policy
R7 EMI Testing Policy
R8 EMI Documentation Policy
R9 EMI Certification Policy
R10 EMI Development tracker

5. Changelog

v2.0 (In progress)

  • 22.08.2011:
    • Added development tasks in change management criteria.
    • Added the correct ETICS configs in the builds specified in the Config and Integration criteria.
  • 03.08.2011 :
    • Apply Release Manager feedback.
    • Change component with release where applicable.
    • Review all existing criteria per policy and make sure it's aligned with the latest versions of each policy.
    • Added Testbed Deployment Criteria.


  • First version that has been used until 03.08.2011 when the document has been reviewed for EMI 2.

This topic: EMI > WebHome > EmiProjectStructure > SA2 > SA2-internal > TSA22 > SQAP > ProductionReleaseCriteria
Topic revision: r15 - 2011-08-22 - MariaALANDESPRADILLO
This site is powered by the TWiki collaboration platform Powered by PerlCopyright & 2008-2023 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
or Ideas, requests, problems regarding TWiki? use Discourse or Send feedback