From Fedora Project Wiki

Revision as of 14:41, 24 February 2016 by Kparal (talk | contribs) (→‎Taskotron tasks: fix link)

This page is deprecated
All Fedora Release Engineering Documentation has moved here with source hosted along side the code in the releng pagure repository


Each release of Fedora is maintained as laid out in the maintenance schedule. At the conclusion of the maintenance period, a Fedora release enters end of life status. This procedure describes the tasks necessary to move a release to that status.


Set date

  • Releng responsibilities:
    • Follow guidelines of maintenance schedule
    • Take into account any infrastructure or other supporting project resource contention
    • Announce the closure of the release to the package maintainers.

Reminder announcement

  • from rel-eng to f-devel-announce, f-announce-l, including
    • date of last update push (if needed)
    • date of actual EOL

Koji tasks

  • disable builds by removing targets
koji remove-target f19
koji remove-target f19-updates-candidate
  • Purge from disk the signed copies of rpms that are signed with the EOL'd release key

Bodhi tasks

  • In puppet, set the push scripts to not push the old release:
diff --git a/configs/system/fedora-updates-push
index 2c05334..39e25f7 100755
--- a/configs/system/fedora-updates-push
+++ b/configs/system/fedora-updates-push
@@ -3,7 +3,7 @@

-for rel in 11 12 13; do
+for rel in 12 13; do

 rsync -rlptDvHh --delay-updates $RSYNC_OPTS --exclude "repodata/*" \
         $SOURCE/f$rel-updates/ $DEST/$rel/ &>/dev/null
@@ -11,7 +11,7 @@ rsync -rlptDvHh --delay-updates $RSYNC_OPTS --delete
--delete-after \
         $SOURCE/f$rel-updates/ $DEST/$rel/ &>/dev/null

-for rel in 11 12 13; do
+for rel in 12 13; do

 rsync -rlptDvHh --delay-updates $RSYNC_OPTS --exclude "repodata/*" \
         $SOURCE/f$rel-updates-testing/ $DEST/testing/$rel/ &>/dev/null
  • Take a bodhi database snapshot for good measure
[masher@releng04 bodhi]$ bodhi-pickledb save 
  • Remove all updates and comments associated with the release
[masher@releng04 bodhi]$ bodhi-rmrelease F19


Set the release to be End of Life in the PackageDB. A admin can login and do this from the web interface.

Source Control (git)

  • Branches for new packages in git are not allowed for distribution X after the Fedora X+2 release. New builds are no longer allowed for EOL Fedora releases.

Fedora Program Manager Tasks


Docs tasks

  • any?

Badges tasks

Cloud tasks

Taskotron tasks

  • File a Taskotron ticket and ask for the EOL'd release support to be removed. (Log in to Phabricator using your email address).

Final announcement

  • from releng to f-announce-l
    • on EOL date if at all possible
    • link to previous reminder announcement (use HTTPS)

Announcement content

Update eol wiki page update with release and number of days.


Consider Before Running

  • Resource contention in infrastructure, such as outages
  • Extenuating circumstances for specific planned updates, if any
  • ot