Schedule

From FedoraProject

(Difference between revisions)
Jump to: navigation, search
(Imported from MoinMoin)
 
(ah ha! should be FedoraVersionNumber|next not FedoraVersion|next)
(7 intermediate revisions by 6 users not shown)
Line 1: Line 1:
 
+
{{:Releases/{{FedoraVersionNumber|next}}/Schedule}}

Revision as of 03:03, 3 July 2008

Note.png
Fedora 28 Schedule
Schedule approved by FESCo. Historical schedules are maintained on a separate page.


Modifications

Etapes clef

2017-08-15 Branch Fedora 27 from Rawhide (Rawhide becomes future F28)
2017-10-24 Fedora 27 Release
2018-01-09 Change Checkpoint: Proposal submission deadline (System Wide Changes)
Change Checkpoint: Proposal submission deadline (Changes requiring mass rebuild)
2018-01-30 Change Checkpoint: Proposal submission deadline (Self Contained Changes)
2018-01-31 Mass Rebuild
2018-02-06 Software String Freeze
2018-02-20 Change Checkpoint: Completion deadline (testable)
Branch Fedora 28 from Rawhide (Rawhide becomes future F29)
2018-03-06 Software Translation Deadline
Bodhi activation point
2018-03-13 Beta Freeze (*)
Change Checkpoint: 100% Code Complete Deadline
2018-03-27 Beta Release (Target date)
2018-04-03 Beta Release (Rain date)
2018-04-17 Final Freeze (*)
2018-05-01 Fedora 28 Final Release (GA) (Target date)
2018-05-08 Fedora 28 Final Release (GA) (Rain date)
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 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.

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 F28

Feel free to add any other significant projects schedules!