This document outlines the procedure for performing end-of-life (EOL) activities.


This process occurs four weeks after the release of Fedora Linux N+2.


Bug closure

Close open bugs using the fedora_bz.py script.

For example, to close Fedora Linux 37 bugs: ./fedora_bz.py eolclose 37

The script will read the EOL date from Bodhi, or you can override it, e.g. ./fedora_bz.py eolclose --date=2023-12-05 37.

You can re-run the script to verify that all bugs are closed (it should change 0 bugs).

This script will take a while to run. Execute it from a machine with stable power and networking. If it dies, you can re-run it and it should pick up where it left off.

The script closes all "Fedora" and "Fedora Container Images" bugs for the EOL release which are still open, unless they have the Tracking keyword. This Bugzilla query is similar to the one it uses (if you want to examine the list before running the script).

Reopening bugs

If you get a request to re-open a bug, do that as a service to the users.

Update product description

Adjust the wording of the Fedora product in Bugzilla to reflect the EOL.

Bugs related to the components of the Fedora distribution. If you are reporting a bug
against a stable release or a branched pre-release version, please select that
version number. The currently maintained released versions are: Fedora N-1, Fedora N.
If you have a bug to report against the daily development tree (rawhide), please choose
'rawhide' as the version.

For more information about filing a bug against Fedora packages, see

Disable EOL version

  1. Disable the EOL release in the

Wiki and website edits

  1. Update the index.html page on the web view of the schedule.

  2. Update the releases docs

    1. Update the Releases page (or really, the nav.adoc sidebar).

    2. Add the EOL version and date to the End of Life page.

Product Pages

Set the release to "Unsupported" in Product Pages. Do not unpublish the release.