Fedora Program Management/EOLRebaseSOP

End of Life & Rawhide Rebase SOP

These two processes are related to Bugzilla clean up in Fedora.

End of Life SOP

Fedora supports two maintained versions in parallel (Fn and Fn-1), older releases are no longer maintained - no bug fixes, no updates are issued. For EOL process, FPgM takes care of Bugzilla cleanup as part of House Keeping process. EOL of Fn-2 is typically 4 weeks after GA of Fn, that means release is usually supported for 13 months but based on GA of Fn, it may vary from less or more than 13 months. EOL is announced by Fedora Release Engineer on devel-announce@ mailing list (but FPgM is responsible to make sure this announcement happens on list).

There are two events:

• EOL warning
• EOL closure

EOL warning

EOL warning usually happens one day after GA unless there's serious reason why not.

1. Update query for EOL release and save CSV from Bugzilla (bottom part of the list of bugs)
2. Update message for EOL release
3. Use fedora_eol_warning.pl script with CSV generated from Bugzilla

EOL closure

The same process applies as for EOL warning. It's recommended to run query and script after last push and once Bugzilla is updated from Bodhi to avoid collisions (bug is part of query results, Bodhi changes status and script is ran with old status).

1. Update query for EOL release and save CSV from Bugzilla (bottom part of the list of bugs)
2. Update message for EOL release
3. Use fedora_close_eol.pl script with CSV generated from Bugzilla

Users has to be able to change version once the bug is closed (as CLOSED:EOL in Bugzilla).

Rawhide Rebase

Rawhide rebase is a process, where bugs reported to Rawhide during development cycle of Fn+1 are rebased to Fn+1. Exceptions are RFE and FutureFeatures + trackers. This helps to identify in which version bug was introduced and in the end, together with EOL process helps keeping Bugzilla clean (as at one point, unfixed bug is closed as EOL).

Please exclude kernel from Rawhide Rebase.