On Tue, Aug 13, 2024 at 4:12 AM Stephen Smoogen <ssmoogen@xxxxxxxxxx> wrote: > > > > On Mon, 12 Aug 2024 at 17:44, Miroslav Suchý <msuchy@xxxxxxxxxx> wrote: >> >> Dne 11. 08. 24 v 12:41 dop. Carl George napsal(a): >> >> - creating epel10 branches (`fedpkg request-branch epel10`) >> >> Can be the branch automatically created for all packages that has epel9 branch? I am not looking forward to request dozens of branches for all my packages. >> >> > > This is something I wanted to do in previous EPEL splits, but it has usually gotten too many complaints from packagers to consider. Many packagers don't want their packages in EPEL at all but will do so if there are requests from someone or that there is going to be a branch packager for EPEL packages. Many EPEL branch packagers really only want to support one release because that is what they are using versus multiple ones. > > That said, I think it is something to revisit like we did for EL7, EL8 and EL9 :). > > -- > 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@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, report it: https://pagure.io/fedora-infrastructure/new_issue Beyond just revisiting it, we need someone to step up to figure out the implementation and policy work. There was some discussion in the EPEL Steering Committee meetings about doing it for EPEL 10 based on ELN Extras workloads in Content Resolver, but that idea lost steam around the time the branch requests became automated with a toddler. Now for packages you're the maintainer of, getting the branch is one additional command that results in the branch being ready within minutes. Is it even worth automating this further? For packages you're not a maintainer of, is it even appropriate for us to automate the process and not rely on maintainer opt-in like we do now? -- 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, report it: https://pagure.io/fedora-infrastructure/new_issue
