On Fri, 2021-03-19 at 16:35 +0100, Miro Hrončok wrote: > With the current way of things (that could possibly change), when > EPEL 10 is > created, ELN is long gone in the RHEL 11 world. > > I could only imagine this scheme: > > ELN -> CentOS Stream N -> RHEL N > ELN Extra -> EPEL N Next -> EPEL N > > (With heroic efforts to align the arrows on the EPEL line to happen > very soon > after the arrows on the RHEL line.) > > Even if we somehow manage do this, what benefits does it bring over: > > ELN -> CentOS Stream N -> RHEL N > Rawhide/Branched -> EPEL N Next -> EPEL N > > ? There's two parts to this. On one hand, a package in eln-extra will be continuously built against ELN, and if the build breaks fixes will be pushed to Rawhide. This means that when the time comes to branch for the new EPEL, it's likely to work out of the box. The other point (and the one I'm specifically interested in) is that this makes it easier to do continuous testing using ELN. Specifically, my plan is to deploy ELN on a small number of systems and use it to spot potential issues and changes that would otherwise only show up when one starts testing the *next* CentOS Stream release. Ideally, this will make it easier to get stuff addressed and fixed in Rawhide, long before the next CentOS Stream even branches, which should results in benefits to both Fedora and CentOS Stream. However, to do this effectively I would also need to have a subset of EPEL available, as in reality we (as I suspect most people) always deploy CentOS Stream together with EPEL. So that's where the idea of having ELN builds for (a subset of) packages currently in EPEL started from, which then evolved in the eln-extra proposal that Troy posted here. Cheers Davide _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to 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/devel@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
