From Fedora Project Wiki
(update criteria links to point to f15) |
m (Add to category QA SOPs) |
||
| Line 1: | Line 1: | ||
{{header|qa}} | |||
Before each public release Development, QA, and Release Engineering meet to determine if the release criteria are met for a particular release. This meeting is called the: '''Go/No-Go Meeting'''. | Before each public release Development, QA, and Release Engineering meet to determine if the release criteria are met for a particular release. This meeting is called the: '''Go/No-Go Meeting'''. | ||
Verifying that the Release criteria are met is the responsibility of the [[QA|QA Team]]. Release Criteria are set for each public release and are found at the following links: | Verifying that the Release criteria are met is the responsibility of the [[QA|QA Team]]. Release Criteria are set for each public release and are found at the following links: | ||
* [[ | * [[Fedora_{{FedoraVersionNumber|next}}_Alpha_Release_Criteria | Alpha]] | ||
* [[ | * [[Fedora_{{FedoraVersionNumber|next}}_Beta_Release_Criteria | Beta]] | ||
* [[ | * [[Fedora_{{FedoraVersionNumber|next}}_Final_Release_Criteria | Final]] | ||
== Meeting Organization == | == Meeting Organization == | ||
| Line 27: | Line 29: | ||
== Contingency Plan == | == Contingency Plan == | ||
If the release criteria are not met the release cannot be declared ''GOLD'', the complete release slips by one week. | If the release criteria are not met the release cannot be declared ''GOLD'', the complete release slips by one week. | ||
[[Category:QA_SOPs]] | |||
Revision as of 14:27, 21 March 2011
Before each public release Development, QA, and Release Engineering meet to determine if the release criteria are met for a particular release. This meeting is called the: Go/No-Go Meeting.
Verifying that the Release criteria are met is the responsibility of the QA Team. Release Criteria are set for each public release and are found at the following links:
Meeting Organization
- The meeting facilitator sends an email announcement three days before the meeting, specifiying the meeting location and time:
- At the start of the meeting representatives from Development, Release Engineering, and Quality Assurance should be clearly identified
Meeting Outcomes
- Decision as to whether the release is GOLD.
- If the release criteria are met the release is declared GOLD.
- If the release criteria are not met, the release is delayed by one week.
- Release is unanimously declared GOLD by a representative from Development, Release Engineering, and Quality Assurance.
- Once a release has been declared GOLD (release criteria satisfactorily met) its status cannot be changed.
- No subsequently unfavorable test results will reverse this decision.
- Email is sent to the following email lists announcing that the release has been declared GOLD by the meeting organizer.
- Staging to Fedora mirrors begins and cannot be reversed even if additional bugs are found.
Contingency Plan
If the release criteria are not met the release cannot be declared GOLD, the complete release slips by one week.