Am 08.12.20 um 19:56 schrieb Japheth Cleaver:
With point releases, at least there was the possibility of flag days around EPEL ABI changes, however with a rolling release format there seems to need to be an active synchronization around such changes, as "expected" breakages aren't really occurring around a public release cycle.
Agreed, I also support some kind of "flag day" support. Sometimes you just have to push an incompatible update and as an EPEL user it would be much easier to me if I could schedule these updates a bit better.
Though after reading the announcement I'm not sure about my interest in EPEL 8+ in the coming years. Just a few weeks ago I replaced the last remaining CentOS 8 server with Fedora so my customers just have a somewhat sizeable fleet of RHEL 7/CentOS 7 machines in production. When CentOS does not track RHEL anymore that puts a big question mark behind my plans regarding RHEL/CentOS 8+.
I won't make any radicale changes right now but right now I feel like just maintaining the EPEL 8 branches for my packages as long CentOS still tracks RHEL. I'll try to stay positive but I feel very 2020 after reading the press release.
Felix _______________________________________________ epel-devel mailing list -- epel-devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to epel-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/epel-devel@xxxxxxxxxxxxxxxxxxxxxxx
