blog.centos.orgの記事: 引用した原文

【5】Balancing the needs around the CentOS platform

https://blog.centos.org/2020/12/balancing-the-needs-around-the-centos-pl...
12/19/2020 Karsten Wade

【原文】

Providing our community with a solid, reliable distro that is good-enough for your workloads is a strong part of the CentOS brand. We’re confident that CentOS Stream can do this.

And while I’m certain now that CentOS Linux cannot do what CentOS Stream can to solve the openness gap, I am confident that CentOS Stream can cover 95% (or so) of current user workloads stuck on the various sides of the availability gap.

It is hard to balance the needs and processes of making business decisions with the needs and processes of making open community decisions. Arguably, Red Hat has been among the best organizations at straddling this hard, thin line. If you trust our code enough to run it for this long, I ask you to trust us to make good decisions here. I ask you to trust Red Hat and the CentOS Board to work with you to find a way to bring the community along into the next chapter.

【4】How RHEL is Made

https://blog.centos.org/2020/12/how-rhel-is-made/
12/11/2020 Brendan Conoboy

【原文】

Many people who use CentOS Linux today now wonder if CentOS Stream 8 will be a suitable distribution for their use: is it tested, will it be stable? If you want to know what to expect from CentOS Stream, the best starting point is knowing how Red Hat Enterprise Linux is built. Let’s get into it!

every RHEL minor release is based on the previous release, plus targeted backports of upstream development. Often, Red Hatters are the original authors of those patches, but there are no shortcuts: upstream acceptance is the first test every patch must go through before we start it through the journey that eventually leads to a patch’s integration in the release. Even then, this is about an upstream patch existing, but that alone will not guarantee a patch’s inclusion.

Any decision to introduce an upstream change into RHEL is a team decision and the team is large: developers, quality engineers, support personnel, product owners, and various partners all work together on priority and feasibility. Once a decision is reached and commitments are made, only then do developers and quality engineers begin writing code. As you probably know, in the most congenial of rivalries, developers try to write code that nobody can break and quality engineers create batteries of ways to break the code developers write. This brings us to the second key place where Red Hat invests: tests.


We write tests for everything: unit tests, systemic tests, kernel and userspace ABI conformance tests, performance tests, dependency tests, architecture tests, driver tests, load tests, and many more. Having tests is foundational, but it is their application that brings meaning. This brings us to the third key area where Red Hat invests: process infrastructure.

When a change is targeted at RHEL, multiple incremental steps occur before it is actually included. Changes are built, but the only certain outcome is that a CI system will run a suite of tests on the builds (the build is not yet made available for general use). If those tests pass, a second round of preverification specific to the code change occurs (not yet good enough). And if those tests pass, the change is tentatively included in the errata system and subject to further verification (it’s still not ready to publish). Systemic test suites run on the combined whole to verify the gestalt functionality. And if those tests pass, the build will finally make it into the space where CentOS Stream systems recognize it as an available update. It’s a long pipeline and many changes move through it every single day. For those interested in more of the vision and architecture of this system, you can read more in CentOS Stream is Continuous Delivery!

it is already happening today with RHEL 8.4 and CentOS Stream 8! At the same time these RHEL builds are verified, they are also delivered to CentOS Stream. Of course we aren’t done yet:

【3】Minutes for CentOS Board of Directors for 2020-11-11

https://blog.centos.org/2020/12/minutes-for-centos-board-of-directors-fo...
12/11/2020 Thomas Oulevey

【原文】

The Board was in an Executive session, where Red Hat CTO, Chris Wright joined to present Red Hat plan around CentOS Linux and CentOS Stream. A Board discussion followed.

Following up the discussion around the different users' communities impacted by proposed changes, Chris Wright, mentioned to the Board that Red Hat is also reshaping and expanding the RHEL Developer program. The details will be communicated through standard Red Hat channels.

The following resolutions were approved by the majority of the Board :

CentOS Stream 8 will continue with contributions for the full-support phase of RHEL 8. APPROVED
CentOS Stream 9 will start on schedule with the RHEL 9 Beta. APPROVED
CentOS Linux 9 will not start. APPROVED
CentOS Linux 8 ends in December 2021. APPROVED

An announcement and detailed FAQ will be prepared in next weeks.

【2】CentOS Stream is Continuous Delivery

https://blog.centos.org/2020/12/centos-stream-is-continuous-delivery/
12/11/2020 Stef Walter

【原文】

The “Always Ready RHEL” effort now continues with continuous delivery, which you now know as CentOS Stream: the RHEL nightly composes are already delivered in CentOS Stream. The whole point of continuous delivery is to make each release as stable as the one before. We’re delivering daily.

To the untrained eye, CentOS Stream is
already as stable as RHEL.

But the challenge here is unparalleled, and RHEL engineers carry awareness of that. The way the different teams do their work integrating RHEL is as diverse as the upstream communities themselves. Yet because so many people are iterating together toward different aspects of this goal, I’m convinced we can make Continuous Delivery a reality..
          原図: https://blog.centos.org/wp-content/uploads/2020/12/fedora-centos-stream-... より

Technically speaking, CentOS Stream and RHEL updates are two binary packages built from the same source. An update will be published to CentOS Stream if and only if it is published to the RHEL nightly builds. Thus the RHEL nightly builds are the CentOS Stream updates you get. Once we branch from Fedora, our development gets into a stride where each change is integrated cleanly on top of everything that went before. An update is pushed to CentOS Stream if and only if it is published to the unreleased minor update of RHEL. RHEL customers later see each of these as a RHEL Errata update.

Each of these changes, whether bug fixes or features, is tested via automated tests and verified by Quality Engineering processes before landing in CentOS Stream.

The only work not directly and immediately visible in Stream is the work we do on the already-released RHEL minor versions themselves (indicated as “errata” in the diagram). Often this work is done under NDA, are embargoed, or are backports of changes already in CentOS Stream.

CentOS Stream intends to be as stable as RHEL,
It’s fundamental to continuous delivery.

But hey, even the RHEL-released product is not completely stable.