[Cosmo-dev] Cosmo planning status

[Mikeal Rogers]

> Question: Do was need a release candidate of 0.5 alpha1 to be put  
> on osaf.us once it is certified by QA?
> If yes, how long will that take? (Jared: perhaps you can answer  
> this and include your plan on moving dogfood users from cosmo demo  
> to osaf.us)
>

For me to certify the release for production I additionally require  
the code to be branched, any bugs that are found to be fixed on the  
branch, and additional rc's built and tested until we have a build  
that passes all testing.

> Here is the status I have for 0.5 so far for :
> + The drop to QA should be approximately 2 weeks after 0.5 alpha1  
> drop to QA? (Ted: please correct me if I'm wrong here? There is  
> branch for the dev. to keep working on the cosmo ui features?)

If we branch the code, test, bug fix, and re-test the rc's so that we  
can certify the build for production then there will be a hit to  
development and I doubt the 2 week assumption on development time  
will be unaffected.

>
> There seems to be a lot of confusion and discussion around this  
> current release. Please clarify as you see fit.

Here was the plan as I understood it.

QA would get a drop of cosmo, we were calling this RC but a better  
word for how I understood it would be SNAPSHOT. This build would go  
through a full QA cycle and bugs would be logged against it. My  
understanding was that no bugs would be fixed against a 0.5alpha1  
branch and would instead only be fixed in the trunk and another build  
would not be produced until 0.5 rc1.

I can certify that QA ran all of our tests and logged all the  
necessary bugs against a drop of cosmo, but I can't certify anything  
for distrobution, much less production use, unless we are branching  
the code for the alpha and fixing all the necessary bugs, building  
additional rc's if necessary and running regression and acceptance  
testing on each rc until everything passes.

I hope this illustrates the difference in time and resources that  
would be required between a full test cycle on a cosmo build and a  
full certification of cosmo for production use.

-Mikeal
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.osafoundation.org/pipermail/cosmo-dev/attachments/20060926/aa8c7720/attachment.htm