On Thu, 2025-02-20 at 06:15 -0800, Troy Dawson wrote: > On Thu, Feb 20, 2025 at 12:10 AM Remi Collet > <[email protected]> wrote: > > Le 18/02/2025 à 09:13, Carl George via epel-announce a écrit : > > > 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 > > > > Can you please confirm if 10.0 new builds will be available > > in "10" (for CentOS Stream users) ? > > > > Or do I have to build in both branches ? > > > > > Currently there are two branches. > epel10 > epel10.0 > > Everything built in epel10 will have a dist-tag of epel10_1 and will > go into the epel10 repo. This is consumed by CentOS Stream 10. > > Everything build in epel10.0 will have a dist-tag of epel10_0 and > will go into the epel10.0 repo. This will be consumed by RHEL 10.0 > only, not CentOS Stream.
OK , seems to me a better solution than epel-next > So it depends on what you want. > If you care only about CentOS Stream 10, then just epel10 is needed. > If you want it to be in both RHEL 10.0+ and CentOS Stream 10, then > yes, you have to build it in both branches. > > Do not build it in epel10.0 only. The build will not transfer over. > > Troy > p.s. If you are a Fedora package maintainer, picture this being right > after the branching point from rawhide. > -- Sérgio M. B.
-- _______________________________________________ epel-devel mailing list -- [email protected] To unsubscribe send an email to [email protected] 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/[email protected] Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
