Release No-Go SOP


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


  1. Follow the Release delay SOP.

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

  3. File a releng issue requesting update of the <VERSION-2> release’s EOL date in Bodhi.