In other languages: English (en) русский (ru) 中文（中國大陸）? (zh-cn) 中文（臺灣）? (zh-tw) 日本語(yǔ) (ja) [edit]

Fedora Project 每隔大約 6 個(gè)月發(fā)布一個(gè)新版本的 Fedora，并會(huì )在13個(gè)月內提供更新支持。This allows users to 'skip a release' while still being able to always have a system that is still receiving updates.

?? 開(kāi)發(fā)計劃

我們說(shuō)開(kāi)發(fā)或者發(fā)布周期“大約是6個(gè)月”，因為想很多其他事情一樣，它們偶爾會(huì )脫離計劃。

最近在開(kāi)發(fā)的版本Fedora 32的發(fā)行進(jìn)度在 發(fā)行進(jìn)度里可以找到. Alpha版，Beta版和 通用版(最終版)的發(fā)行通常是在美國東部時(shí)間的10:00am，也就是1500UTC或者1400UTC（得看夏時(shí)令是否生效）。

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

?? Steps to Construct a New Schedule

This is admittedly an unusual methodology, but it is fairly easy to generate using the the TaskJuggler schedules John Poelstra creates.

1. Pick GA 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

3. Set the feature submission and completion dates working backwards from the Branch Freeze date

4. The time between the feature submission deadline and the GA of the previous release is the time dedicated to development

• Development time varies from from release to release based on how when the previous release finished

• The freeze and testing time (from Branch Freeze until GA) 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 30 will be maintained until 1 month after the release of Fedora 32.

• Fedora 31 will be maintained until 1 month after the release of Fedora 33.

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

?? 生命周期結束 (EOL)

When the a release reaches the point where it no longer supported, updates are no longer created for it and 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.

?? 附加信息

• 查看目前所有發(fā)布的版本

• 不再受支持的版本

• 歷史發(fā)行計劃