From Fedora Project Wiki

< Releases‎ | 28

(put testable on branch day)
(add cake.)
 
(13 intermediate revisions by 8 users not shown)
Line 1: Line 1:
{{autolang|base=yes}}
{{lang|en|fr|page=Releases/28/Schedule}}
{{admon/note | Fedora 28 Schedule | This is a DRAFT release schedule for Fedora 28. Historical schedules are maintained on [[Releases/HistoricalSchedules|a separate page]].}}
{{admon/note | Fedora 28 Schedule | Schedule [https://pagure.io/fesco/issue/1765 approved by FESCo]. Historical schedules are maintained on [[Releases/HistoricalSchedules|a separate page]].}}
{{draft}}
<!--{{draft}}-->
__NOTOC__
__NOTOC__


Line 10: Line 10:


== Key Milestones ==
== Key Milestones ==
{|
{| class="wikitable"
|-
|-
| 2017-08-15 || Branch Fedora 27 from Rawhide (Rawhide becomes future F28)  
| 2017-08-15 || Branch Fedora 27 from Rawhide (Rawhide becomes future F28)  
|-
|-
| 2017-10-24 || Fedora 27 Release
| <s>2017-10-24</s><br>2017-11-14 || Fedora 27 Release
|-
|-
|rowspan="2"|2018-01-09 || Change Checkpoint: Proposal submission deadline (System Wide Changes)  
|rowspan="2"|2018-01-09 || Change Checkpoint: Proposal submission deadline (System Wide Changes)  
Line 30: Line 30:
| Branch Fedora 28 from Rawhide (Rawhide becomes future F29)
| Branch Fedora 28 from Rawhide (Rawhide becomes future F29)
|-
|-
|rowspan="2"| 2018-03-06 || [[L10N_Freezes#Translation_Deadline| Software Translation Deadline]]
|rowspan="4"| 2018-03-06 || [[L10N_Freezes#Translation_Deadline| Software Translation Deadline]]
|-
|-
| Bodhi activation point
| Bodhi activation point
|-
|-
|rowspan="2"| 2018-03-13 || [[Milestone freezes |Beta Freeze]] (*)
| [[Milestone freezes |Beta Freeze]] (*)
|-
|-
| [[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-03-27|| Beta Release (Target date)
| <s>2018-03-27</s>||<s>Beta Release (Preferred Target)</s> [https://meetbot.fedoraproject.org/fedora-meeting-1/2018-03-22/f28-beta-go-no-go-meeting.2018-03-22-17.00.html No-Go]
|-
|-
| 2018-04-03 || Beta Release (Rain date)
| 2018-04-03 || Beta Release (Target #1)
|-
|-
| 2018-04-17 || [[Milestone freezes | Final Freeze]] (*)
| 2018-04-17 || [[Milestone freezes | Final Freeze]] (*)
|-
|-
| 2018-05-01|| [[Fedora_28_Final_Release_Criteria | Fedora 28 Final Release (GA) (Target date)]]
| 2018-05-01|| [[Fedora_28_Final_Release_Criteria | Fedora 28 Final Release (GA) (Preferred Target)]] 🎂
|-
|-
| 2018-05-08|| [[Fedora_28_Final_Release_Criteria | Fedora 28 Final Release (GA) (Rain date)]]
| <s> 2018-05-08 </s>|| <s>[[Fedora_28_Final_Release_Criteria | Fedora 28 Final Release (GA) (Target #1)]] </s>  (Preferred Target used)
|}
|}


{{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 ==

Latest revision as of 01:01, 1 May 2018

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


Changes

Key Milestones

2017-08-15 Branch Fedora 27 from Rawhide (Rawhide becomes future F28)
2017-10-24
2017-11-14
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
Beta Freeze (*)
Change Checkpoint: 100% Code Complete Deadline
2018-03-27 Beta Release (Preferred Target) No-Go
2018-04-03 Beta Release (Target #1)
2018-04-17 Final Freeze (*)
2018-05-01 Fedora 28 Final Release (GA) (Preferred Target) 🎂
2018-05-08 Fedora 28 Final Release (GA) (Target #1) (Preferred Target used)
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 F28

Feel free to add any other significant projects schedules!