On Thu, Jul 25, 2024 at 8:41 AM Stephen Gallagher <sgallagh@xxxxxxxxxx> wrote: > > On Thu, Jul 25, 2024 at 8:01 AM <sgallagh@xxxxxxxxxx> wrote: > > > > Dear all, > > > > You are kindly invited to the meeting: > > ELN SIG on 2024-07-26 from 12:00:00 to 13:00:00 US/Eastern > > At fedora-meeting@xxxxxxxxxxxxxxx > > > > The meeting will be about: > > The sunsetting of the ELN Extras sub-project and brainstorming how to > work with the EPEL project to have EPEL 11 built against ELN until > CentOS Stream 11 branches. The following meeting summary was going to be brought to you by ChatGPT, but it missed the mark so badly that I think it may actually have been trained by an Imperial Stormtrooper... so I've rewritten it completely from scratch. Full meeting logs: https://meetbot.fedoraproject.org/meeting_matrix_fedoraproject-org/2024-07-26/eln.2024-07-26-16.00.log.html # Meeting Summary ## Participants: yselkowitz Davide Cavalca Stephen Gallagher Michel Lind Troy Dawson Carl George Conan Kudo ## Sunsetting ELN Extras We discussed the current state of ELN Extras, particularly the fact that it has proven a failure of its original stated mission to prepare for EPEL 10. We discussed that it still has some value in helping prepare spec files for eventual EPEL usage, but ultimately it cannot be used directly for import to EPEL. We discussed new plans for how we might proceed instead. Most notably, we decided that it would probably serve us better if it was migrated under the EPEL umbrella rather than the ELN one, since EPEL has a much more recognizable brand. Our current high-level plan (to be implemented once EPEL 10 is launched) is as follows: - phase 1: no branches, no commits, just automatic rebuilds of rawhide packages using eln as a buildroot. basically eln extras rebranded as epel11, implemented with epel11 koji tags. - phase 2: mass branching from rawhide to epel11 for a planned set of content, at the same time as the c11s branching. no more automatic rebuilds, manual builds using c11s as a buildroot. added in bodhi, with rawhide-style automatic creation of updates. - phase 3: official epel launch, disabling automatic creation of bodhi updates, enabling epel-testing repo This will need to be broken down into workable tasks. I have volunteered to prepare a first draft based on discussion and feedback in this meeting and at the Flock to Fedora conference in a week and a half. Many other rabbit-holes and tangents were explored during the meeting, and for these I encourage you to review the full logs. -- _______________________________________________ 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, report it: https://pagure.io/fedora-infrastructure/new_issue
