On Tue, 11 Oct 2022 at 14:34, Troy Dawson <tdaw...@redhat.com> wrote:
> On Thu, Oct 6, 2022 at 8:50 AM Stephen Smoogen <ssmoo...@redhat.com> > wrote: > >> >> >> On Wed, 31 Aug 2022 at 17:08, Stephen Smoogen <ssmoo...@redhat.com> >> wrote: >> >>> >>> When EPEL-8 was launched, it came with some support for modules with the >>> hope that a module ecosystem could be built from Fedora packages using RHEL >>> modules as an underlying tool. This has never happened and we have ended up >>> with a muddle of modular packages which will 'build' but may not install or >>> even run on an EL-8 system. Attempts to fix this and work within how EPEL >>> is normally built have been tried for several years by different people but >>> have not worked. >>> >>> At this point it is time to say this experiment with modules in EPEL has >>> not worked and focus resources on what does work. I would like to propose >>> that modular support is removed from EPEL by January 2023. >>> >>> Steps: >>> 1. Approval of this proposal by the EPEL Steering committee and any >>> other ones required. >>> 2. Announcement of end of life to various lists. >>> 3. Archiving of the modules on XYZ date to >>> /pub/archive/epel/8.YYYY-MM/Modular and pointing mirrormanager to that for >>> that >>> 4. Make changes in bodhi to turn off reporting about modules for EL8. >>> 5. Make changes in MBS configs to turn off building modules for EL8. >>> 6. Make changes in PDC for EL8 modules >>> 7. Make changes in compose scripts and tools to no longer cover EPEL-8 >>> modules >>> 8. Remove epel-8 modules from /pub/epel/8 >>> 9. Announce closure of this proposal and any lessons learned. >>> >>> >> Due to the year end freezes that many Enterprise consumers are starting, >> I would like to propose the change to the timeline >> >> 2b. Make changes to epel-release so that EPEL modular is no longer turned >> on by default with README. >> 2c. Document configuration changes that would be needed for sites >> mirroring using Enterprise patch management systems. >> 3a. Start regular Archiving of the modules on XYZ date to >> /pub/archive/epel/8 >> 3b. and pointing mirrormanager to that for that >> >> We can do steps up to 3a. and then start on 3b and other items after >> February 1st 2023. >> > > Just letting people know, adjusting the timeline of the modularity will be > first thing on the agenda in this weeks EPEL Steering Committee meeting. > If we are going to extend the cut off date, we need to decide that fast. > If we are not, I need to get the word out broader than I have. > > I personally think we should extend it to sometime in February. Maybe > February 15th. Middle of a month on a wednesday. > > I agree. On a lot of reflection and some 'what the hell were you thinking?', that is the earliest I can see this not breaking our enterprise customers. -- Stephen Smoogen, Red Hat Automotive Let us be kind to one another, for most of us are fighting a hard battle. -- Ian MacClaren
_______________________________________________ epel-devel mailing list -- epel-devel@lists.fedoraproject.org To unsubscribe send an email to epel-devel-le...@lists.fedoraproject.org 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@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
