From Fedora Project Wiki

m (Development Process)
(again, let's use the milestone freeze page to define what a milestone freeze is, less duplication is better)
Line 21: Line 21:
 
After the [[Updates Policy#Bodhi enabling|Bodhi enabling point]], the [[Bodhi]] system is permanently active on the Branched release (all the way until it goes EOL), and requirements for updates to be marked as ''stable'' are set out in the [[Updates Policy]]. Packages must go through the [[Repositories#updates-testing|''updates-testing'']] repository for the release before entering its [[Repositories#stable|''stable'']] repository, according to rules defined in the updates policy: these rules tighten gradually from Alpha through to post-GA (Final), but the basic process does not change.
 
After the [[Updates Policy#Bodhi enabling|Bodhi enabling point]], the [[Bodhi]] system is permanently active on the Branched release (all the way until it goes EOL), and requirements for updates to be marked as ''stable'' are set out in the [[Updates Policy]]. Packages must go through the [[Repositories#updates-testing|''updates-testing'']] repository for the release before entering its [[Repositories#stable|''stable'']] repository, according to rules defined in the updates policy: these rules tighten gradually from Alpha through to post-GA (Final), but the basic process does not change.
  
For the two weeks prior to a milestone (Alpha, Beta, Final) release (the [[Milestone freezes]] dates) an additional deeper freeze is in effect which prevents packages moving from ''updates-testing'' to ''stable'' except in accordance with the [[QA:SOP_blocker_bug_process|blocker]] and [[QA:SOP_freeze_exception_bug_process|freeze exception]] bug policies. This freeze is not in effect for the three weeks between a milestone build and the next milestone's ''Milestone freeze''.
+
For some time prior to a milestone (Alpha, Beta, Final) release a [[Milestone freezes|freeze]] is in effect which prevents packages moving from ''updates-testing'' to ''stable'' except in accordance with the [[QA:SOP_blocker_bug_process|blocker]] and [[QA:SOP_freeze_exception_bug_process|freeze exception]] bug policies. This freeze is not in effect for the three weeks between a milestone build and the next milestone's ''Milestone freeze''.
  
 
=== Schedule Methodology ===
 
=== Schedule Methodology ===

Revision as of 00:26, 27 September 2014

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

Development Schedule

We say approximately every 6 months because like many things, they don't always go exactly as planned. The schedule is not strictly time-based, but a hybrid of time and quality. The milestone releases are tested for compliance with the Fedora Release Criteria, and releases will be delayed if this is not the case.

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

Development Planning

Fedora development planning is handled by the Release Planning Process. So-called Changes are proposed, initially reviewed, and monitored through the development process by the engineering steering committee.

Development Process

Fedora uses a system involving two 'development' trees. Rawhide is a constantly rolling development tree. No releases are built directly from Rawhide. 14 weeks before the planned date of a Fedora release, a tree for that release is "Branched" from the Rawhide tree. At that point the Rawhide tree is moving towards the release after the new Branched release, and the pending release is stabilized in the Branched tree.

Idea.png
Birth of a Fedora
This means that development of a Fedora release is considered to begin at the time its predecessor branches from Rawhide. For instance, development on Fedora 30 began the day after Fedora 29 branched from Rawhide and entered the stabilization process.

After the Bodhi enabling point, the Bodhi system is permanently active on the Branched release (all the way until it goes EOL), and requirements for updates to be marked as stable are set out in the Updates Policy. Packages must go through the updates-testing repository for the release before entering its stable repository, according to rules defined in the updates policy: these rules tighten gradually from Alpha through to post-GA (Final), but the basic process does not change.

For some time prior to a milestone (Alpha, Beta, Final) release a freeze is in effect which prevents packages moving from updates-testing to stable except in accordance with the blocker and freeze exception bug policies. This freeze is not in effect for the three weeks between a milestone build and the next milestone's Milestone freeze.

Schedule Methodology

Fedora release schedules are proposed by the Fedora Program Manager and ratified by Fedora Engineering Steering Committee (FESCo), with input from other groups. 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 (Tuesdays or Thursdays) Length
Planning and Development Branch point of previous release plus one day Variable
Change Proposal Deadline Tue: Branch point minus 3 months n/a
Branch point Tue: Alpha Freeze minus 2 weeks n/a
Alpha test composes Any time after Branch point Until Alpha release candidates
Alpha Freeze Tue: Alpha Release minus 2 weeks QA:SOP_freeze_exception_bug_process and QA:SOP_blocker_bug_process in effect until Alpha Release
Bodhi activation point Tue: Same day as Alpha Freeze Bodhi enabled and Updates_Policy requirements in effect until EOL
String Freeze Tue: Same day as Alpha Freeze Software String Freeze Policy in effect until GA Release
Changes freeze (changes to be 'testable') Tue: Same day as Alpha Freeze N/A
Alpha release candidates Any time after Alpha Freeze Until Alpha Release
Alpha Go_No_Go_Meeting Thu @ 13:00 E{D,S}T: planned Alpha Release minus five days (repeats if No-Go) n/a
Alpha Release Tue: Beta Release minus 5 weeks, Alpha Freeze plus 2 weeks Live until Beta Release
Beta test composes Tue: Beta Freeze minus 2 weeks, Alpha Release plus 1 week Until Beta release candidates
Beta Freeze Tue: Beta Release minus 2 weeks, Alpha Release plus 3 weeks QA:SOP_freeze_exception_bug_process and QA:SOP_blocker_bug_process in effect until Beta Release
Beta release candidates Any time after Beta Freeze Until Beta Release
Changes code complete Tue: Same day as Beta Freeze N/A
Beta Go_No_Go_Meeting Thu @ 13:00 E{D,S}T: planned Beta Release minus five days (repeats if No-Go) n/a
Beta Release Tue: Beta Freeze plus 2 weeks, GA Release minus 5 weeks Live until GA release
Final test composes Tue: Final Freeze minus 2 weeks, Beta Release plus 1 week Until Final release candidates
Final Freeze Tue: Final Release minus 2 weeks, Beta Release plus 3 weeks QA:SOP_freeze_exception_bug_process and QA:SOP_blocker_bug_process in effect until GA Release
Final release candidates Any time after Final Freeze Until GA Release
Final Go_No_Go_Meeting Thu @ 13:00 E{D,S}T: planned GA Release minus five days (repeats if No-Go) n/a
GA Release Tue: Primary date from which rest of schedule derives n/a
Maintenance Tue: Same day as GA release ~13 Months
End of Life GA of next-but-one release plus one month n/a

Steps to Construct a New Schedule

This is admittedly an unusual methodology, but it is fairly easy to generate using the the TaskJuggler schedules the Fedora Program Manager maintains.

  1. Pick GA release date (the Tuesday before May 1st or October 31st)
  2. Work backwards using consistent spacing for freezes, composes, and releases for Alpha, Beta, and Final, as described above, to the Branch point
  3. Set the change proposal deadline working backwards from the Branch point
  4. The time before the change proposal deadline and after the Branch point of the previous release is the time dedicated to development
    • Development time varies from from release to release based on when the previous release branched
    • The stabilization and testing time (from Branch point until GA release) is held constant from release to release

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 other distributions following Fedora having adopted a similar release cycle. Several other major components, including the Linux kernel, Openoffice.org, Xorg, have started following a time based release schedule. 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 the Alpha, Beta, or Final Go_No_Go_Meetings result in a "No Go" determination, that milestone and subsequent milestones will be pushed back by one week.

One week is 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. Go/No Go meetings receive input from representatives of FESCo, Release Engineering, and Quality Assurance.

Maintenance Schedule

We say maintained for approximately 13 months because the supported period for 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 28 will be maintained until 1 month after the release of Fedora 30.
  • Fedora 29 will be maintained until 1 month after the release of Fedora 31.

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 Rawhide and the pre-release Branched code to be a manageable work load.

End of Life (EOL)

When a release reaches the point where it is no longer supported nor updates are created for it, then it is considered End of Life (EOL). Branches for new packages in the SCM are not allowed for distribution X after the Fedora X+2 release and new builds are no longer allowed.

The tasks performed at EOL are documented in the End of life SOP.

Additional Release Schedule Information