Adam :ansible: :linux: :bash:
I get the feeling too many people are sleeping on CentOS Stream because of how the CentOS #Linux EOL thing went down.
I mean sure, the messaging wasn't great but it happened and it is what it is. Don't let that detract from the greatness of the #CentOS Stream project in its own right and as a collaboration point for all the #RHEL based distros.
The gravity seems lost on most that for the first time ever the RHEL development process happens in the open. That's amazing. I love it. #community
Adam :ansible: :linux: :bash:
@vwbusguy biggest difference is you can actually contribute to CS. Alma is a rebuild and if you need to fix something or get a feature into Alma then you submit a merge request to CS and wait until it lands in Alma downstream.
Scott Williams 🐧
@maxamillion I would also be quick to point out that CS is part of the success story for AlmaLinux as they build against CS repos ahead of their own releases, which is part of why they're so quick to have stuff out when RHEL releases (especially compared to Rocky and Oracle who tend to have significant more lag).
Scott Williams 🐧
@maxamillion I don't have the bandwidth for this right now, but sometime I'd be curious to test the differences between CS and AlmaLinux with the testing repo enabled.
Scott Williams 🐧
@maxamillion That doesn't mean it isn't good or useful, but that it takes more intentional consideration in deploying it than CentOS Linux did.
Adam :ansible: :linux: :bash:
@vwbusguy fair
Scott Williams 🐧
@maxamillion This is unfortunately not trivial. I've had some trouble with filing Github issues against CentOS Stream because the upstream only now "supports Rocky", etc. Having to cut through the FUD around it gets tiring, honestly, but CS is still really nice for having fast track container patches and as a CI platform. I mean, I'm still using it very much, but I understand why there's preference for the rebuilds.
Scott Williams 🐧
@maxamillion While I agree, it's definitely not helping things that CentOS Stream still goes EOL well before RHEL, AlmaLinux, etc.
Adam :ansible: :linux: :bash:
@carlwgeorge @vwbusguy yes, this.
Scott Williams 🐧
@maxamillion @carlwgeorge Everyone has a test environment. Some are fortunate enough to have one that isn't their production.
Carl George :fedora: :centos:
@vwbusguy @maxamillion It sounds like you're describing a shop that applies updates in prod without first testing them in non-prod. How do they explain when a regression or change in RHEL brings down prod? It's not really different. Testing updates before deploying them in prod is a best practice no matter what OS you're using.
Scott Williams 🐧
@maxamillion Oh sure, I understand that as someone who is into contributing to open source and building stuff. It's a harder sell in a place that's just looking for a platform to run their production stuff. No one wants to risk having to explain that prod is down because of a patch in CS that broke something and the vendor no longer "supports CentOS" (even if it's eventually going to be a problem for the vendor in the next RHEL release).
Scott Williams 🐧
@carlwgeorge @maxamillion Sometimes things that are in CS that aren't in RHEL end up in the dev/testing repo for AlmaLinux. For example, when OpenLDAP got abruptly pulled and reinstated in RHEL, it became available in CS first and was in the Alma testing repos ahead of the next RHEL release that added it back in.
Carl George :fedora: :centos:
@vwbusguy @maxamillion It's going to be very close, because CentOS Stream is very close to RHEL itself. When I've measured it, it's typically 90-95% the same software versions depending on where in the cycle you are.
GNU social JP is a social network, courtesy of GNU social JP管理人. It runs on GNU social, version 2.0.2-dev, available under the GNU Affero General Public License.
All GNU social JP content and data are available under the Creative Commons Attribution 3.0 license.