Release Delay SOP

The document outlines the procedure for delaying the release. Refer to the schedule contingency planning docs for when to delay future milestones.

  1. In Smartsheet, add a new milestone (if needed) and update the Current (Beta|Final) Target date milestone to have the new target date as a predecessor.

  2. Save the updated schedule to the git repository and publish to the web.

  3. Update Product Pages. If the new target date is beyond target date #1 or you have reason to believe the release will slip further, set the status to yellow. If the new target date is beyond target date #2 or you have reason to believe the release will slip further, set the status to red.

  4. 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.

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

Delay announcement emails

These are suggestions. You can and should customize them to meet specific releases and your own "voice".

Delayed due to no RC

Due to outstanding blocker bugs[1], we do not have an F<VERSION> <MILESTONE> RC. As
a result, F<VERSION> <MILESTONE> is NO-GO by default and tomorrow's Go/No-Go meeting is
cancelled.

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

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

Delayed due to No-Go decision

Due to outstanding blocker bugs[1], F<VERSION> <MILESTONE> RC<CANDIDATE> was declared NO-GO in
today's Go/No-GO meeting.

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

[1] https://qa.fedoraproject.org/blockerbugs/milestone/<VERSION>/<MILESTONE>/buglist
[2] https://meetbot.fedoraproject.org/<MEETING MINUTES URL>
[2] https://calendar.fedoraproject.org/meeting/<MEETING ID>/
[3] https://fedorapeople.org/groups/schedule/f-<VERSION>/f-<VERSION>-key-tasks.html

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