[Cosmo-dev] 0.5 status

[Bobby Rullo]

This looks good.
On Sep 11, 2006, at 4:40 PM, Ted Leung wrote:

> Hi all,
>
> I've been talking to people about estimates and dates and so forth,  
> and it's hard to coordinate all that point to point, so we're going  
> to experiment with doing it here.
>
> So for 0.5 we have the following scheduled work and *very* rough  
> estimates  (all bug numbers and descriptions are taken from <http:// 
> wiki.osafoundation.org/bin/view/Projects/CosmoZeroPointFive>)
>
> Brian:
>    Hibernate.  After that he plans to play free safety and help  
> Bobby out
>
> Bobby:
>    Anonymous access: bug 6179 - est 4days
>    Managing recurring calendar events: bug 6180 - est 3-4 days
>    Server part of Client timezone support: bug  6195 est 8 days
>    Default Timezone, (depends on 6195): bug 6199 est 3 days
>
>    Total time (taking high ends of ranges) = 19 days
>
> Matthew
>    Navigation: Jump To Date: bug 6182 - 3 days
>    Navigation: Mail To Link: bug 6183 - 3 days
>    Visual Tweaks: Display of Working Hours: bug 5123 - 1 day
>    Visual Tweaks: Lozenge States: bug 6158, bug 5683 - 2 days - I  
> know Matthew has additional status, because he's mostly done
>    Refactoring: cal_main.js: bug 6228 - 2-11 days depending on how  
> much we do.
>
>    Total time (taking low ends of ranges) = 11 days
>
> Travis
>    Additional trace/debug logging - no estimate, but not on the  
> critical path, and Travis is just coming up to speed on Cosmo
>
> As you can see, the prediction for how many more days 0.5 will take  
> can run to anywhere from 11 to 19 days:
>
> 11 days = Brian can help enough to cut Bobby's workload to the  
> longest path (timezone), 11 days, which is the same length as  
> Matthews work
> 19 days = The worst case where Bobby doesn't get any help from Brian.
>
> If we end up taking more than 11 days, then I'd like to see Matthew  
> get more time to do more refactoring in preparation for future  
> release.   There's also the question of allocating some of Brian's  
> time to validate the new Cosmo against Chandler just in case.
>
> Note that this is the time till we can get a release that we can  
> start testing.  I'm not making any predictions about how long  
> testing and the other non-code deliverables take.  11 working days  
> from today is September 26, 19 days is October 6.
>
> Please let me know if I've gotten any information wrong, if there  
> is important information missing, or if you have ideas on how to  
> get us to a release in a shorter amount of time.
>
> Ted
> _______________________________________________
> cosmo-dev mailing list
> cosmo-dev at lists.osafoundation.org
> http://lists.osafoundation.org/mailman/listinfo/cosmo-dev