Production Release Criteria
Note that this twiki contains a draft version of the Production Release Criteria to be approved by PEB.
Latest approved version of this document |
DRAFT |
Introduction
The Producton Release criteria defines the minimum set of criteria considered to be mandatory in a component release scheduled for production. The criteria will be checked by QC who will write a QC report informing about the compliance with the criteria. This check takes place once the component release has been certified by the PT as described in the
Change Management Policy. The Production release criteria may change throughout the lifetime of the project. Changes will be agreed with PEB and QC, and announced to PTs.
QC Verification Report
The acceptance criteria is checked by QC for every certified component release. The review of the acceptance criteria is reported in the QC report. A template can be found below.
********************
EMI QC report
********************
- Component:
- Savannah task:
- EMI Major Release:
- Platform:
- Author:
- Date:
*************
Summary
*************
List of RfCs:
- Available [ yes/no ]
ETICS configuration and VCS TAG:
- Available [ yes/no ]
List of packages:
- Binary packages [ yes/no ]
- Binary tarballs [ yes/no ]
- Souce packages [ yes/no ]
- Souce tarballs [ yes/no ]
Test Report:
- Available at least with:
- Unit tests [ yes/no ]
- Deployment tests [ yes/no ]
- Basic Functionality tests [ yes/no ]
- Automatic Regression tests if any [ yes/no ]
- Remarks
Release Notes:
- Available [ yes/no ]
- Structure OK [ yes/no ]
- Contents OK [ yes/no ]
Minimum Required Documentation URLs:
- Available [ yes/no ]
- Up to date [ yes/no ]
Certification Report:
- Available [ yes/no ]
- Complete for all sections [ yes/no ]
- Remarks
Change Management Criteria
Every component release must be tracked in a component release task created by the release manager in the
EMI release tracker
. PTs must fill in the remaining fields not provided by the release manager.
All the changes included in the component release must be tracked in an RfC in the PT tracking tool. All the RfCs must be attached to the component release task.
The details of component release tasks and RfCs can be found in the
Change Management Policy.
Integration and Configuration criteria
Every component release 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 in the nightly build of the release candidate project configuration.
For more details on building in ETICS, please check the [[]https://twiki.cern.ch/twiki/bin/view/EMI/EmiSa2ConfigurationIntegrationPolicy][Configuration and Integration Policy]].
Packaging criteria
Every component release must include a link to all the new packages in all supported packaging formats.
For more details on packaging, please check the
Packaging Policy.
Testing criteria
Every component release task must include a link to the test plan of the component. The minimum set of tests that are mandatory at this stage of the project are:
- Unit Tests
- Deployment Tests
- Basic Functionality Tests
- Any existing automatic regression tests
Every component release task must attach the test report for the component including the test results of the mentioned set of tests.
For more details on testing, please check the
Testing Policy.
Documentation criteria
Every component release task must include the release notes and a set of links to the Minimum Required Documentation. At this stage of the project, the Minimum Required Documentation must comprise (without including the test plan already discussed in a previous section):
- User guide
- Installation guide
- Service Reference Card, when the component is a service.
For more details on documentation, please check the
Documentation Policy.
Certification criteria
Every component release must include a link to the certification report.
For more details on certification, please check the
Certification Policy.
--
MariaALANDESPRADILLO - 06-Dec-2010