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

Wed Jun 1 19:49:38 UTC 2011
Ned Slider <ned at unixmail.co.uk>

On 01/06/11 06:16, Les Mikesell wrote:
> On 5/31/11 6:38 PM, Karanbir Singh wrote:
>> On 06/01/2011 12:33 AM, Les Mikesell wrote:
>>> can go wrong.  My opinion is that it would be best to expose the initial
>>> release as 'test' quality and let a large number of people try it in a
>>> large number of environments - knowing that they should treat it as a test.
>> In which case, how would one estimate 'enough' people have used it and
>> 'enough' people have said ok ? Or, in other words 'enough' people have
>> not reported anything breaking for them.
> Off the top of my head I'd say a few dozen people explicitly reporting a
> tested-good status or a few thousand downloads and a few days with no negative
> reports.


 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.

Unless I misunderstand, KB is talking about releasing packages to CR as 
soon as they are ready (meaning as soon as they have passed all internal 
tests + QA) rather than delaying their release whilst the ISOs are 
subsequently built and everything is synced up to the mirrors. The 
packages released to CR would be the exact same set used to build the 
ISOs and eventually released to the mirrors, just you'd get access to 
them maybe a week earlier.

If more testing is needed then we need to add that to the existing QA 
phase, either by adding the required tests and/or by recruiting more 
testers. Anyone can contribute to that process by writing automated test