From Fedora Project Wiki
(Redo this with the proper template) |
(Add link to OOo FAQ) |
||
Line 31: | Line 31: | ||
** on EOL date if at all possible | ** on EOL date if at all possible | ||
** link to previous reminder announcement | ** link to previous reminder announcement | ||
==== Announcement content ==== | |||
* Consider this [http://www.openoffice.org/servlets/ReadMsg?list=announce&msgNo=407 EOL announcement] from openoffice.org | |||
** Note FAQ | |||
== Verification == | == Verification == |
Revision as of 21:25, 3 January 2010
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
Considerations
- Resource contention in infrastructure, such as outages
- Extenuating circumstances for specific planned updates, if any
- other?