[EPEL-devel] Re: EPEL 10.0 mass branching

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

 



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 ? 


> 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 ? 


-- 
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




[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