CentOS - Dec 2020 - CentOS Stream from bottom works, what is this?

On 12/9/20 8:54 AM, Bernstein, Noam CIV USN NRL (6393) Washington DC
(USA) via CentOS wrote:
> On Dec 9, 2020, at 9:45 AM, Johnny Hughes <johnny at
centos.org<mailto:johnny at centos.org>> wrote:
> 
> CentOS Stream is built from the currently released RHEL Source Code + 0.1
> 
> So if RHEL 8.3 is released .. Stream is the Source Code (built) that
> will become 8.4 in a few months.
> 
> If this statement is exactly correct, then I think a lot of the issues in
this thread may be easy to address.  However, the question is whether it is
really
> "That will become"
> or actually
> "That might become, if it turns out to be stable enough,"
> 
> I.e., to me the critical question is how often (in practice) will updates
that have problems, and will not actually make it into RHEL, end up in CentOS
Stream.  Presumably all such updates will be superseded in Stream by corrected
ones, before they're in RHEL.
> 
> In fact, would it be possible, to list the final versions of each
package's update at the moment of the RHEL release, and only do the CentOS
Stream update based on that list?
> 
There is one source for the source code that will be used.  While in
stream it will iterative (the push a bunch of changes today .. the build
those change today).  Those go through a CI process and get released
into stream.

When it comes time to build rhel 8.4 it will come from the same source code.

On Wed, 9 Dec 2020, Johnny Hughes wrote:
> On 12/9/20 8:54 AM, Bernstein, Noam CIV USN NRL (6393) Washington DC
> (USA) via CentOS wrote:
>> On Dec 9, 2020, at 9:45 AM, Johnny Hughes <johnny at
centos.org<mailto:johnny at centos.org>> wrote:
>>
>> CentOS Stream is built from the currently released RHEL Source Code +
0.1
>>
>> So if RHEL 8.3 is released .. Stream is the Source Code (built) that
>> will become 8.4 in a few months.
>>
>> If this statement is exactly correct, then I think a lot of the issues
in this thread may be easy to address.  However, the question is whether it is
really
>> "That will become"
>> or actually
>> "That might become, if it turns out to be stable enough,"
>>
>> I.e., to me the critical question is how often (in practice) will
updates that have problems, and will not actually make it into RHEL, end up in
CentOS Stream.  Presumably all such updates will be superseded in Stream by
corrected ones, before they're in RHEL.
>>
>> In fact, would it be possible, to list the final versions of each
package's update at the moment of the RHEL release, and only do the CentOS
Stream update based on that list?
>>
>
> There is one source for the source code that will be used.  While in
> stream it will iterative (the push a bunch of changes today .. the build
> those change today).  Those go through a CI process and get released
> into stream.
>
> When it comes time to build rhel 8.4 it will come from the same source
code.
If a bug were to make it into CentOS Stream, and identified before RHEL 
8.4 was released, would an updated/fixed package be produced and placed into 
CentOS Stream?

If a bug were to make it past CentOS Stream and into RHEL 8.4 and the bug 
is then identified and fixed after the release of RHEL 8.4 would an 
updated/fixed package be produced and placed into CentOS Stream in the 
same timeframe or only if/when updated packages and their dependencies 
were made/released into CentOS Stream for updated features for RHEL 8.5?

If the same happened in the previous question but was in a package or set 
of packages that was being rebased in 8.5 would it work the same way?

Thanks,
Barry

On Wed, 9 Dec 2020, Johnny Hughes wrote:
> On 12/9/20 8:54 AM, Bernstein, Noam CIV USN NRL (6393) Washington DC
> (USA) via CentOS wrote:
>> On Dec 9, 2020, at 9:45 AM, Johnny Hughes <johnny at
centos.org<mailto:johnny at centos.org>> wrote:
>>
>> CentOS Stream is built from the currently released RHEL Source Code +
0.1
>>
>> So if RHEL 8.3 is released .. Stream is the Source Code (built) that
>> will become 8.4 in a few months.
>>
>> If this statement is exactly correct, then I think a lot of the issues
in this thread may be easy to address.  However, the question is whether it is
really
>> "That will become"
>> or actually
>> "That might become, if it turns out to be stable enough,"
>>
>> I.e., to me the critical question is how often (in practice) will
updates that have problems, and will not actually make it into RHEL, end up in
CentOS Stream.  Presumably all such updates will be superseded in Stream by
corrected ones, before they're in RHEL.
>>
>> In fact, would it be possible, to list the final versions of each
package's update at the moment of the RHEL release, and only do the CentOS
Stream update based on that list?
>>
>
> There is one source for the source code that will be used.  While in
> stream it will iterative (the push a bunch of changes today .. the build
> those change today).  Those go through a CI process and get released
> into stream.
>
> When it comes time to build rhel 8.4 it will come from the same source
code.
So if I understand this correctly, centos8 + will basically be a rolling release
and we will never know what we are really running. Is this correct?

To put it another way all of the stability we are used to will be gone and in
order to stay up to date with stream I could potentially need to reboot machines
daily depending on what packages $REDHAT developer decides to work on that day.

Am I missing something?

Regards,

-- 
Tom			me at tdiehl.org