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.

  1. Select all bugs for Fedora version N-2 that are not closed and save the results as a CSV file.

    1. Do this for both the Fedora product and the Fedora Container Images product.

    2. Exclude bugs with the Tracking keyword.

    3. This Bugzilla query will give you the right results (just update the version).

  2. Run the fedora_bz.py script against it.

    1. For example, to close Fedora Linux 34 bugs with an EOL date of 7 June 2022: ./fedora_bz.py --release 34 --date 2022-06-07 eolclose bugs-2022-06-07.csv

  3. Re-run the Bugzilla query to verify that all bugs are closed.

  4. Close any still-open bugs.

This script will take a while to run. Execute it from a machine with stable power and networking.

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.