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

[Karanbir Singh]

Hi,

On 06/01/2011 09:18 PM, Les Mikesell wrote:
>>    From where I'm standing, what you describe is pretty much exactly what
>> we currently have in place with the current QA system. The whole point
>> of a CR repository is to get the updates out quickly rather than wait
>> for ISO to be built and pushed to the mirror network. If you add an
>> additional layer of testing that's not going to happen.
>
> Not quite.  You need to balance the risk of not making the updates
> available as the default 'yum update' action (the bazillion internet
> connected Centos boxes aren't all going to enable some new funky

The CR rpms will only be available by making a manual choice on the 
machines, so people need to opt-in rather than opt-out. So mass rollout 
should not happen.

> repository just to get an update quicker) against the risk of pushing a
> broken build.  My opinion leans toward pushing security fixes as fast as

The important point to keep in mind  is that packages from the 
buildsystem will only be released when they have been through the 
regular package level as well as update from 
centos-<release-being-worked-on>-1. The aim is to reduce the need to 
ever reissue a package that has already been through that process.

The time that gets cut out is from not needing to wait for the distro 
stuff ( isos, mirrors, qa of the distro etc ) - which is a bulk of the 
time between upstream release and our release being available.

- KB