Re: EPEL9 Rollout Proposals

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Fri, Nov 19, 2021 at 5:26 PM Miroslav Suchý <msuchy@xxxxxxxxxx> wrote:
>
> Dne 20. 11. 21 v 0:04 Troy Dawson napsal(a):
> > Do we keep everything in epel9-next until RHEL9 GA and then do a mass branch over and mass rebuild? (Plan A)
>
> And again with 9.1 GA? And again with 9.2 GA? // I do not expect answer, just pointing that minor releases should be
> part of the solution.
>
> Miroslav
> _______________________________________________
> 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
> Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure

Historically most EPEL packages don't need to be rebuilt with every
minor release, as RHEL libraries don't change often.  When they do
need to be rebuilt, it's been left up to the individual maintainers to
take care of as their time allows.  This has mostly worked OK for us.

Plan A would be a departure from the norm, where we do a mass rebuild
at 9.0 for a "bootstrap" of epel9 content from epel9-next.  At the
last EPEL Steering Committee meeting we talked about doing mass
rebuilds at every future minor release, but more or less agreed that
this would be overkill and would result in a drastic increase in disk
usage in the infrastructure.  Additionally our existing mass rebuild
tooling doesn't account for changes that exist in the epel9-next
branches that need to be merged to the epel9 branches before building.

Plans B and C are more like the status quo, where packagers target
epel9, and do individual package rebuilds as needed after a RHEL minor
release.

-- 
Carl George
_______________________________________________
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
Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure




[Index of Archives]     [Fedora Announce]     [Fedora News]     [Fedora Cloud]     [Fedora Advisory Board]     [Fedora Education]     [Fedora Security]     [Fedora Scitech]     [Fedora Robotics]     [Fedora Maintainers]     [Fedora Infrastructure]     [Fedora Websites]     [Anaconda Devel]     [Fedora Devel Java]     [Fedora Legacy]     [Fedora Desktop]     [Fedora Fonts]     [ATA RAID]     [Fedora Marketing]     [Fedora Management Tools]     [Fedora Mentors]     [Fedora Package Announce]     [SSH]     [Fedora Package Review]     [Fedora R Devel]     [Fedora PHP Devel]     [Kickstart]     [Fedora Music]     [Fedora Packaging]     [Centos]     [Fedora SELinux]     [Fedora Legal]     [Fedora Kernel]     [Fedora QA]     [Fedora Triage]     [Fedora OCaml]     [Coolkey]     [Virtualization Tools]     [ET Management Tools]     [Yum Users]     [Tux]     [Yosemite News]     [Linux Apps]     [Gnome Users]     [KDE Users]     [Fedora Tools]     [Fedora Art]     [Fedora Docs]     [Maemo Users]     [Asterisk PBX]     [Fedora Sparc]     [Fedora Universal Network Connector]     [Fedora ARM]

  Powered by Linux