From Fedora Project Wiki
No edit summary |
(Redo this with the proper template) |
||
| Line 1: | Line 1: | ||
{{draft}} | |||
== Description == | == Description == | ||
<!-- Put a description of the task here. --> | <!-- Put a description of the task here. --> | ||
Each release of Fedora is maintained as laid out in the [[Fedora_Release_Life_Cycle#Maintenance_Schedule | 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 == | == Action == | ||
<!-- | <!-- Use headings to list out tasks in some semblance of chronological order, then flesh them out... I don't know them all, just guessing. --> | ||
=== Set date === | |||
* FESCo responsibility | |||
** Should follow guidelines of [[Fedora_Release_Life_Cycle#Maintenance_Schedule | 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 | |||
=== Koji tasks === | |||
=== Bodhi tasks === | |||
=== QA tasks === | |||
* Bugzilla? | |||
=== Docs tasks === | |||
* any? | |||
=== Final announcement === | |||
* from FPL to f-announce-l | |||
** on EOL date if at all possible | |||
** link to previous reminder announcement | |||
== Verification == | == Verification == | ||
| Line 10: | Line 37: | ||
== Considerations == | == Considerations == | ||
<!-- Create a list of things to keep in mind when performing action. --> | <!-- Create a list of things to keep in mind when performing action. --> | ||
* Resource contention in infrastructure, such as outages | |||
* Extenuating circumstances for specific planned updates, if any | |||
* other? | |||
<!-- Be sure to remove the Category:Template link below. Keep the RelEng SOP category link. --> | <!-- Be sure to remove the Category:Template link below. Keep the RelEng SOP category link. --> | ||
[[Category:Release Engineering SOPs]] | [[Category:Release Engineering SOPs]] | ||
Revision as of 15:40, 18 December 2009
This page is a draft only
It is still under construction and content may change. Do not rely on the information on this page.
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
Koji tasks
Bodhi tasks
QA tasks
- Bugzilla?
Docs tasks
- any?
Final announcement
- from FPL to f-announce-l
- on EOL date if at all possible
- link to previous reminder announcement
Verification
Considerations
- Resource contention in infrastructure, such as outages
- Extenuating circumstances for specific planned updates, if any
- other?