On Thu, 17 Dec 2020 at 04:45, Robin Opletal <me@xxxxxxxxxxxxxxxx> wrote:
I think this wouldn't be that much of a problem - what I think is bad is
that CentOS Stream security updates aren't going to come before RHEL's
will, and they will essentially be backported, at least as I understood
it.
a) CentOS regular security updates don't come before RHEL's so there is no change here.
Here is what happens currently for regular CentOS.
RHEL engineers do all their work internally and push their changes to a CDN. Customers then get those binaries.
The team which does these pushes then pushes the source code into the centos look-aside cache and the specs+patches into the git repo.
That team then sends an email to the CentOS admins who then start building the code. Then this loop begins
for (code is not built){
build code
if code builds and passes t_functional then break
else { check chain of rebuilds to see if order changed. if yes {break} if no check to see if more code was needed to be pushed.. get that pushed.. break}
endfor
push the updates to the mirrors for people.
If updates are a long time then the complaints go to the CentOS devels who will say 'it is ready when it is ready'.
Here is what happens differently with CentOS Stream... not much except that CentOS Stream is supposed to work and every failed compose, delay, etc is going to get a lot more media attention.. so no pressure folks (he says to himself as he goes to make sure that it keeps working).
Correct me if I am wrong
On Wed Dec 9, 2020 at 5:52 PM CET, Adam Williamson wrote:
> It's a rolling release *of a stable RHEL branch*. You're not getting
> radical new changes if you run CentOS Stream; you're just getting the
> changes you'd usually get in RHEL stable point releases (e.g. 8.1, 8.2
> etc) but getting them early and as they are produced, rather than in
> periodic lumps).
_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
--
Stephen J Smoogen.
_______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
