On Sun, 3 Jul 2011 23:11:16 +0200 Björn Persson <bjorn(a)xn--rombobjrn-67a.se&gt; wrote: > Hello! > > I'm considering making EPEL 6 branches of my Fedora packages. I've > found answers to most of my questions in the wiki, but one question > remains: > > When a new version of RHEL is released, where is the corresponding > new EPEL branched from? From the previous EPEL, from Rawhide or from > some Fedora release? epel4 -> master

epel5 -> master

epel6 -> f12

(The logic being that rhel6 was somewhat based on f12, and the other ones are so old we no longer have active branches for the releases that they were based on). You can of course import whatever you like after the branch is made. kevin

Dennis Gilmore wrote: > On Sunday, July 03, 2011 04:20:14 PM Kevin Fenzi wrote: > > epel4 -> master > > epel-4 comes from FC-3 if it exists if not rawhide > > > epel5 -> master > > epel-5 comes from FC-6 if it exists if not rawhide > > > epel6 -> f12 > > epel-6 comes from F-12 if it exists if not rawhide May i ask what exactly you mean with "if it exists"? Fedpkg lists a remote "origin/f12" branch for all of my packages, so in that sense they exist in F-12, but the el6 branches I got when my package change requests were processed all started out with the same content as the master branch. In this case I would have synchronized them with Rawhide anyway, and then adapted them as necessary from there, so I'm not complaining, but I notice a discrepancy between what I saw and what you're saying. When the time comes for EPEL 7 I will probably prefer that the packages are branched from the most closely matching Fedora release (as Kevin says they will probably be).

Replying again... I might have misread your query. If you mean a completely new branch (like a RHEL7) we would probibly branch from whatever Fedora release most closely matches that, but maintainers could of course override that and build whatever they wish in those branches.