[cosmo-dev] Release terminology

[Mikeal Rogers]

On Dec 11, 2007, at December 11, 200711:13 AM, Randy Letness wrote:

> Aparna Kadakia wrote:
>> We don't want to complicate the testing process by adding another  
>> level of testing checkpoints. QA relies on constantly building from  
>> sources so verifying bugs will only be faster than waiting for the  
>> next RC.  When QA is done with what we call "certification" (refer  
>> to Mikeal's original email) , a final RC will be cut, sanity tested  
>> by QA and ready for release.
>>
>
> Ok I was confused.  I was under the impression that testing was done  
> on RC builds only.  If testing is done from code built from the most  
> recent source, then yes there is no need for checkpoint builds.  I  
> think my point was when "Triple Zero" is hit, there is still a high  
> probability of bugs being found due to new features so its kind of  
> pointless to cut an RC before these features are tested.

The reason i think we should cut an RC build is to flush out build  
related issues and give other people in the community something to  
sink their teeth in to. We won't be using it in QA to do all of our  
testing because we have the lab.osaf.us build system which builds in a  
lot of extra production related options that we need to test and can  
be rebuilt easily whenever a fix drops in to the branch that we need.

I guess the name of that build "Release Candidate" is misleading since  
it isn't actually a viable candidate for release, but I'm out of new  
names for things :)

>
>
> -Randy
> _______________________________________________
> cosmo-dev mailing list
> cosmo-dev at lists.osafoundation.org
> http://lists.osafoundation.org/mailman/listinfo/cosmo-dev