06-21-2019, 01:30 PM
Making Fedora 30
<div style="margin: 5px 5% 10px 5%;"><img src="http://www.sickgaming.net/blog/wp-content/uploads/2019/06/making-fedora-30.png" width="256" height="256" title="" alt="" /></div><div><p>What does it take to make a Linux distribution like Fedora 30? As you might expect, it’s not a simple process.</p>
<p> <span id="more-28415"></span> </p>
<h2>Changes in Fedora 30</h2>
<p>Although Fedora 29 released on October 30, 2018, work on Fedora 30 began long before that. The first change proposal was submitted in late August. By my count, contributors made nine separate change proposals for Fedora 30 before Fedora 29 shipped.</p>
<p>Some of these proposals come early because they have a big impact, like mass removal of Python 2 packages. By the time the proposal deadline arrived in early January, the community had submitted 50 change proposals.</p>
<div class="wp-block-image">
<figure class="alignleft is-resized"><img src="http://www.sickgaming.net/blog/wp-content/uploads/2019/06/making-fedora-30.png" alt="" class="wp-image-28436" width="222" height="222" /></figure>
</div>
<p>Of course, not all change proposals make it into the shipped release. Some of them are more focused on <em>how</em> we build the release instead of <em>what</em> we release. Others don’t get done in time. System-wide changes must have a contingency plan. These changes are generally evaluated at one of three points in the schedule: when packages branch from Rawhide, at the beginning of the Beta freeze, and at the beginning of the Final freeze. For Fedora 30, <strong>45 Change proposals</strong> were still active for the release.</p>
<p>Fedora has a calendar-based release schedule, but that doesn’t mean we ship whatever exists on a given date. We have a set of <a href="https://fedoraproject.org/wiki/Fedora_30_Final_Release_Criteria">release criteria</a> that we test against, and we don’t put out a release until all the blockers are resolved. This sometimes means a release is delayed, but it’s important that we ship reliable software.</p>
<p>For the Fedora 30 development cycle, we accepted 22 proposed blocker bugs and rejected 6. We also granted 33 freeze exceptions — bugs that can be fixed during the freeze because they impact the released artifacts or are otherwise important enough to include in the release.</p>
<h2>Other contributions</h2>
<p>Of course, there’s more to making a release than writing or packaging the code, testing it, and building the images. As with every release, the Fedora Design team created a new desktop background along with several <a href="https://fedoramagazine.org/fedora-30-supplemental-wallpapers/">supplemental wallpapers</a>. The <a href="https://fedoraproject.org/wiki/Marketing">Fedora Marketing team</a> wrote release announcements and put together talking points for the <a href="https://fedoraproject.org/wiki/Ambassadors">Ambassadors</a> and <a href="https://fedoraproject.org/wiki/Advocates">Advocates</a> to use when talking to the broader community. </p>
<p>If you’ve looked at our new <a href="https://getfedora.org/">website</a>, that was the work of the Websites team in preparation for the Fedora 30 release:</p>
<figure class="wp-block-image"><img src="http://www.sickgaming.net/blog/wp-content/uploads/2019/06/making-fedora-30-1.png" alt="" class="wp-image-28426" /></figure>
<p>The Documentation Team wrote Release Notes and updated other <a href="https://docs.fedoraproject.org/en-US/fedora/f30/">documentation</a>. Translators provided translations to <a href="https://fedora.zanata.org/version-group/view/PriorityPackages?dswid=7939">dozens of languages</a>.</p>
<p>Many other people made contributions to the release of Fedora 30 in some way. It’s not easy to count everyone who has a hand in producing a Linux distribution, but we appreciate every one of our contributors. If you would like to join the Fedora Community but aren’t sure where to start, check out <a href="https://whatcanidoforfedora.org/">What Can I Do For Fedora?</a></p>
<hr class="wp-block-separator" />
<p><em>Photo by </em><a href="https://unsplash.com/@robin_sommer?utm_source=unsplash&utm_medium=referral&utm_content=creditCopyText"><em>Robin Sommer</em></a><em> on </em><a href="https://unsplash.com/search/photos/factory?utm_source=unsplash&utm_medium=referral&utm_content=creditCopyText"><em>Unsplash</em></a>.</p>
</div>
<div style="margin: 5px 5% 10px 5%;"><img src="http://www.sickgaming.net/blog/wp-content/uploads/2019/06/making-fedora-30.png" width="256" height="256" title="" alt="" /></div><div><p>What does it take to make a Linux distribution like Fedora 30? As you might expect, it’s not a simple process.</p>
<p> <span id="more-28415"></span> </p>
<h2>Changes in Fedora 30</h2>
<p>Although Fedora 29 released on October 30, 2018, work on Fedora 30 began long before that. The first change proposal was submitted in late August. By my count, contributors made nine separate change proposals for Fedora 30 before Fedora 29 shipped.</p>
<p>Some of these proposals come early because they have a big impact, like mass removal of Python 2 packages. By the time the proposal deadline arrived in early January, the community had submitted 50 change proposals.</p>
<div class="wp-block-image">
<figure class="alignleft is-resized"><img src="http://www.sickgaming.net/blog/wp-content/uploads/2019/06/making-fedora-30.png" alt="" class="wp-image-28436" width="222" height="222" /></figure>
</div>
<p>Of course, not all change proposals make it into the shipped release. Some of them are more focused on <em>how</em> we build the release instead of <em>what</em> we release. Others don’t get done in time. System-wide changes must have a contingency plan. These changes are generally evaluated at one of three points in the schedule: when packages branch from Rawhide, at the beginning of the Beta freeze, and at the beginning of the Final freeze. For Fedora 30, <strong>45 Change proposals</strong> were still active for the release.</p>
<p>Fedora has a calendar-based release schedule, but that doesn’t mean we ship whatever exists on a given date. We have a set of <a href="https://fedoraproject.org/wiki/Fedora_30_Final_Release_Criteria">release criteria</a> that we test against, and we don’t put out a release until all the blockers are resolved. This sometimes means a release is delayed, but it’s important that we ship reliable software.</p>
<p>For the Fedora 30 development cycle, we accepted 22 proposed blocker bugs and rejected 6. We also granted 33 freeze exceptions — bugs that can be fixed during the freeze because they impact the released artifacts or are otherwise important enough to include in the release.</p>
<h2>Other contributions</h2>
<p>Of course, there’s more to making a release than writing or packaging the code, testing it, and building the images. As with every release, the Fedora Design team created a new desktop background along with several <a href="https://fedoramagazine.org/fedora-30-supplemental-wallpapers/">supplemental wallpapers</a>. The <a href="https://fedoraproject.org/wiki/Marketing">Fedora Marketing team</a> wrote release announcements and put together talking points for the <a href="https://fedoraproject.org/wiki/Ambassadors">Ambassadors</a> and <a href="https://fedoraproject.org/wiki/Advocates">Advocates</a> to use when talking to the broader community. </p>
<p>If you’ve looked at our new <a href="https://getfedora.org/">website</a>, that was the work of the Websites team in preparation for the Fedora 30 release:</p>
<figure class="wp-block-image"><img src="http://www.sickgaming.net/blog/wp-content/uploads/2019/06/making-fedora-30-1.png" alt="" class="wp-image-28426" /></figure>
<p>The Documentation Team wrote Release Notes and updated other <a href="https://docs.fedoraproject.org/en-US/fedora/f30/">documentation</a>. Translators provided translations to <a href="https://fedora.zanata.org/version-group/view/PriorityPackages?dswid=7939">dozens of languages</a>.</p>
<p>Many other people made contributions to the release of Fedora 30 in some way. It’s not easy to count everyone who has a hand in producing a Linux distribution, but we appreciate every one of our contributors. If you would like to join the Fedora Community but aren’t sure where to start, check out <a href="https://whatcanidoforfedora.org/">What Can I Do For Fedora?</a></p>
<hr class="wp-block-separator" />
<p><em>Photo by </em><a href="https://unsplash.com/@robin_sommer?utm_source=unsplash&utm_medium=referral&utm_content=creditCopyText"><em>Robin Sommer</em></a><em> on </em><a href="https://unsplash.com/search/photos/factory?utm_source=unsplash&utm_medium=referral&utm_content=creditCopyText"><em>Unsplash</em></a>.</p>
</div>