[Cosmo-dev] Cosmo 0.6.1 status and endgame

[Ted Leung]

Hi folks,

We're probably a bit overdue for a status update on Cosmo 0.6.1.     
Up til now, the high-order bit for the Cosmo 0.6.1 release has been  
to fix the various syncing bugs that either kept Chandler syncing  
from working, or lost data during the syncing process.    We seem to  
be making good progress on Chandler syncing during the IRC sessions,  
and according to Randy, the rate of incoming data loss bugs is  
dropping off.    That means that we're in a position to look at other  
potential blocking bugs for Cosmo 0.6.1.

Here is a list of all the current 0.6.1 blockers, and their assignees.

8458       randy at osafoundation.org 403 for authenticated user
8838 	br at osafoundation.org       'Could not load events' on accessing  
my personal calendar...
8916 	randy at osafoundation.org	modify title for event shows up in note  
field in chandler
8917 	mde at osafoundation.org  	change event timezone to America Lima  
event time in lozen...
8919 	mde at osafoundation.org  	cosmo ui doesn't handle durations on  
event modifications

It would really help if people could take a look at these bugs and  
update the bug comments with some estimate of how long it will take  
to get these fixed.

Also, it would be good to hear from QA how much testing remains to be  
done.   I believe that we finally made it through the interop section  
of the Cosmo 0.6.1 test plan <http://svn.osafoundation.org/docs/trunk/ 
testspecs/rel061/ZeroDotSixDotOneTestPlan.html>, but I'm not clear on  
how much testing remains to be done, since the status columns haven't  
been updated.

I'd say that unless we start finding more data loss bugs, we should  
be looking to go into a regular release endgame early next week.    
Are there other factors that I am not accounting for here?

Thanks,

Ted