From Fedora Project Wiki
(Add link to OOo FAQ) |
m (→Considerations) |
||
| Line 39: | Line 39: | ||
<!-- Provide a method to verify the action was successful --> | <!-- Provide a method to verify the action was successful --> | ||
== | == Consider Before Running == | ||
* Resource contention in infrastructure, such as outages | * Resource contention in infrastructure, such as outages | ||
* Extenuating circumstances for specific planned updates, if any | * Extenuating circumstances for specific planned updates, if any | ||
* | * ot | ||
[[Category:Release Engineering SOPs]] | [[Category:Release Engineering SOPs]] | ||
Revision as of 18:00, 8 January 2010
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
Announcement content
- Consider this EOL announcement from openoffice.org
- Note FAQ
Verification
Consider Before Running
- Resource contention in infrastructure, such as outages
- Extenuating circumstances for specific planned updates, if any
- ot