< Releases
(Make order more logical. This page might need love.) |
(Fix links to be more readable.) |
||
| Line 1: | Line 1: | ||
= Fedora Release Schedule = | = Fedora Release Schedule = | ||
The schedule for the release currently under development | The schedule for the release currently under development, {{FedoraVersion|full|next}}, is on its [[Releases/{{FedoraVersion||next}}/Schedule| release schedule]] page. | ||
Documentation and translation of content depends on this schedule. The documentation release schedule is found on the [[DocsProject/Schedule| | Documentation and translation of content depends on this schedule. The documentation release schedule is found on the [[DocsProject/Schedule| Documentation team's schedule]] page. | ||
Historically Test and General Availability releases happen at 10:00am Eastern US Time, which is either 1500UTC or 1400UTC depending on daylight savings. | Historically Test and General Availability releases happen at 10:00am Eastern US Time, which is either 1500UTC or 1400UTC depending on daylight savings. | ||
Revision as of 15:24, 5 February 2009
Fedora Release Schedule
The schedule for the release currently under development, Fedora 41, is on its release schedule page.
Documentation and translation of content depends on this schedule. The documentation release schedule is found on the Documentation team's schedule page.
Historically Test and General Availability releases happen at 10:00am Eastern US Time, which is either 1500UTC or 1400UTC depending on daylight savings.
Schedule Rationale
Typically Fedora follows a six-month development schedule to provide a regular and predictable release. Having a new release in early May and late October moves development forward without the distractions of winter holidays and Red Hat fiscal quarters. This routine is subject to change as approved by the community-elected Fedora Engineering Steering Committee (FESCo).
Development Information
You can find detailed information about release plans, process and other information at the Fedora development page and the release engineering page.
Test users should continue to file bug reports against each test release even after we have frozen for the next test release; all feedback is helpful. After Beta release, weekly snapshots will be attempted each Friday.
Special Terms
Development freeze : The package set is frozen. Only packages that fix significant issues found in testing are added to the tree.
Feature freeze : All features must be complete in a testable state. Anything that's not will either be dropped or reverted.
String freeze : Packages which we are the 'upstream' for freeze their translatable strings. No new strings should be added without notifying the L10n team. ( more info )
Translation deadline: Translations made up to this point are guaranteed to be in the release. Packages which we are the 'upstream' for should pull translations and be repackaged after this date and before the packages are branched for the release. ( more info )
Test freeze : Rawhide is frozen until the test release is compiled.
Release: Availability for download. With a test release a test freeze ends and with the final release the development freeze ends.
Final Development freeze : Rawhide is frozen until the final release is compiled.