From Fedora Project Wiki

(→‎Development: link to Branched)
(→‎Development: add download links and context)
Line 16: Line 16:
* [[Releases/Branched]] - Continuous daily updates.  The [[Feature Freeze Policy|Feature Freeze]] and [[Software String Freeze Policy|String Freeze]] are started during this phase.  The Alpha Freeze occurs as that milestone approaches.  Installers and updaters receive close attention.
* [[Releases/Branched]] - Continuous daily updates.  The [[Feature Freeze Policy|Feature Freeze]] and [[Software String Freeze Policy|String Freeze]] are started during this phase.  The Alpha Freeze occurs as that milestone approaches.  Installers and updaters receive close attention.
* [[Alpha Milestone|Alpha]] - Initial testing of all packages, which must be feature-complete by this point.  The [[Beta Freeze Policy|Beta Freeze]] occurs as that milestone approaches.
* [[Alpha Milestone|Alpha]] - Initial testing of all packages, which must be feature-complete by this point.  The [[Beta Freeze Policy|Beta Freeze]] occurs as that milestone approaches.
* Beta - Wide testing of all packages.  The [[Final Freeze Policy|Final Freeze]] occurs as that milestone approaches.
* Beta - Wide testing of all packages.  The [[Final Freeze Policy|Final Freeze]] occurs as that milestone approaches.  See http://fedoraproject.org/get-prerelease to download.
* Final Release - Suitable for the general public.
* Final Release - Suitable for the general public.


Line 22: Line 22:


During the Branched, Alpha, and Beta phases, there will be "fedora" and "updates-testing" repositories.  As updates are approved, they will move into the "fedora" repository.  As the final release occurs, an "updates" repository will be created, and packages will move from "updates-testing" to "updates" instead of "fedora".  The "rawhide" repository will always follow the Rawhide branch, and it receives all updates directly and untested.
During the Branched, Alpha, and Beta phases, there will be "fedora" and "updates-testing" repositories.  As updates are approved, they will move into the "fedora" repository.  As the final release occurs, an "updates" repository will be created, and packages will move from "updates-testing" to "updates" instead of "fedora".  The "rawhide" repository will always follow the Rawhide branch, and it receives all updates directly and untested.
During the Branched, Alpha, and Beta phases, daily spins of Live media are available at: http://alt.fedoraproject.org/pub/alt/nightly-composes/
These include only packages in the "stable" repository for that release, but that can include updates which have been approved for stable after the milestone date.  The maximum size is now 1GB (intended for USB or DVD media, potentially too big for CD).  Live spins are ideal for testing without disturbing an existing system.
During the testing phases following the Alpha and Beta releases, the distribution for those milestones can be downloaded at: http://fedoraproject.org/get-prerelease


== Current Supported Releases ==
== Current Supported Releases ==

Revision as of 16:59, 9 March 2010

Fedora Releases

Time Based Release Schedule

To understand the reasoning behind time based release cycles and Fedora's release lifecycle see Fedora Release Life Cycle.

Development

The release of Fedora currently under development is Fedora 42.

Starting with Fedora 13 the "No Frozen Rawhide" pattern will be used, meaning each release will have the following phases:

  • Releases/Rawhide - Continuous daily updates with no guarantee of stability. Intended for initial testing of the very latest code under active development.
  • Releases/Branched - Continuous daily updates. The Feature Freeze and String Freeze are started during this phase. The Alpha Freeze occurs as that milestone approaches. Installers and updaters receive close attention.
  • Alpha - Initial testing of all packages, which must be feature-complete by this point. The Beta Freeze occurs as that milestone approaches.
  • Beta - Wide testing of all packages. The Final Freeze occurs as that milestone approaches. See http://fedoraproject.org/get-prerelease to download.
  • Final Release - Suitable for the general public.

During the Branched, Alpha, Beta, and Final phases, a separate Rawhide version will continue to receive daily updates, and be developed in parallel to the code on the "stable release" track. For example, the Rawhide code that is being developed during Fedora 13 Branched, Alpha, Beta, and Final phases will become Fedora 14.

During the Branched, Alpha, and Beta phases, there will be "fedora" and "updates-testing" repositories. As updates are approved, they will move into the "fedora" repository. As the final release occurs, an "updates" repository will be created, and packages will move from "updates-testing" to "updates" instead of "fedora". The "rawhide" repository will always follow the Rawhide branch, and it receives all updates directly and untested.

During the Branched, Alpha, and Beta phases, daily spins of Live media are available at: http://alt.fedoraproject.org/pub/alt/nightly-composes/ These include only packages in the "stable" repository for that release, but that can include updates which have been approved for stable after the milestone date. The maximum size is now 1GB (intended for USB or DVD media, potentially too big for CD). Live spins are ideal for testing without disturbing an existing system.

During the testing phases following the Alpha and Beta releases, the distribution for those milestones can be downloaded at: http://fedoraproject.org/get-prerelease

Current Supported Releases

Currently maintained releases of Fedora are:

Old Unsupported Releases

History

Related