02-27-2020, 05:22 AM
How we decide when to release Fedora
<div><p>Open source projects can use a variety of different models for deciding when to put out a release. Some projects release on a set schedule. Others decide on what the next release should contain and release whenever that is ready. Some just wake up one day and decide it’s time to release. And other projects go for a rolling release model, avoiding the question entirely.</p>
<p>For Fedora, we go with a <a href="https://fedoraproject.org/wiki/Fedora_Release_Life_Cycle#Development_Schedule">schedule-based approach</a>. Releasing twice a year means we can give our contributors time to implement large changes while still keeping on the leading edge. Targeting releases for the end of April and the end of October gives everyone predictability: contributors, users, upstreams, and downstreams.</p>
<p>But it’s not enough to release whatever’s ready on the scheduled date. We want to make sure that we’re releasing <em>quality</em> software. Over the years, the Fedora community has developed a set of processes to help ensure we can meet both our time and and quality targets.</p>
<h2>Changes process</h2>
<p>Meeting our goals starts months before the release. Contributors propose changes through our <a href="https://docs.fedoraproject.org/en-US/program_management/changes_policy/">Changes process</a>, which ensures that the community has a chance to provide input and be aware of impacts. For changes with a broad impact (called “system-wide changes”), we require a contingency plan that describes how to back out the change if it’s broken or won’t be ready in time. In addition, the change process includes providing steps for testing. This helps make sure we can properly verify the results of a change. </p>
<p>Change proposals are due 2-3 months before the beta release date. This gives the community time to evaluate the impact of the change and make adjustments necessary. For example, a new compiler release might require other package maintainers to fix bugs exposed by the new compiler or to make changes that take advantage of new capabilities.</p>
<p>A few weeks before the beta and final releases, we enter a <a href="https://fedoraproject.org/wiki/Milestone_freezes">code freeze</a>. This ensures a stable target for testing. Bugs identified as blockers and non-blocking bugs that are granted a freeze exception are updated in the repo, but everything else must wait. The freeze lasts until the release.</p>
<h2>Blocker and freeze exception process</h2>
<p>In a project as large as Fedora, it’s impossible to test every possible combination of packages and configurations. So we have a set of test cases that we run to make sure the key features are covered.</p>
<p>As much as we’d like to ship with zero bugs, if we waited until we reached that state, there’d never be another Fedora release again. Instead, we’ve defined release criteria that define what bugs can <a href="https://fedoraproject.org/wiki/QA:SOP_blocker_bug_process">block the release</a>. We have <a href="https://fedoraproject.org/wiki/Basic_Release_Criteria">basic release criteria</a> that apply to all release milestones, and then separate, cumulative criteria for <a href="https://fedoraproject.org/wiki/Fedora_32_Beta_Release_Criteria">beta</a> and <a href="https://fedoraproject.org/wiki/Fedora_32_Final_Release_Criteria">final</a> releases. With beta releases, we’re generally a little more forgiving of rough edges. For a final release, it needs to pass all of beta’s criteria, plus some more that help make it a better user experience.</p>
<p>The week before a scheduled release, we hold a “<a href="https://fedoraproject.org/wiki/Go_No_Go_Meeting">go/no go meeting</a>“. During this meeting, the QA team, release engineering team, and the Fedora Engineering Steering Committee (FESCo) decide whether or not we will ship the release. As part of the decision process, we conduct a final review of blocker bugs. If any accepted blockers remain, we push the release back to a later date.</p>
<p>Some bugs aren’t severe enough to block the release, but we still would like to get them fixed before the release. This is particularly true of bugs that affect the live image experience. In that case, we grant an <a href="https://fedoraproject.org/wiki/QA:SOP_freeze_exception_bug_process">exception for updates that fix those bugs</a>.</p>
<h2>How you can help</h2>
<p>In all my years as a Fedora contributor, I’ve never heard the QA team say “we don’t need any more help.” Contributing to the pre-release testing processes can be a great way to make your first Fedora contribution.</p>
<p>The Blocker Review meetings happen most Mondays in #fedora-blocker-review on IRC. All members of the Fedora community are welcome to participate in the discussion and voting. One particularly useful contribution is to look at the <a href="https://qa.fedoraproject.org/blockerbugs/">proposed blockers</a> and see if you can reproduce them. Knowing if a bug is widespread or not is important to the blocker decision.</p>
<p>In addition, the QA team conducts test days and test weeks focused on various parts of the distribution: the kernel, GNOME, etc. Test days are announced on <a href="https://fedoramagazine.org/tag/test-day/">Fedora Magazine</a>.</p>
<p>There are plenty of other ways to contribute to the QA process. The Fedora wiki has a <a href="https://fedoraproject.org/wiki/QA/Join">list of tasks and how to contact the QA team</a>. The Fedora 32 Beta release is a few weeks away, so now’s a great time to get started!</p>
</div>
https://www.sickgaming.net/blog/2020/02/...se-fedora/
<div><p>Open source projects can use a variety of different models for deciding when to put out a release. Some projects release on a set schedule. Others decide on what the next release should contain and release whenever that is ready. Some just wake up one day and decide it’s time to release. And other projects go for a rolling release model, avoiding the question entirely.</p>
<p>For Fedora, we go with a <a href="https://fedoraproject.org/wiki/Fedora_Release_Life_Cycle#Development_Schedule">schedule-based approach</a>. Releasing twice a year means we can give our contributors time to implement large changes while still keeping on the leading edge. Targeting releases for the end of April and the end of October gives everyone predictability: contributors, users, upstreams, and downstreams.</p>
<p>But it’s not enough to release whatever’s ready on the scheduled date. We want to make sure that we’re releasing <em>quality</em> software. Over the years, the Fedora community has developed a set of processes to help ensure we can meet both our time and and quality targets.</p>
<h2>Changes process</h2>
<p>Meeting our goals starts months before the release. Contributors propose changes through our <a href="https://docs.fedoraproject.org/en-US/program_management/changes_policy/">Changes process</a>, which ensures that the community has a chance to provide input and be aware of impacts. For changes with a broad impact (called “system-wide changes”), we require a contingency plan that describes how to back out the change if it’s broken or won’t be ready in time. In addition, the change process includes providing steps for testing. This helps make sure we can properly verify the results of a change. </p>
<p>Change proposals are due 2-3 months before the beta release date. This gives the community time to evaluate the impact of the change and make adjustments necessary. For example, a new compiler release might require other package maintainers to fix bugs exposed by the new compiler or to make changes that take advantage of new capabilities.</p>
<p>A few weeks before the beta and final releases, we enter a <a href="https://fedoraproject.org/wiki/Milestone_freezes">code freeze</a>. This ensures a stable target for testing. Bugs identified as blockers and non-blocking bugs that are granted a freeze exception are updated in the repo, but everything else must wait. The freeze lasts until the release.</p>
<h2>Blocker and freeze exception process</h2>
<p>In a project as large as Fedora, it’s impossible to test every possible combination of packages and configurations. So we have a set of test cases that we run to make sure the key features are covered.</p>
<p>As much as we’d like to ship with zero bugs, if we waited until we reached that state, there’d never be another Fedora release again. Instead, we’ve defined release criteria that define what bugs can <a href="https://fedoraproject.org/wiki/QA:SOP_blocker_bug_process">block the release</a>. We have <a href="https://fedoraproject.org/wiki/Basic_Release_Criteria">basic release criteria</a> that apply to all release milestones, and then separate, cumulative criteria for <a href="https://fedoraproject.org/wiki/Fedora_32_Beta_Release_Criteria">beta</a> and <a href="https://fedoraproject.org/wiki/Fedora_32_Final_Release_Criteria">final</a> releases. With beta releases, we’re generally a little more forgiving of rough edges. For a final release, it needs to pass all of beta’s criteria, plus some more that help make it a better user experience.</p>
<p>The week before a scheduled release, we hold a “<a href="https://fedoraproject.org/wiki/Go_No_Go_Meeting">go/no go meeting</a>“. During this meeting, the QA team, release engineering team, and the Fedora Engineering Steering Committee (FESCo) decide whether or not we will ship the release. As part of the decision process, we conduct a final review of blocker bugs. If any accepted blockers remain, we push the release back to a later date.</p>
<p>Some bugs aren’t severe enough to block the release, but we still would like to get them fixed before the release. This is particularly true of bugs that affect the live image experience. In that case, we grant an <a href="https://fedoraproject.org/wiki/QA:SOP_freeze_exception_bug_process">exception for updates that fix those bugs</a>.</p>
<h2>How you can help</h2>
<p>In all my years as a Fedora contributor, I’ve never heard the QA team say “we don’t need any more help.” Contributing to the pre-release testing processes can be a great way to make your first Fedora contribution.</p>
<p>The Blocker Review meetings happen most Mondays in #fedora-blocker-review on IRC. All members of the Fedora community are welcome to participate in the discussion and voting. One particularly useful contribution is to look at the <a href="https://qa.fedoraproject.org/blockerbugs/">proposed blockers</a> and see if you can reproduce them. Knowing if a bug is widespread or not is important to the blocker decision.</p>
<p>In addition, the QA team conducts test days and test weeks focused on various parts of the distribution: the kernel, GNOME, etc. Test days are announced on <a href="https://fedoramagazine.org/tag/test-day/">Fedora Magazine</a>.</p>
<p>There are plenty of other ways to contribute to the QA process. The Fedora wiki has a <a href="https://fedoraproject.org/wiki/QA/Join">list of tasks and how to contact the QA team</a>. The Fedora 32 Beta release is a few weeks away, so now’s a great time to get started!</p>
</div>
https://www.sickgaming.net/blog/2020/02/...se-fedora/