End of life SOP

This page is a draft only
It is still under construction and content may change. Do not rely on the information on this page.

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.

Action

Set date

• FESCo responsibility
  • Should follow guidelines of maintenance schedule
  • Take into account any infrastructure or other supporting project resource contention

Reminder announcement

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

PackageDB

Set the release to be End of Life in the PackageDB. Currently, that's done with the following db query:

update collection set statuscode = 9 where name = 'Fedora' and version = '11'; 

Source Control (CVS)

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

Bugzappers Tasks

• Close all open bugs
• End of life process

Docs tasks

• any?

Final announcement

• from FPL to f-announce-l
  • on EOL date if at all possible
  • link to previous reminder announcement

Announcement content

• Consider this EOL announcement from openoffice.org
  • Note FAQ

Consider Before Running

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