From Fedora Project Wiki

(Development Process)
m (fixed dead link to End Of Life SOP)
 
(31 intermediate revisions by 6 users not shown)
Line 5: Line 5:
 
== Development Schedule ==
 
== Development Schedule ==
  
We say ''approximately every 6 months'' because like many things, they don't always go exactly as planned.
+
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 [[QA:Release_validation_test_plan|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, {{FedoraVersion|full|next}}, is on its [[Releases/{{FedoraVersion||next}}/Schedule| 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.
+
The schedule for the release currently under development, {{FedoraVersion|full|next}}, is on its [[Releases/{{FedoraVersion||next}}/Schedule| release schedule]] page. Beta, and General Availability (final) releases happen at 14:00 UTC.
 +
 
 +
=== Development Planning ===
 +
 
 +
Fedora development planning is handled by the [[Changes/Policy|Release Planning Process]]. So-called ''Changes'' are proposed, initially reviewed, and monitored through the development process by the [[Fedora_Engineering_Steering_Committee|engineering steering committee]].
  
 
=== Development Process ===
 
=== Development Process ===
  
Fedora uses a system involving two 'development' releases. [[Releases/Rawhide|Rawhide]] is a constantly rolling development repository. No releases are built directly from Rawhide. 14 weeks before the planned date of a Fedora release, a tree for that release is "[[Releases/Branched|Branched]]" from the Rawhide tree. At that point the Rawhide tree is moving towards the next release but one, and the pending release is stabilized in the Branched tree.
+
Fedora uses a system involving two 'development' trees. [[Releases/Rawhide|Rawhide]] is a constantly rolling development tree. No releases are built directly from Rawhide. Approximately 10 weeks before the planned date of a Fedora release, a tree for that release is "[[Releases/Branched|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.
 +
 
 +
{{admon/tip|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 {{FedoraVersion|long|next}} began the day after {{FedoraVersion|long}} branched from Rawhide and entered the stabilization process.}}
  
After the Alpha [[Change_deadlines|Change deadline]], the [[Updates_Policy]] is active on the Branched release until the GA (Final) release. Packages must go through the [[QA:Updates_Testing|''updates-testing'']] repository for the Branched release before entering its ''stable'' repository, according to rules defined in the updates policy.
+
After the [[Updates Policy#Bodhi enabling|Bodhi activation 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 Beta 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 ''Change deadline'' date) 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 ''Change deadline''.
+
For some time prior to a milestone (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 lifted once the milestone is finished, and so packages begin to move from ''updates-testing'' to ''stable'' as normal again, until the next milestone's freeze date.
  
 
=== Schedule Methodology ===
 
=== Schedule Methodology ===
  
Fedora release schedules are proposed by the Fedora Program Manager and ratified by [[FESCo | 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.
+
Fedora release schedules are proposed by the [[Fedora_Program_Management|Fedora Program Manager]] and ratified by the [[FESCo | 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.
 +
 
 +
''Note: When referring to '''Beta/Final Target''', we refer to an planned date. When referring to '''Beta/Final release''' only, we refer to a date the release has actually happened.''
  
 
{|border="1"  
 
{|border="1"  
!Task/Milestone !!  Start Day !! Length
+
!Task/Milestone !!  Start Day (Tuesdays or Thursdays) !! Length
 
|-
 
|-
 
| Planning and Development || ''Branch point'' of ''previous release'' plus '''one day''' || Variable
 
| Planning and Development || ''Branch point'' of ''previous release'' plus '''one day''' || Variable
 
|-
 
|-
| [[Changes/Policy|Change Proposal Deadline]] || Tue: ''Branch point'' minus '''3 months''' || n/a
+
| [[Changes/Policy#For_Developers|Changes Checkpoint: Proposal deadline for Changes requiring ''Mass rebuild'']] || Tue: ''Mass rebuild'' minus '''3 weeks''' || n/a
 
|-
 
|-
| [[Releases/Branched|Branch point]] || Tue: ''Alpha Change Deadline'' minus '''2 weeks''' || n/a
+
| [[Changes/Policy#For_Developers|Changes Checkpoint: Proposal deadline for System Wide Changes]] || Tue: ''Mass rebuild'' minus '''1 week''' || n/a
 
|-
 
|-
| [[QA:SOP_compose_request|Alpha test composes]] || Any time after ''Branch point'' || Until ''Alpha release candidates''
+
| style="background:lightgrey;" | '''Mass rebuild''' || ''Branch point'' minus '''5 weeks''' || Until ''Branch point''
 
|-
 
|-
| [[Change_deadlines | Alpha Change Deadline]] || Tue: ''Alpha Release'' minus '''2 weeks''' || [[QA:SOP_freeze_exception_bug_process]] and [[QA:SOP_blocker_bug_process]] in effect until ''Alpha Release''
+
| [[Changes/Policy#For_Developers|Changes Checkpoint: Proposal deadline for Self Contained Changes]] || Tue: ''Branch point'' minus '''3 weeks''' || n/a
 
|-
 
|-
| Update policy activation || Tue: '''Same day''' as ''Alpha Change Deadline'' || [[Updates_Policy]] in effect until ''GA Release''
+
| style="background:lightgrey;" | '''[[Releases/Branched|Branch point]]''' || Tue: ''Preferred Beta Release Target'' minus '''5 weeks''' || n/a
 
|-
 
|-
| String Freeze || Tue: '''Same day''' as ''Alpha Change Deadline'' || [[Software String Freeze Policy]] in effect until ''GA Release''
+
| [[Changes/Policy#For_Developers|Changes Checkpoint: Completion deadline (testable)]] || Tue: '''Same day''' as ''Branch point'' || N/A
 
|-
 
|-
| [[Changes/Policy|Changes substantially complete and testable]]  || Tue: '''Same day''' as ''Alpha Change Deadline'' || [[Changes_Freeze_Policy]] partly in effect until ''GA Release''
+
| String Freeze || Tue: ''Branch point'' plus '''1 week''' || [[Software String Freeze Policy]] in effect until ''Final Release (GA)''
 
|-
 
|-
| [[QA:SOP_compose_request|Alpha release candidates]] || Any time after ''Alpha Change Deadline'' || Until ''Alpha Release''
+
| [[Updates Policy#Bodhi activation|Bodhi activation point]] || Tue: ''Preferred Beta Target'' minus '''3 weeks''', '''Same day''' as ''Beta Freeze'' || [[Bodhi]] enabled and [[Updates_Policy]] requirements in effect until ''EOL''
 
|-
 
|-
| Alpha [[Go_No_Go_Meeting]] || '''Thu''' @ 13:00 E{D,S}T: planned ''Alpha Release'' '''minus five days''' (repeats if No-Go) || n/a
+
| [[Milestone freezes | Beta Freeze]] || Tue: ''Preferred Beta Target'' minus '''3 weeks''' || [[QA:SOP_freeze_exception_bug_process]] and [[QA:SOP_blocker_bug_process]] in effect until ''Beta Release''
 
|-
 
|-
| Alpha Release || Tue: ''Beta Release'' minus '''5 weeks''', ''Branch Freeze'' plus '''2 weeks''' || Live until ''Beta Release''
+
| [[Changes/Policy#For_Developers|Changes Checkpoint: 100% code complete deadline ]]  || Tue: '''Same day''' as ''Beta Freeze'' || N/A
 
|-
 
|-
| [[QA:SOP_compose_request|Beta test composes]] || Tue: ''Beta Change Deadline'' minus '''2 weeks''', ''Alpha Release'' plus '''1 week''' || Until ''Beta release candidates''
+
| [[QA:SOP_compose_request|Beta release candidates]] || Any time after ''Beta Freeze'' || Until ''Beta Release''
 
|-
 
|-
| [[Change_deadlines | Beta Change Deadline]] || 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 [[Go_No_Go_Meeting]] || '''Thu''' @ 13:00 E{D,S}T: planned ''Preferred Beta Target'' '''minus five days''' (repeats if No-Go) || n/a
 
|-
 
|-
| [[QA:SOP_compose_request|Beta release candidates]] || Any time after ''Beta Change Deadline'' || Until ''Beta Release''
+
| style="background:lightgrey;" | '''Preferred Beta Target'''|| Tue: ''Preferred Final Target'' minus '''5 weeks''' || Live until ''GA release''
 
|-
 
|-
| [[Changes/Policy|Changes 100% code complete]]  || Tue: '''Same day''' as ''Beta Change Deadline'' || [[Changes_Freeze_Policy]] fully in effect until ''GA release''
+
| Beta Target #1|| Tue: ''Preferred Beta Target'' plus '''1 week''', ''Preferred Final Target'' minus '''4 weeks''' || 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
+
| [[Milestone freezes | Final Freeze]] || Tue: ''Preferred Final Target'' minus '''2 weeks''' || [[QA:SOP_freeze_exception_bug_process]] and [[QA:SOP_blocker_bug_process]] in effect until ''Final Release (GA)''
 
|-
 
|-
| Beta Release || Tue: ''Beta Change Deadline'' plus '''2 weeks''', ''GA Release'' minus '''5 weeks''' || Live until ''GA release''
+
| [[QA:SOP_compose_request|Final release candidates]] || Any time after ''Final Freeze'' || Until ''Final Release (GA)''
 
|-
 
|-
| [[QA:SOP_compose_request|Final test composes]] || Tue: ''Final Change Deadline'' minus '''2 weeks''', ''Beta Release'' plus '''1 week''' || Until ''Final release candidates''
+
| Final [[Go_No_Go_Meeting]] || '''Thu''' @ 13:00 E{D,S}T: planned ''Final Release (GA)'' '''minus five days''' (repeats if No-Go) || n/a
 
|-
 
|-
| [[Change_deadlines | Final Change Deadline]] || 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''
+
| style="background:lightgrey;" | '''Preferred Final Target''' || Tue: '''Primary date''' from which rest of schedule derives<br>This date is either the Tuesday before May 1st or October 31st. || n/a
 
|-
 
|-
| [[QA:SOP_compose_request|Final release candidates]] || Any time after ''Final Change Deadline'' || Until ''GA Release''
+
| Final Target #1 || Tue: ''Preferred Final Target'' plus '''1 week''' || n/a
 
|-
 
|-
| Final [[Go_No_Go_Meeting]] || '''Thu''' @ 13:00 E{D,S}T: planned ''GA Release'' '''minus five days''' (repeats if No-Go) || n/a
+
| Maintenance || Tue: '''Same day''' as ''Final Release (GA)'' || ~'''13 Months'''
 
|-
 
|-
| GA Release || Tue: '''Primary date''' from which rest of schedule derives || n/a
+
| End of Life || ''Final Release (GA) of next-but-one release'' plus '''one month''' || 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 [https://fedorapeople.org/groups/schedule/f-{{FedoraVersionNumber|next}} TaskJuggler schedules] the Fedora Program Manager maintains.
 
 
# Pick ''GA release'' date (the Tuesday before May 1st or October 31st)
 
# Work backwards using consistent spacing for freezes, composes, and releases for Alpha, Beta, and Final, as described above, to the ''Branch point''
 
# Set the [[Changes/Policy|change proposal deadline]] working backwards from the ''Branch point''
 
# 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 ===
 
=== 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 [[FESCo | Fedora Engineering Steering Committee (FESCo)]].
+
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 for avoiding significant holiday breaks.  Changes to this standard must be approved by the community-elected [[FESCo | 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 [http://article.gmane.org/gmane.linux.redhat.fedora.advisory-board/1475/ 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.
 
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 [http://article.gmane.org/gmane.linux.redhat.fedora.advisory-board/1475/ 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.
 +
 +
Although due to how planning process and release validation works, Fedora is not a strictly time based distribution, but uses combination of both time and feature based release paradigms. This way we can react to bigger changes aka new installed, way how we release bits (Fedora.Next) etc.
  
 
=== Schedule Contingency Planning ===
 
=== Schedule Contingency Planning ===
 +
If ''Mass rebuild'' is not completed on time, all the subsequent milestones starting with ''Branch point'' are pushed back for one week until the ''Mass rebuild'' is completed.
 +
 +
If the Beta [[Go_No_Go_Meeting]] results in a "No Go" determination, rescheduling of the milestone and subsequent milestones follows these rules:
 +
* Slip of the Beta from the Preferred Target to Target #1 does not affect Final Release (GA) date. The Final Release (GA) date remains on ''Preferred Final Target''.
 +
* Slip of the Beta to Target #1 adds a new ''Beta Target #2'' and Final Release (GA) slips to ''Final Target #1'' (and we don't yet add a ''Final Target #2'').
 +
* Slip of the Beta past Target #N (where N >= 2) adds a new ''Beta Target #(N+1)'' and also adds a new ''Final Target #N''
 +
 +
If the Final [[Go_No_Go_Meeting]] results in a "No Go" determination, that milestone and subsequent milestones will be pushed back by one week.
  
If the Alpha, Beta, or Final [[Go_No_Go_Meeting]]s 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 correspond to the established day we synchronize our content with the mirrors that carry our releases. Be aware of holidays and of possible PR conflicts (contact Fedora PR) with the new proposed final date.
  
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 [[Fedora_Engineering_Steering_Committee|FESCo]], [[ReleaseEngineering|Release Engineering]], and [[QA|Quality Assurance]].
+
Go/No Go meetings receive input from representatives of [[Fedora_Engineering_Steering_Committee|FESCo]], [[ReleaseEngineering|Release Engineering]], and [[QA|Quality Assurance]].
  
 
== Maintenance Schedule ==
 
== Maintenance Schedule ==
Line 108: Line 112:
 
Fedora is [[Objectives | focused]] on free and open source software [[Red Hat contributions | 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.
 
Fedora is [[Objectives | focused]] on free and open source software [[Red Hat contributions | 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.
+
Historically, the Fedora Project has found that supporting two releases plus Rawhide and the pre-release Branched code to be a manageable work load.
  
 
== End of Life (EOL) ==
 
== 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.
+
When a release reaches the point where it is no longer supported when no 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]].
+
The tasks performed at EOL are documented in the [https://docs.pagure.org/releng/sop_end_of_life.html End of life SOP].
  
 
= Additional Release Schedule Information =
 
= Additional Release Schedule Information =

Latest revision as of 09:08, 13 November 2018

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. Beta, and General Availability (final) releases happen at 14:00 UTC.

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. Approximately 10 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 activation 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 Beta through to post-GA (Final), but the basic process does not change.

For some time prior to a milestone (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 lifted once the milestone is finished, and so packages begin to move from updates-testing to stable as normal again, until the next milestone's freeze date.

Schedule Methodology

Fedora release schedules are proposed by the Fedora Program Manager and ratified by the 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.

Note: When referring to Beta/Final Target, we refer to an planned date. When referring to Beta/Final release only, we refer to a date the release has actually happened.

Task/Milestone Start Day (Tuesdays or Thursdays) Length
Planning and Development Branch point of previous release plus one day Variable
Changes Checkpoint: Proposal deadline for Changes requiring Mass rebuild Tue: Mass rebuild minus 3 weeks n/a
Changes Checkpoint: Proposal deadline for System Wide Changes Tue: Mass rebuild minus 1 week n/a
Mass rebuild Branch point minus 5 weeks Until Branch point
Changes Checkpoint: Proposal deadline for Self Contained Changes Tue: Branch point minus 3 weeks n/a
Branch point Tue: Preferred Beta Release Target minus 5 weeks n/a
Changes Checkpoint: Completion deadline (testable) Tue: Same day as Branch point N/A
String Freeze Tue: Branch point plus 1 week Software String Freeze Policy in effect until Final Release (GA)
Bodhi activation point Tue: Preferred Beta Target minus 3 weeks, Same day as Beta Freeze Bodhi enabled and Updates_Policy requirements in effect until EOL
Beta Freeze Tue: Preferred Beta Target minus 3 weeks QA:SOP_freeze_exception_bug_process and QA:SOP_blocker_bug_process in effect until Beta Release
Changes Checkpoint: 100% code complete deadline Tue: Same day as Beta Freeze N/A
Beta release candidates Any time after Beta Freeze Until Beta Release
Beta Go_No_Go_Meeting Thu @ 13:00 E{D,S}T: planned Preferred Beta Target minus five days (repeats if No-Go) n/a
Preferred Beta Target Tue: Preferred Final Target minus 5 weeks Live until GA release
Beta Target #1 Tue: Preferred Beta Target plus 1 week, Preferred Final Target minus 4 weeks n/a
Final Freeze Tue: Preferred Final Target minus 2 weeks QA:SOP_freeze_exception_bug_process and QA:SOP_blocker_bug_process in effect until Final Release (GA)
Final release candidates Any time after Final Freeze Until Final Release (GA)
Final Go_No_Go_Meeting Thu @ 13:00 E{D,S}T: planned Final Release (GA) minus five days (repeats if No-Go) n/a
Preferred Final Target Tue: Primary date from which rest of schedule derives
This date is either the Tuesday before May 1st or October 31st.
n/a
Final Target #1 Tue: Preferred Final Target plus 1 week n/a
Maintenance Tue: Same day as Final Release (GA) ~13 Months
End of Life Final Release (GA) of next-but-one release plus one month n/a

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 for 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.

Although due to how planning process and release validation works, Fedora is not a strictly time based distribution, but uses combination of both time and feature based release paradigms. This way we can react to bigger changes aka new installed, way how we release bits (Fedora.Next) etc.

Schedule Contingency Planning

If Mass rebuild is not completed on time, all the subsequent milestones starting with Branch point are pushed back for one week until the Mass rebuild is completed.

If the Beta Go_No_Go_Meeting results in a "No Go" determination, rescheduling of the milestone and subsequent milestones follows these rules:

  • Slip of the Beta from the Preferred Target to Target #1 does not affect Final Release (GA) date. The Final Release (GA) date remains on Preferred Final Target.
  • Slip of the Beta to Target #1 adds a new Beta Target #2 and Final Release (GA) slips to Final Target #1 (and we don't yet add a Final Target #2).
  • Slip of the Beta past Target #N (where N >= 2) adds a new Beta Target #(N+1) and also adds a new Final Target #N

If the Final Go_No_Go_Meeting results 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 correspond to the established day we synchronize our content with the mirrors that carry our releases. Be aware of holidays and of possible PR conflicts (contact Fedora PR) with the new proposed final date.

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 that 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 when no 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