On 6 August 2013 10:30, Sam Kottler <skott...@redhat.com> wrote: > Hi, > > We've had this conversation at least once before, but I figured I would bring > it up again [1]. > > You can see in Mike's original post that there a number of reasons we should > bump to the 2.7 series in EPEL, but primarily it's because critical bug fixes > aren't ending up in the 2.6 series any longer. I don't want to completely > rehash the conversation in the old thread, but I think that it's important > for EPEL to be providing updates on a maintained branch so I'd like to > propose that both EPEL 5 & EPEL 6 packages get bumped to 2.7. This plan will > largely avoid the issues that come with the potentially tricky upgrade path > for users between 2.x and 3.x. > > Thoughts?
I think both to 2.7.x sounds workable with the usual trumpets and fanfare to let people know that clients and/or servers going to 2.7 might have problems if not done syncronously... > -Sam > > 1. https://www.redhat.com/archives/epel-devel-list/2012-October/msg00043.html > _______________________________________________ > epel-devel mailing list > epel-de...@lists.fedoraproject.org > https://admin.fedoraproject.org/mailman/listinfo/epel-devel -- Stephen J Smoogen. _______________________________________________ epel-devel mailing list epel-de...@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/epel-devel
