|
|
| (25 intermediate revisions by 11 users not shown) |
| Line 1: |
Line 1: |
| {{draft}} | | {{admon/important|This page has moved [https://docs.pagure.org/releng/sop_end_of_life.html here] with source hosted along side the code in the [https://pagure.io/releng releng pagure repository]}} |
| == Description ==
| |
| <!-- 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 ==
| |
| <!-- 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
| |
|
| |
| ==== Announcement content ====
| |
| * Consider this [http://www.openoffice.org/servlets/ReadMsg?list=announce&msgNo=407 EOL announcement] from openoffice.org
| |
| ** Note FAQ
| |
|
| |
| == Verification ==
| |
| <!-- Provide a method to verify the action was successful -->
| |
|
| |
| == Considerations ==
| |
| <!-- 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. -->
| |
|
| |
|
| [[Category:Release Engineering SOPs]] | | [[Category:Release Engineering SOPs]] |
