Fedora Release Life Cycle

From FedoraProject

(Difference between revisions)
Jump to: navigation, search
(Adjusted to reflect current plans for Fedora 13)
(Schedule Methodology)
Line 9: Line 9:
 
=== Schedule Methodology ===
 
=== Schedule Methodology ===
  
Fedora release schedules are proposed by the Release Engineering team and ratified by [[FESCo | Fedora Engineering Steering Committee (FESCo)]].  FESCo is responsible for overseeing the technical direction of the Fedora distribution.  A core schedule is built around key milestones in a Fedora that Release Engineering is able to support by building the distribution for public release on those dates.
+
Fedora release schedules are proposed by the Release Engineering team and ratified by [[FESCo | Fedora Engineering Steering Committee (FESCo)]].  FESCo is responsible for overseeing the technical direction of the Fedora distribution.  A core schedule is created using the key tasks listed below.  Detailed team schedules are built around these dates.
  
 
{|border="1"  
 
{|border="1"  
Line 16: Line 16:
 
| Planning and Development    || Day After GA of Previous Release || Depends on GA date<br>and working backwards
 
| Planning and Development    || Day After GA of Previous Release || Depends on GA date<br>and working backwards
 
|-
 
|-
| Feature Acceptance Deadline || Two weeks before Feature Freeze || n/a
+
| Feature Acceptance Deadline || Tuesday--Two weeks before Feature Freeze || n/a
 
|-
 
|-
| [[ReleaseEngineering/FeatureFreezePolicy| Feature Freeze]] || 1 week before Alpha Freeze || Until GA
+
| [[ReleaseEngineering/FeatureFreezePolicy|Feature Freeze]] || Tuesday--1 week before Alpha Freeze || Until GA
 
|-
 
|-
| [[Alpha_Freeze_Policy| Alpha Freeze]] || One week after Feature Freeze  || 2 weeks
+
| [[Alpha_Freeze_Policy|Alpha Freeze]] || Tuesday--One week after Feature Freeze  || 2 weeks
 
|-
 
|-
| [[ReleaseEngineering/StringFreezePolicy| String Freeze]] || Same time as Alpha Freeze || Until GA
+
| [[ReleaseEngineering/StringFreezePolicy|String Freeze]] || Same time as Alpha Freeze || Until GA
 
|-
 
|-
| Alpha Public Public Testing || After Alpha Freeze || 3 Weeks
+
| Alpha Go/No-Go Meeting || Wednesday @ 20:00 E{D,S}T before Tuesday release day || n/a
 +
|-
 +
| Alpha Public Public Testing || Tuesday--End of Alpha Freeze || 3 Weeks
 
|-
 
|-
 
| [[ReleaseEngineering/FinalFreezePolicy|  Beta Freeze]] || After Alpha Public Testing || Until GA
 
| [[ReleaseEngineering/FinalFreezePolicy|  Beta Freeze]] || After Alpha Public Testing || Until GA
 
|-
 
|-
| Beta Public Public Testing || After Beta Freeze || 3 Weeks
+
| Beta Go/No-Go Meeting || Wednesday @ 20:00 E{D,S}T before Tuesday release day || n/a
 +
|-
 +
| Beta Public Public Testing || Tuesday--End of Beta Freeze || 3 Weeks
 
|-
 
|-
 
| Compose GA RC || Two Days after end of Beta Public Testing || 1 Day
 
| Compose GA RC || Two Days after end of Beta Public Testing || 1 Day
 
|-
 
|-
 
| Test GA RC || After Compose GA RC || 1 week
 
| Test GA RC || After Compose GA RC || 1 week
 +
|-
 +
| Final Go/No-Go Meeting || Monday @ 20:00 E{D,S}T before Tuesday release day || n/a
 
|-
 
|-
 
| GA Release || Six days after Test GA RC ends || n/a
 
| GA Release || Six days after Test GA RC ends || n/a

Revision as of 21:40, 25 November 2009

The Fedora Project releases a new version of Fedora about every 6 months and provides updated packages (maintenance) to these releases for about 13 months. This allows users to "skip a release" while still being able to always have a system that is still receiving updates.

Contents

Development Schedule

We say developed and released about every 6 months because like many things--they don't always go exactly as planned.

The schedule for the release currently under development, Fedora 21 (TBA), is on its release schedule page. Test and General Availability (final) releases happen at 10:00am Eastern US Time, which is either 1500UTC or 1400UTC depending on if daylight savings effect.

Schedule Methodology

Fedora release schedules are proposed by the Release Engineering team and ratified by Fedora Engineering Steering Committee (FESCo). FESCo is responsible for overseeing the technical direction of the Fedora distribution. A core schedule is created using the key tasks listed below. Detailed team schedules are built around these dates.

Task/Milestone Start Day Length
Planning and Development Day After GA of Previous Release Depends on GA date
and working backwards
Feature Acceptance Deadline Tuesday--Two weeks before Feature Freeze n/a
Feature Freeze Tuesday--1 week before Alpha Freeze Until GA
Alpha Freeze Tuesday--One week after Feature Freeze 2 weeks
String Freeze Same time as Alpha Freeze Until GA
Alpha Go/No-Go Meeting Wednesday @ 20:00 E{D,S}T before Tuesday release day n/a
Alpha Public Public Testing Tuesday--End of Alpha Freeze 3 Weeks
Beta Freeze After Alpha Public Testing Until GA
Beta Go/No-Go Meeting Wednesday @ 20:00 E{D,S}T before Tuesday release day n/a
Beta Public Public Testing Tuesday--End of Beta Freeze 3 Weeks
Compose GA RC Two Days after end of Beta Public Testing 1 Day
Test GA RC After Compose GA RC 1 week
Final Go/No-Go Meeting Monday @ 20:00 E{D,S}T before Tuesday release day n/a
GA Release Six days after Test GA RC ends n/a
End of Life One month after GA of current release + 2 releases ~13 Months

Development Schedule Rationale

Fedora generally develops new releases over a six month period to provide a regular and predictable release schedule. The bi-annual targeted release dates are May Day (May 1st) and Halloween (October 31) making them easy to remember and avoiding significant holiday breaks. Changes to this standard must be approved by the community-elected Fedora Engineering Steering Committee (FESCo).

A six month release schedule also follows the precedence of Red Hat Linux (precursor to Fedora). Former Red Hat software engineer Havoc Pennington offers a historical perspective here. GNOME started following a time based release based on the ideas and success of Red Hat Linux and others distribution following Fedora having adopted a similar release cycle too. Several other major components including the Linux kernel, Openoffice.org, Xorg have started following a time based release schedule too. While the exact release schedules vary between these components and other upstream projects, the interactions between these components and Fedora makes a six month time based release schedule a good balance.

Schedule Contingency Planning

If it becomes readily evident, based on the input from representatives of FESCo, Release Engineering, and Quality Assurance that any of the following milestones will not be met, one week will be added to all remaining scheduled milestones and dependent tasks--including the final release date:

  • Public Alpha Release
  • Public Beta Release
  • Public Final Release

One week is the added to the schedule to maintain the practice of releasing on Tuesdays. Tuesdays are the designated release day because they are good days for news coverage and the established day we synchronize our content with the mirrors that carry our releases.

Maintenance Schedule

We say maintained for about 13 months because the supported period for released releases is dependent on the date the release under development goes final. As a result, Release X is supported until one month after the release of Release X+2.

This translates into:

  • Fedora 19 will be maintained until 1 month after the release of Fedora 21.
  • Fedora 20 will be maintained until 1 month after the release of Fedora 22.

Maintenance Schedule Methodology

FIXME -- add schedule of how maintenance date is set/announced

Maintenance Schedule Rationale

Fedora is focused on free and open source software innovations and moves quickly. If you want a distribution that moves slower but has a longer lifecycle, Red Hat Enterprise Linux, which is derivative of Fedora or free rebuilds of that such as CentOS might be more suitable for you. Refer to the RHEL page for more details.

Historically, the Fedora Project has found supporting two releases plus a release under development to be a manageable work load.

Additional Release Schedule Information