On Mon, Mar 3, 2025 at 1:36 PM Sérgio Basto via epel-devel <epel-devel@xxxxxxxxxxxxxxxxxxxxxxx> wrote: > > On Mon, 2025-03-03 at 15:05 +0100, Fabio Valentini wrote: > > 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) > > RHEL 10.0 which is RHEL 10 Beta ? Not exactly. RHEL 10 Beta essentially functions like a minor version before RHEL 10.0. Nothing in EPEL has been built against it, so you'll probably run into edge cases of missing dependencies and other oddities. If you want to test EPEL 10.0 updates, your best bet at this point to use CentOS Stream 10 and override releasever to 10.0. This isn't perfectly correct either, but it is quite a bit closer to RHEL 10.0 than RHEL 10 Beta is at this point in time. Also remember that it is ok to just build for EPEL 10.1, unless you're specifically fixing a bug in an EPEL 10.0 package. You don't have to build for both if you don't need to. You can treat EPEL 10.0 similar to how you would treat a Fedora branch after the updates-testing activation. It's ok to defer non-essential updates to 10.1. This is similar to doing an update in Fedora right now. If you're making a non-essential change, it probably shouldn't be done in F42, and instead only be done in rawhide so that it is deferred to F43. The EPEL Steering Committee has been discussing modifying the EPEL updates policy to capture this nuance, modeled after the Fedora updates policy. > > > > 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). > > > I like the schema , seems to me that is more correct , any plan use the > same for EL 9 ? I'm happy to hear you like it. It was designed to work more similar to Fedora. However, I'm afraid it would be far too disruptive to port EPEL 9 to the same structure midway through its lifecycle. I'm happy to discuss it further if people have specific ideas about how such a transition would work, but for now I consider this new scheme to be EPEL 10+ only. > > > -- > Sérgio M. B. > -- > _______________________________________________ > 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 -- 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
