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.

PackageDB

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

-- For the Package ACLs
update collection set statuscode = 9 where name = 'Fedora' and version = '11';
-- For the Application Database
select * from repos where shortname ~'^F-11-.*' and active = true;
-- Check that only repositories for the EOL repo are listed.
BEGIN;
update repos set active = false where shortname ~ '^F-11-*' and active = true;
-- Make sure the same number of records were modified as previous select
COMMIT;

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.

AutoQA

The AutoQA project maintains a config file (repoinfo.conf) that describes available package repositories and their inheritance. When a Fedora release is EOL'd, the repoinfo.conf file needs to be updated. Please file an autoqa ticket to modify the repoinfo.conf file to remove pointers to the EOL'd release.