Go No Go Meeting

From FedoraProject

Revision as of 23:08, 17 May 2011 by Adamwill (Talk | contribs)

Jump to: navigation, search
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 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. There is no room for discretion in this determination.

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

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

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.

Contingency Plan

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