[CentOS-devel] CentOS-[56] Continous Release

Tue Jun 21 22:33:35 UTC 2011
Karanbir Singh <mail-lists at karan.org>

On 06/21/2011 07:03 PM, Les Mikesell wrote:
> So, if you were managing an internet connected host running CentOS,
> would you configure it to track the CR repo or not?  Or what criteria

I would yes, but thats my personal choice on my personal machines.

> would you use to make this decision?  I'm still having trouble seeing
> why, if upstream decided they should go out, that someone running what
> is essentially identical to that upstream code doesn't need them for the
> same reasons.  Or why to think the risk of installing them outweighs the
> risk of continuing to run what upstream had its reasons to replace.

You basically hit the nail on the head there - the testing that we hope 
to go through before putting the packages into CR is exactly the testing 
that that needs to be done to make sure that things are how they should 
be. Done on a per-rpm level, in smaller groups and closer to build times 
means that we can get them out faster to a public place.

The 'issue' is how we execute the process on the public (~ user) side of 
things, what their process of opting in would be, and how they would get 
back onto the regular os/ and updates/ repo once that point release goes 

- KB