Release No-Go SOP
This document outlines the procedure for when a relase is declared "no-go".
Shift to the next target milestone in the schedule.
Send an announcement email similar to the below to email@example.com, firstname.lastname@example.org, email@example.com, and firstname.lastname@example.org.
Cancel the go/no-go meeting if the "no-go" determination is made preemptively.
For the Final milestone:
Submit a pull request to the <VERSION-2> release’s fedora-release package to update the eol_date variable in the
fedora-release.specfile. You may need to request a new package build from the Release Engineering team.
Update the <VERSION-2> release schedule’s EOL date entry.
|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, 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 will be held at 1700 UTC on Thursday <DATE> in <CHANNEL>. We will aim for the <TARGET> milestone of <TARGET_DATE>. The release schedule has been updated accordingly.  https://qa.fedoraproject.org/blockerbugs/milestone/<VERSION>/<MILESTONE>/buglist  <FEDOCAL_URL>  https://fedorapeople.org/groups/schedule/f-<VERSION>/f-<VERSION>-key-tasks.html
Want to help? Learn how to contribute to Fedora Docs ›