Release No-Go SOP

Trigger/timing

This document outlines the procedure for when a relase is declared "no-go".

Procedure

  1. Shift to the next target milestone in the schedule.

  2. Update the dates in the report and office hours files.

  3. Send an announcement email similar to the below to logistics@lists.fedoraproject.org, devel-announce@lists.fedoraproject.org, test-announce@lists.fedoraproject.org, and rel-eng@lists.fedoraproject.org.

  4. Cancel the go/no-go meeting if the "no-go" determination is made preemptively.

For the Final milestone:

  1. Submit a pull request to the <VERSION-2> release’s fedora-release package to update the eol_date variable in the fedora-release.spec file. You may need to request a new package build from the Release Engineering team.

  2. Update the <VERSION-2> release schedule’s EOL date entry.

No-go announcement email

The example below is based on the case where a release is preemptively declared "no go" due to oustanding blockers. 
Due to outstanding blocker bugs[1], we do not have a current release candidate. As a result, Fedora Linux <VERSION> <MILESTONE> is NO-GO.

The next Fedora Linux <VERSION> <MILESTONE> Go/No-Go meeting[2] will be held at 1700 UTC on Thursday <DATE> in <CHANNEL>. We will aim for the <TARGET> milestone of <TARGET_DATE>. The release schedule[3] has been updated accordingly.

[1] https://qa.fedoraproject.org/blockerbugs/milestone/<VERSION>/<MILESTONE>/buglist
[2] <FEDOCAL_URL>
[3] https://fedorapeople.org/groups/schedule/f-<VERSION>/f-<VERSION>-key-tasks.html

Want to help? Learn how to contribute to Fedora Docs ›