From Fedora Project Wiki

< Releases‎ | 29

(initial draft based on f27 plan)
 
(F29 Final is No-Go)
 
(15 intermediate revisions by 6 users not shown)
Line 1: Line 1:
{{autolang|base=yes}}
{{autolang|base=yes}}
{{admon/note | Fedora 29 Schedule | This a DRAFT release schedule for Fedora 29. Historical schedules are maintained on [[Releases/HistoricalSchedules|a separate page]].}}
<!-- {{admon/note | Fedora 29 Schedule | This a DRAFT release schedule for Fedora 29. Historical schedules are maintained on [[Releases/HistoricalSchedules|a separate page]].}} -->
{{draft}}
<!--{{draft}}-->
__NOTOC__
__NOTOC__


Line 10: Line 10:


== Key Milestones ==
== Key Milestones ==
{|
{| class="wikitable"
|-
|-
| 2018-02-06 || Branch Fedora 28 from Rawhide (Rawhide becomes future F29)
| 2018-02-20 || Branch Fedora 28 from Rawhide (Rawhide becomes future F29)
|-
|-
| 2018-05-01 || Fedora 28 Release
| 2018-05-01 || Fedora 28 Release
Line 24: Line 24:
| 2018-07-24 || Change Checkpoint: Proposal submission deadline (Self Contained Changes)  
| 2018-07-24 || Change Checkpoint: Proposal submission deadline (Self Contained Changes)  
|-
|-
|rowspan="2"| 2018-07-31|| Change Checkpoint: Completion deadline (testable)
| 2018-07-31|| [[ReleaseEngineering/StringFreezePolicy|Software String Freeze]]
|-
|-
| [[ReleaseEngineering/StringFreezePolicy|Software String Freeze]]
|rowspan="2"| 2018-08-14 || Change Checkpoint: Completion deadline (testable)
|-
|-
| 2018-08-14 || Branch Fedora 29 from Rawhide (Rawhide becomes future F30)
| Branch Fedora 29 from Rawhide (Rawhide becomes future F30)  
|-
|-
|rowspan="2"| 2018-08-28 || [[L10N_Freezes#Translation_Deadline| Software Translation Deadline]]
|rowspan="2"| 2018-08-28 || [[L10N_Freezes#Translation_Deadline| Software Translation Deadline]]
Line 34: Line 34:
| Bodhi activation point
| Bodhi activation point
|-
|-
|rowspan="2"| 2018-09-04 || [[Milestone freezes |Beta Freeze]] (*)
|rowspan="2"| 2018-08-28 || [[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-09-18|| Beta Release (Target date)
| <s>2018-09-18</s>|| <s>Beta Release (Preferred target)</s>
|-
|-
| 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-10 || Update of the AppStream data
|-
|-
| 2018-10-30|| [[Fedora_29_Final_Release_Criteria | Fedora 29 Final Release (GA) (Rain date)]]
| <s>2018-10-23</s>|| <s>[[Fedora_29_Final_Release_Criteria| Fedora 29 Final Release (GA) (Preferred target)]]</s>
|-
| 2018-10-30|| [[Fedora_29_Final_Release_Criteria | Fedora 29 Final Release (GA) (Target #1)]]
|}
|}
''The schedule has been approved by FESCo: [https://pagure.io/fesco/issue/1858 #1858]''


{{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 ==
Line 70: Line 74:
== History ==
== History ==


FESCo planning ticket: TBD
FESCo planning ticket: [https://pagure.io/fesco/issue/1858 #1858]
 
* Draft for FESCo approval: 2018-03-04
* Drafty draft: 2017-07-05


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


== Important Fedora Events ==


== Important Fedora Events ==
* [[Flock#2018]] (2018-08-08 -11)
* FLOCK -- [https://flocktofedora.org/ August?]
* [[DevConf#DevConf.us 2018]] ([https://devconf.info/us/2018  2018-08-17 -19])
<!--
* DevConf -- [http://devconf.cz/ January 2019]
-->


== Upstream Project Schedules ==
== Upstream Project Schedules ==
Line 89: Line 93:


* Linux kernel -- [http://phb-crystal-ball.org/ Linux kernel predictions and history]
* Linux kernel -- [http://phb-crystal-ball.org/ Linux kernel predictions and history]
* glibc -- [https://sourceware.org/glibc/wiki/Release/2.25 Release/2.25], [https://sourceware.org/glibc/wiki/Glibc%20Timeline GLibc schedule history]
* glibc -- [https://sourceware.org/glibc/wiki/Release/2.28 Release/2.28], [https://sourceware.org/glibc/wiki/Glibc%20Timeline GLibc schedule history]
* Gnome -- [https://wiki.gnome.org/Schedule Schedule]
* Gnome -- [https://wiki.gnome.org/Schedule Schedule]
* KDE Plasma -- [https://community.kde.org/Schedules/Plasma_5 Schedule]
* KDE Plasma -- [https://community.kde.org/Schedules/Plasma_5 Schedule]
* LibreOffice -- [https://wiki.documentfoundation.org/ReleasePlan Schedule]
* LibreOffice -- [https://wiki.documentfoundation.org/ReleasePlan Schedule]
* Python -- [https://www.python.org/dev/peps/pep-0494/#schedule Schedule]
* Python 3.7 -- [https://www.python.org/dev/peps/pep-0537/#schedule Schedule]


Feel free to add any other significant projects schedules!
Feel free to add any other significant projects schedules!


[[Category:F29]]
[[Category:F29]]

Latest revision as of 17:51, 18 October 2018


Changes

Key Milestones

2018-02-20 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-08-28 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-10 Update of the AppStream data
2018-10-23 Fedora 29 Final Release (GA) (Preferred target)
2018-10-30 Fedora 29 Final Release (GA) (Target #1)

The schedule has been approved by FESCo: #1858

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 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: #1858

  • Draft for FESCo approval: 2018-03-04
  • 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!