[Cosmo-dev] Cosmo planning status

[Priscilla Chung]

Yes. I agree doing a checkpoint when the merge/hibernate work is  
complete is a good idea. So just to clarify before I update the wiki  
again:

Cosmo 0.5 alpha 1
+ scooby/cosmo merge
+ hibernate work

Here is the status I have for 0.5 alpha1 so far for :
The drop to QA should be sometime today (9/26/06)?
QA should be able to finish testing by early next week (10/2/06)?

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)

Cosmo 0.5
+ Some features based on the Casual Collaborator target user (some  
features such as unified url will be moved to 0.6)
+ Some features for the Admin target user
+ Regression testing
+ Additional tests
+ Refactoring
+ Documentation

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?)

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


On Sep 25, 2006, at 6:05 PM, Mikeal Rogers wrote:

> We're still cutting a release after the merge/hibernate work is  
> complete and all the functional tests are passing (just finished)  
> right?

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