In the comment section one Red hatter says the differences will be minimal for Alma and Rocky, though some embargoed fix might be out. Seems mostly ok (I’d say for most use cases even CentOS Stream is ok)
That’s a Red Hat employee that has nothing to do with code. The comments about emabargoed stuff appearing in Red Hat before CentOS Stream are for coordinated code releases to fix a bug that’s not been released yet. (e.g. there’s a remote code exploit in the network stack related to intel NICs. Intel will coordinate with people like Red Hat and MS to get the release out in a coordinated fashion, but the data Intel supplies is embargoed until the coordinated release.)
So, while in theory someone who has a license can use source RPM’s to get at code, Rocky, and likely Alma, aren’t set up to deal with that as upstream sources. Plus, even though that matches the GPL (if someone sells you code, they have to supply source without restitrictions), I’d imagine the GPL doesn’t say that if someone sells a GPL’d product, they have to sell to you.
My guess is Alma and Rocky will figure a way around this, but id also guess it’s going to be tough.
In the comment section one Red hatter says the differences will be minimal for Alma and Rocky, though some embargoed fix might be out. Seems mostly ok (I’d say for most use cases even CentOS Stream is ok)
That’s a Red Hat employee that has nothing to do with code. The comments about emabargoed stuff appearing in Red Hat before CentOS Stream are for coordinated code releases to fix a bug that’s not been released yet. (e.g. there’s a remote code exploit in the network stack related to intel NICs. Intel will coordinate with people like Red Hat and MS to get the release out in a coordinated fashion, but the data Intel supplies is embargoed until the coordinated release.)
Rocky reports their release cycles are all tied to automation of the git repos that are going away. https://forums.rockylinux.org/t/has-red-hat-just-killed-rocky-linux/10378
So, while in theory someone who has a license can use source RPM’s to get at code, Rocky, and likely Alma, aren’t set up to deal with that as upstream sources. Plus, even though that matches the GPL (if someone sells you code, they have to supply source without restitrictions), I’d imagine the GPL doesn’t say that if someone sells a GPL’d product, they have to sell to you.
My guess is Alma and Rocky will figure a way around this, but id also guess it’s going to be tough.
Would this affect the lifecycle of Alma and Rocky? CentOS Stream had support for 5 years only, whereas RHEL comes with a 10 year support policy.