EOL day SOP
This document outlines the procedure for performing end-of-life (EOL) activities.
Process
Bug closure
Close open bugs.
-
Select all bugs for Fedora version N-2 that are not closed and save the results as a CSV file.
-
Do this for both the Fedora product and the Fedora Container Images product.
-
Exclude bugs with the Tracking keyword.
-
This Bugzilla query will give you the right results (just update the version).
-
-
Run the
fedora_bz.py
script against it.-
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
-
-
Re-run the Bugzilla query to verify that all bugs are closed.
-
Close any still-open bugs.
This script will take a while to run. Execute it from a machine with stable power and networking. |
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 https://docs.fedoraproject.org/en-US/quick-docs/howto-file-a-bug/
Disable EOL version
-
Disable the EOL release in the
-
Fedora product
-
Fedora Container Images product
-
Wiki and website edits
-
Update the index.html page on the web view of the schedule.
-
Update the releases docs
-
Update the Releases page (or really, the
nav.adoc
sidebar). -
Add the EOL version and date to the End of Life page.
-
Want to help? Learn how to contribute to Fedora Docs ›