m (→Fedora Release Schedule: Use long fedora version.) |
m (some small changes) |
||
| Line 3: | Line 3: | ||
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. | 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. | ||
Documentation and translation of content depends on this schedule. The documentation release schedule is found on the [[DocsProject/Schedule| DocsProject/Schedule]] | Documentation and translation of content depends on this schedule. The documentation release schedule is found on the [[DocsProject/Schedule| DocsProject/Schedule]] wiki page. | ||
The schedule for the current release is at [[Releases/ | The schedule for the current release is at [[Releases/10/Schedule| Schedule]]. | ||
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. | ||
| Line 11: | Line 11: | ||
== Schedule Rationale == | == Schedule Rationale == | ||
A 6 month development schedule has been planned for Fedora | A 6 month development schedule has been planned for Fedora 10 in order to get into a regular and predictable release schedule with a new release every 6 months. Having a new release in early May and late October moves development forward without getting distracted with winter holidays and Red Hat fiscal quarters. | ||
== Development Information == | == Development Information == | ||
| Line 39: | Line 39: | ||
* [[Releases/HistoricalSchedules | Fedora Historical Schedules]] | * [[Releases/HistoricalSchedules | Fedora Historical Schedules]] | ||
[[Category:Distribution]] | [[Category:Distribution]] | ||
Revision as of 09:03, 5 June 2008
Fedora Release Schedule
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.
Documentation and translation of content depends on this schedule. The documentation release schedule is found on the DocsProject/Schedule wiki page.
The schedule for the current release is at Schedule.
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
A 6 month development schedule has been planned for Fedora 10 in order to get into a regular and predictable release schedule with a new release every 6 months. Having a new release in early May and late October moves development forward without getting distracted with winter holidays and Red Hat fiscal quarters.
Development Information
You can find detailed information about release plans, process and other information at the Fedora development page.
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.