[cosmo-dev] Release terminology

[Randy Letness]

Mikeal Rogers wrote:
>
> 2. "Triple Zero" -- 0 open untargetted bugs, 0 open bugs in the 
> release, 0 automated test failures
>    - If the release branch hasn't happened yet, it should happen now.
>    - If QA wasn't automating features tests before this, they are now
>    - At this point bear should do a release build and mark it RC1 so 
> that outside contributors may start testing the build at home. This 
> will also flush out any release build related issues.
>    - QA provides an estimate to when they will be done adding new 
> automated tests to this release. This timeline will obviously reflect 
> how much time QA was spending on these features beforehand.

Whats the difference between "Triple Zero" and RC?  I think a problem we 
were running into was that an RC was cut before any real feature testing 
was done.  New bugs were found, and we would wait a while before cutting 
another RC (a manual process) and verify those bugs as fixed.  This 
could be a lag time of a few days and in some cases would result in the 
bug being punted because to prevent another RC.  What about testing from 
checkpoints, that are built automatically, if possible.  That way when a 
bug is fixed, it can be verified in the next checkpoint. When all bugs 
are fixed and verified, then an RC is cut and final certification 
testing is done.

-Randy