CentOS no longer downstream of RHEL

Cantor, Scott cantor.2 at osu.edu
Thu Oct 14 12:51:38 UTC 2021


On 10/14/21, 8:37 AM, "dev on behalf of Peter Schober" <dev-bounces at shibboleth.net on behalf of peter.schober at univie.ac.at> wrote:
 
> There's mention of the Rocky Linux CentOS fork in the context of
>  (internal) "project infrastructure"

I was happy to be proven wrong. Never seen so many people move so quickly outside of a post-Thanksgiving sale at a toy store.
    
> But will Rocky Linux be(come) the primary platform to build and test on? ;)

If you mean the SP, I have always primarily built and tested on Windows. Everything else is just sanity checked at best (usually not even that), and that's much more so now that I don't actually run any SPs.

I'll probably spin something up in AWS just so we have a reference point but realistically, we're now at the "author doesn't use his own software" stage with the SP, as we will eventually be with the IdP. And yes, that hurts the overall product, it can't do otherwise. Shibboleth's best attribute in the 20 years it's existed is that I always used it.

>    What are the project's plans with regard to officially supported
>    platforms after the end of the year (coinciding with the end of CentOS
>    Linux)?

The current set is likely to be at least:

RHEL 7/8
CentOS 7
Rocky 8
Amazon Linux 2

John can correct me, but I think that might be it initially. The only real change is losing SUSE, which...he did try but it was a mess getting it to work in AWS, and the only one I actually even have to "support" now is a dated, though still alive, SUSE Enterprise, plus outdated OpenSUSE.

I still plan to drop macOS officially unless there's clear member need.

We might do CentOS Stream just because, if it's easy. Anything we spin up in AWS that uses rpm could in theory be a target, it's just that some work better than others. If there are other clones people need, we can consider it.

But there's no "reference" choice for Linux, which seems to be your question, that's definitely Windows. Partly because Visual Studio is still the only debugger I can use in general, and partly because it's the most used platform and the most outlying in terms of what's involved in making it work and has both Apache and IIS available to test.

-- Scott




More information about the dev mailing list