updates in builders?

Thorsten Leemhuis fedora at leemhuis.info
Tue Dec 11 08:15:09 UTC 2007

On 11.12.2007 01:33, Michael Stahnke wrote:
> On Dec 10, 2007 2:19 PM, Jesse Keating <jkeating at redhat.com> wrote:
>> On Mon, 10 Dec 2007 13:11:53 -0700
>> Kevin Fenzi <kevin at tummy.com> wrote:
>>> Personally, my vote is to always add the updates in.

+1 -- that actually was the plan, but it got forgotten afaics as we iirc
had no way to get the updates easily when we started EPEL. Does reposync
provide a solution these days for RHEL5?

>>> It's easier to tell people that they must have an updated system in
>>> order to use EPEL packages.
>>> Any other thoughts?
>> I agree with Kevin.  The latest updates should be made available in the
>> buildroot.  The /only/ time where this might not be done is at a point
>> release date, where a /lot/ of updates will be released.  Depending on
>> how EPEL works with CentOS, there might be a delay at this point.
> That's probably reasonable and sane.


> It would be nice if we could put
> together some sort of schedule like when our builders get updates
> after a RHEL (or I guess CentOS actually) update.  Is it 2 weeks?  Is
> it whenever we get to it?

Soon after the CentOS updates ships?


More information about the epel-devel-list mailing list