(Moving Translation Deadline to the same date as Bodhi activation point (see https://lists.fedoraproject.org/archives/list/trans@lists.fedoraproject.org/message/MCTS7CWDGDKCP4LT5UDVGXALGX4EBFJY/ )) |
|||
Line 29: | Line 29: | ||
| 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-08- | |rowspan="2"| 2017-08-29 || [[L10N_Freezes#Translation_Deadline| Software Translation Deadline]] | ||
|- | |- | ||
| Bodhi activation point | |||
|- | |- | ||
|rowspan="2"| 2017-09-05 || [[Milestone freezes |Beta Freeze]] (*) | |rowspan="2"| 2017-09-05 || [[Milestone freezes |Beta Freeze]] (*) |
Revision as of 09:36, 30 March 2017
Changes
- Fedora 27 Accepted Changes
- Before the accepted Change set is finalized, proposed changes can be found in Category:ChangeAnnounced or Category:ChangeReadyForWrangler
Key Milestones
2017-02-28 | Branch Fedora 26 from Rawhide (Rawhide becomes future F27) |
2017-06-20 | Change Checkpoint: Proposal submission deadline (Changes requiring mass rebuild) |
2017-06-27 | Fedora 26 Release |
2017-07-04 | Change Checkpoint: Proposal submission deadline (System Wide Changes) |
2017-07-12 | Mass Rebuild |
2017-07-25 | Change Checkpoint: Proposal submission deadline (Self Contained Changes) |
2017-08-01 | Change Checkpoint: Completion deadline (testable) |
Software String Freeze | |
2017-08-15 | Branch Fedora 27 from Rawhide (Rawhide becomes future F28) |
2017-08-29 | Software Translation Deadline |
Bodhi activation point | |
2017-09-05 | Beta Freeze (*) |
Change Checkpoint: 100% Code Complete Deadline | |
2017-09-19 | Beta Release (Target date) |
2017-09-26 | Beta Release (Rain date) |
2017-10-10 | Final Freeze (*) |
2017-10-24 | Fedora 27 Final Release (GA) (Target date) |
2017-10-31 | Fedora 27 Final Release (GA) (Rain date) |
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
- All Detailed Schedules and iCal files
- Ambassadors
- Design
- Development
- Documentation
- Marketing
- Release Engineering
- Quality Assurance
- Translation
- Web Sites
History =
FESCo planning ticket: [1]
Initial Approval: 2017-02-10 Revised for Changes/NoMoreAlpha: 2017-03-17
Important Fedora Events
- FLOCK -- 2017-08-28 ... 2016-09-01
Upstream Project Schedules
Links to other significant project schedules--useful for seeing how Fedora aligns with them.
TODO: Fix these for F27
- Linux kernel -- Linux kernel predictions and history
- glibc -- Release/2.25, GLibc schedule history
- Gnome -- Schedule
- KDE Plasma -- Schedule
- LibreOffice -- Schedule
- Python -- Schedule
Feel free to add any other significant projects schedules!