I think new development needs to be able to advance at at least the speed of evolution of c++ and the shipping compiler and toolchain implementations in modern Linux distributions. How the project deals with retiring old stable releases is orthogonal, but I think Casey's position seems reasonable.
Matt
On Thu, Sep 14, 2023 at 12:06 PM Mark Nelson <mark.a.nelson@xxxxxxxxx> wrote:
We'll need to update the performance lab nodes (they are on Centos8
stream still), but that's not the end of the world. Honestly I was
planning on doing it anyway sooner or later.
I do have some concerns similar to Anthony. I know users who are still
running CentOS 7 in production and are just struggling to get off that.
We're pretty aggressive regarding needing Compiler/OS upgrades versus a
lot of projects out there and at times it feels somewhat unnecessary.
I guess my take is that there's a balancing act here. If supporting
older distros is a major burden and blocker for future growth it makes
sense to drop them. If we're dropping them because we want to chase
brand new C++ language features that are exciting and fun but not
fundamental for the project, that's less of a justification imho.
Mark
On 9/13/23 09:02, Casey Bodley wrote:
> now that Reef gives our users an upgrade path away from centos stream
> 8 and ubuntu 20.04, i propose that we drop support for those old
> distros from the S release. if there's agreement here, we can stop
> building/testing them on main asap
> _______________________________________________
> Dev mailing list -- dev@xxxxxxx
> To unsubscribe send an email to dev-leave@xxxxxxx
_______________________________________________
Dev mailing list -- dev@xxxxxxx
To unsubscribe send an email to dev-leave@xxxxxxx
--
Matt Benjamin
Red Hat, Inc.
315 West Huron Street, Suite 140A
Ann Arbor, Michigan 48103
http://www.redhat.com/en/technologies/storage
tel. 734-821-5101
fax. 734-769-8938
cel. 734-216-5309
_______________________________________________ Dev mailing list -- dev@xxxxxxx To unsubscribe send an email to dev-leave@xxxxxxx
