From Fedora Project Wiki

< Releases‎ | 29

(put change checkpoint at branch)
(update to remove "rain date" terminology, which turns out to not be well-understood globally)
Line 38: Line 38:
 
| [[Changes/Policy#Beta_deadline.2Faccepted_changes_100.25_complete|Change Checkpoint: 100% Code Complete Deadline]]
 
| [[Changes/Policy#Beta_deadline.2Faccepted_changes_100.25_complete|Change Checkpoint: 100% Code Complete Deadline]]
 
|-
 
|-
| 2018-09-18|| Beta Release (Target date)
+
| 2018-09-18|| Beta Release (Preferred target)
 
|-
 
|-
| 2018-09-25 || Beta Release (Rain date)
+
| 2018-09-25 || Beta Release (Target #1)
 
|-
 
|-
 
| 2018-10-09 || [[Milestone freezes | Final Freeze]] (*)
 
| 2018-10-09 || [[Milestone freezes | Final Freeze]] (*)
 
|-
 
|-
| 2018-10-23|| [[Fedora_29_Final_Release_Criteria | Fedora 29 Final Release (GA) (Target date)]]
+
| 2018-10-23|| [[Fedora_29_Final_Release_Criteria | Fedora 29 Final Release (GA) (Preferred target)]]
 
|-
 
|-
| 2018-10-30|| [[Fedora_29_Final_Release_Criteria | Fedora 29 Final Release (GA) (Rain date)]]
+
| 2018-10-30|| [[Fedora_29_Final_Release_Criteria | Fedora 29 Final Release (GA) (Target #1)]]
 
|}
 
|}
  
 
{{admon/note | Milestone freezes | (*) Beta and Final freezes are in effect from 00:00 UTC of the freeze day. The last stable push is conducted at this time for the milestone.}}
 
{{admon/note | Milestone freezes | (*) Beta and Final freezes are in effect from 00:00 UTC of the freeze day. The last stable push is conducted at this time for the milestone.}}
  
Because we integrate upstream software with phenomenal rate of change every release, Fedora milestones are never certain. We balance getting releases to our users with making those releases reliably high-quality, and so follow a middle path between "release when it's ready" and "release on specific dates". We plan to release on the target dates listed above, or if the [[Fedora_Program_Management/GoNoGoSOP Go/No-Go meeting]] decides we're not ready, on the rain dates. If the beta release is not ready even by the rain date, the final schedule will be pushed back correspondingly.
+
Because we integrate upstream software with phenomenal rate of change every release, Fedora milestones are never certain. We balance getting releases to our users with making those releases reliably high-quality, and so follow a middle path between "release when it's ready" and "release on specific dates". We plan to release on the "Preferred target" dates listed above, or if the [[Fedora_Program_Management/GoNoGoSOP Go/No-Go meeting]] decides we're not ready, on the "Target #1" dates. See the [[Fedora Release Life Cycle]] for details.
  
 
== Detailed Schedules ==
 
== Detailed Schedules ==

Revision as of 16:32, 9 January 2018

Note.png
Fedora 29 Schedule
This a DRAFT release schedule for Fedora 29. Historical schedules are maintained on a separate page.
Warning.png
This page is a draft only
It is still under construction and content may change. Do not rely on the information on this page.


Changes

Key Milestones

2018-02-06 Branch Fedora 28 from Rawhide (Rawhide becomes future F29)
2018-05-01 Fedora 28 Release
2018-06-19 Change Checkpoint: Proposal submission deadline (Changes requiring mass rebuild)
2018-07-03 Change Checkpoint: Proposal submission deadline (System Wide Changes)
2018-07-11 Mass Rebuild
2018-07-24 Change Checkpoint: Proposal submission deadline (Self Contained Changes)
2018-07-31 Software String Freeze
2018-08-14 Change Checkpoint: Completion deadline (testable)
Branch Fedora 29 from Rawhide (Rawhide becomes future F30)
2018-08-28 Software Translation Deadline
Bodhi activation point
2018-09-04 Beta Freeze (*)
Change Checkpoint: 100% Code Complete Deadline
2018-09-18 Beta Release (Preferred target)
2018-09-25 Beta Release (Target #1)
2018-10-09 Final Freeze (*)
2018-10-23 Fedora 29 Final Release (GA) (Preferred target)
2018-10-30 Fedora 29 Final Release (GA) (Target #1)
Note.png
Milestone freezes
(*) Beta and Final freezes are in effect from 00:00 UTC of the freeze day. The last stable push is conducted at this time for the milestone.

Because we integrate upstream software with phenomenal rate of change every release, Fedora milestones are never certain. We balance getting releases to our users with making those releases reliably high-quality, and so follow a middle path between "release when it's ready" and "release on specific dates". We plan to release on the "Preferred target" dates listed above, or if the Fedora_Program_Management/GoNoGoSOP Go/No-Go meeting decides we're not ready, on the "Target #1" dates. See the Fedora Release Life Cycle for details.

Detailed Schedules


Note.png
Schedule adjustment
For any requests regarding Fedora schedule, go to Fedora Schedule Pagure Issue Tracker and file an issue or contact the current Schedule Wrangler (Jan Kurik at the moment). Requested changes might need coordination with other Fedora teams.

History

FESCo planning ticket: TBD

Drafty draft: 2017-07-05 Initial Approval: future!


Important Fedora Events

Upstream Project Schedules

Links to other significant project schedules--useful for seeing how Fedora aligns with them.

TODO: Fix these for F29

Feel free to add any other significant projects schedules!