From Fedora Project Wiki

(Add mailing list links and correct test-announce list name)
(Adjust mailing list url's)
Line 20: Line 20:
#* No subsequently unfavorable test results will reverse this decision.
#* 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
# Email is sent to the following email lists announcing that the release has been declared ''GOLD'' by the meeting organizer
#* logistics@lists.fedoraproject.org
#* [http://lists.fedoraproject.org/pipermail/logistics/ logistics@lists.fedoraproject.org]
#* fedora-devel-announce@redhat.com
#* [https://www.redhat.com/mailman/listinfo/fedora-devel-announce fedora-devel-announce@redhat.com]
#* fedora-test-announce@lists.fedoraproject.org
#* [http://lists.fedoraproject.org/pipermail/test-announce/ test-announce@redhat.com]
# Staging to Fedora mirrors begins and cannot be reversed even if additional bugs are found
# Staging to Fedora mirrors begins and cannot be reversed even if additional bugs are found


== Contingency Plan ==
== Contingency Plan ==
If the release criteria are not met the release cannot be declared ''GOLD'' and the complete release slips by one week.
If the release criteria are not met the release cannot be declared ''GOLD'' and the complete release slips by one week.

Revision as of 21:03, 7 December 2009

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

  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 unaimously 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 and the complete release slips by one week.