On Mon, Mar 3, 2025 at 1:53 AM Sérgio Basto via epel-devel <epel-devel@xxxxxxxxxxxxxxxxxxxxxxx> wrote: > > On Tue, 2025-02-18 at 02:13 -0600, Carl George wrote: > > Hello EPEL packagers, > > > > Later today (2025-02-18), Release Engineering will branch epel10.0 > > from epel10, in accordance with our overall branching strategy for > > EPEL 10. > > > > https://docs.fedoraproject.org/en-US/epel/branches/#_epel_10 > > > > During the branching, we will temporarily disable builds to the > > epel10-candidate target, which is used when you run `fedpkg build` > > from the epel10 branch. If you are trying to create a build and > > receive an error about a target not existing, please try again later > > in the day. Because this is the first time we are doing an EPEL mass > > branching, we don't know precisely how long it will take or how long > > we will need to disable the builds for. > > > When we want update epel for both RHEL and Centos (stream) i.e. build > on el9 and not el9-next, for el10 should we build on epel10 or > epel10.0 ? The short answer is "both if you want both" :) Since epel10.0 has already been branched off of epel10, you will need to submit a build from both the epel10 branch and the epel10.0 branch if you still want a change to land in both EPEL 10.0 (for RHEL 10.0) and in EPEL 10 (for CentOS Stream 10). If you only build from the epel10 branch, it will only land in what will become epel10.1 once that is branched off in ~6 months (similar to what happens when you only build in rawhide - it will trickle down to stable branches only at the next branch point). Fabio -- _______________________________________________ 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
