Go No Go Meeting

From FedoraProject

(Difference between revisions)
Jump to: navigation, search
(add a bit about validation testing to the QA determination paragraph)
 
(4 intermediate revisions by 2 users not shown)
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]]. QA team's determination must be based on the [[QA:SOP_blocker_bug_process|blocker bug process]]. QA approves the release if all validation tests appropriate to the release phase (Alpha, Beta or Final) have been performed and there are no accepted blocker bugs that are unaddressed in the candidate compose. QA does not approve the release if there are any accepted blocker bugs that are unaddressed in the candidate compose or if validation testing is incomplete. There is no room for discretion in this determination. The Go/No-Go Meeting may serve as a blocker review meeting, if there are outstanding proposed blockers - as long as the necessary groups are present - in order to make the determination possible by deciding if they are accepted or rejected.
* [[Fedora_14_Alpha_Release_Criteria | Alpha]]  
+
 
* [[Fedora_14_Beta_Release_Criteria | Beta]]  
+
Release Criteria are set for each public release and are found at the following links:
* [[Fedora_14_Final_Release_Criteria | Final]]  
+
* [[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 31:
 
== 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]]

Latest revision as of 21:08, 10 August 2011

QA.png


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. QA team's determination must be based on the blocker bug process. QA approves the release if all validation tests appropriate to the release phase (Alpha, Beta or Final) have been performed and there are no accepted blocker bugs that are unaddressed in the candidate compose. QA does not approve the release if there are any accepted blocker bugs that are unaddressed in the candidate compose or if validation testing is incomplete. There is no room for discretion in this determination. The Go/No-Go Meeting may serve as a blocker review meeting, if there are outstanding proposed blockers - as long as the necessary groups are present - in order to make the determination possible by deciding if they are accepted or rejected.

Release Criteria are set for each public release and are found at the following links:

[edit] Meeting Organization

  1. The meeting facilitator sends an email announcement three days before the meeting, specifiying the meeting location and time:
  2. At the start of the meeting representatives from Development, Release Engineering, and Quality Assurance should be clearly identified

[edit] Meeting Outcomes

  1. 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.
  2. Release is unanimously declared GOLD by a representative from Development, Release Engineering, and Quality Assurance.
  3. 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.
  4. Email is sent to the following email lists announcing that the release has been declared GOLD by the meeting organizer.
  5. Staging to Fedora mirrors begins and cannot be reversed even if additional bugs are found.

[edit] Contingency Plan

If the release criteria are not met the release cannot be declared GOLD, the complete release slips by one week.