End Of Life

Description

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.

Actions

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

  • Run the following end of life script from bodhi backend

    bodhi releases edit --name F21 --state archived

Warning

Due to a bug in Bodhi, it is critical that Bodhi processes be restarted any time bodhi releases create or bodhi releases edit are used.

PackageDB

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

Bugzilla

Docs tasks

  • any?

Badges tasks

  • Update the cold undead hands badge.

    • In order to do this, you need to be in the sysadmin-badges group and the gitbadges group. If you’re not, just email those two groups at sysadmin-badges-members@fedoraproject.org and gitbadges-members@fedoraproject.org. Tell them that they need to update this badge and point them to these instructions.

    • Clone the repo with `` $ git clone ssh://git@pagure.io/fedora-badges-assets.git``

    • Edit rules/you-can-pry-it-from-my-cold-undead-hands.yml and add the EOL release to the list in the trigger section on line 19.

    • Push that back to Pagure.

    • Push the rule change out live to our servers by logging into batcave and running the manual/push-badges.yml playbook. https://infrastructure.fedoraproject.org/cgit/ansible.git/tree/playbooks/manual/push-badges.yml

    • All done.

Cloud tasks

Note

FIXME: This needs updating, I’m pretty sure we need to do something with fedimg here

Taskotron tasks

File Taskotron ticket and ask for the EOL’d release support to be removed.

Final announcement

  • from releng to f-announce-l

    • on EOL date if at all possible

    • link to previous reminder announcement (use HTTPS)

Announcement content

  • As of the <eol_date>, Fedora X has reached its end of life for updates and support. No further updates, including security updates, will be available for Fedora X. A previous reminder was sent on <announcement_daet> [0]. Fedora X+1 will continue to receive updates until approximately one month after the release of Fedora X+3. The maintenance schedule of Fedora releases is documented on the Fedora Project wiki [1]. The Fedora Project wiki also contains instructions [2] on how to upgrade from a previous release of Fedora to a version receiving updates.

    <your_name>.

    [0]<url to the announcement from announce@lists.fedoraproject.org list> [1]https://fedoraproject.org/wiki/Fedora_Release_Life_Cycle#Maintenance_Schedule [2]https://getfedora.org/

Note

All dates should follow xxth of month year format.(Example: 19th of July 2016)

Update eol wiki page

https://fedoraproject.org/wiki/End_of_life update with release and number of days.

Verification

Note

FIXME: This section needs some love

Consider Before Running

  • Resource contention in infrastructure, such as outages

  • Extenuating circumstances for specific planned updates, if any

  • ot