From Fedora Project Wiki
m (サブタイトルの和訳)
m (1.2まで和訳の追記)
Line 8: Line 8:


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.
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.
だいたい半年ごとと言いましたが、これは、概して、いつも計画通りに行かないからです。予定の基準は、時間に厳しくはしておらず、時間と品質を織り交ぜています。節目のリリースでは、[[Fedora Release Criteria]]準拠の[[QA:Release_validation_test_plan|テスト]]がされており、そうでない場合には、リリースが延期されます。


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.
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) ===
開発真っ最中のリリースに向けたスケジュール({{FedoraVersion|full|next}})は、[[Releases/{{FedoraVersion||next}}/Schedule|リリーススケジュール]]のページにあります。β版と一般公開版(最終版)リリースは、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]].
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]].
Fedoraの開発計画は、[[Changes/Policy|Release Planning Process]]に従って策定されます。いわゆる''変更''が提案されると、最初に[[Fedora_Engineering_Steering_Committee|engineering steering committee]]が、レビューし、開発中は、進捗管理されます。


=== 開発の手順(Development Process) ===
=== 開発の手順(Development Process) ===


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.
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.
Fedoraは、二つの開発ツリーにまたがるシステムを使います。[[Releases/Rawhide|Rawhide]]は、常に開発中のツリーです。Rawhideから直接リリースビルドが作られることはないです。Fedoraのリリース日のだいたい10週間前になると、リリースのためのツリーが、Rawhideのツリーから"[[Releases/Branched|Branched]]"されます。


{{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.}}
{{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.}}
{{admon/tip|Fedoraリリースの誕生|Fedoraのリリースに向けた開発は、Rawhideから枝分かれされた、リリースの前の状態から始まると解釈されます。例えば、{{FedoraVersion|long|next}}の開発は、{{FedoraVersion|long}} がRawhideから枝分かれされた次の日に始まり、安定化に向けた流れがに入っています。}}


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.
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.
[[Updates Policy#Bodhi enabling|Bodhiが有効にされた]]後には、[[Bodhi]]システムは、Branchedリリースに対して、常に稼働し続けます(EOLまでずっと)。''安定した''と見なされるための更新についての要件は、[[Updates Policy]]に記載されています。パッケージは、[[Repositories#stable|''stable'']]レポジトリに入る前に、リリースのための[[Repositories#updates-testing|''updates-testing'']]レポジトリを経由しなければなりません。これは、[[Updates Policy]]で定義されているルールによるものです。これらのルールは、β版から一般公開版(最終版)までの間徐々に厳しくなります。基本的な流れは変わりません。


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.
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.
節目(β版や最終版)となりリリース前のしばらくの間は、[[Milestone freezes|freeze]]という状態が有効になります。[[QA:SOP_blocker_bug_process|blocker]] そして [[QA:SOP_freeze_exception_bug_process|freeze exception]] バグポリシーに従わないパッケージを''updates-testing'' から ''stable'' に移動できません。


=== 予定の立て方(Schedule Methodology) ===
=== 予定の立て方(Schedule Methodology) ===

Revision as of 07:12, 1 April 2019

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.

Fedoraプロジェクトは、だいたい半年ごとに新しいバージョンをリリースし、だいたい13ヶ月間ごとに更新されたパッケージ(保守管理業務として)を提供します。これは、ユーザに一つのリリースをスキップすることを許し、いつでもパッケージの更新を引き続き受けることができる仕組みを実現しています。

開発スケジュール(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.

だいたい半年ごとと言いましたが、これは、概して、いつも計画通りに行かないからです。予定の基準は、時間に厳しくはしておらず、時間と品質を織り交ぜています。節目のリリースでは、Fedora Release Criteria準拠のテストがされており、そうでない場合には、リリースが延期されます。

The schedule for the release currently under development, Fedora 40, is on its release schedule page. Beta, and General Availability (final) releases happen at 14:00 UTC.

開発真っ最中のリリースに向けたスケジュール(Fedora 40)は、リリーススケジュールのページにあります。β版と一般公開版(最終版)リリースは、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.

Fedoraの開発計画は、Release Planning Processに従って策定されます。いわゆる変更が提案されると、最初に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.

Fedoraは、二つの開発ツリーにまたがるシステムを使います。Rawhideは、常に開発中のツリーです。Rawhideから直接リリースビルドが作られることはないです。Fedoraのリリース日のだいたい10週間前になると、リリースのためのツリーが、Rawhideのツリーから"Branched"されます。

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 40 began the day after Fedora 39 branched from Rawhide and entered the stabilization process.
Idea.png
Fedoraリリースの誕生
Fedoraのリリースに向けた開発は、Rawhideから枝分かれされた、リリースの前の状態から始まると解釈されます。例えば、Fedora 40の開発は、Fedora 39 がRawhideから枝分かれされた次の日に始まり、安定化に向けた流れがに入っています。


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.

Bodhiが有効にされた後には、Bodhiシステムは、Branchedリリースに対して、常に稼働し続けます(EOLまでずっと)。安定したと見なされるための更新についての要件は、Updates Policyに記載されています。パッケージは、stableレポジトリに入る前に、リリースのためのupdates-testingレポジトリを経由しなければなりません。これは、Updates Policyで定義されているルールによるものです。これらのルールは、β版から一般公開版(最終版)までの間徐々に厳しくなります。基本的な流れは変わりません。

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.

節目(β版や最終版)となりリリース前のしばらくの間は、freezeという状態が有効になります。blocker そして freeze exception バグポリシーに従わないパッケージをupdates-testing から stable に移動できません。

予定の立て方(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 38 will be maintained until 1 month after the release of Fedora 40.
  • Fedora 39 will be maintained until 1 month after the release of Fedora 41.

保守管理予定の根拠(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)