Hi,
We've been reviewing the Preview schedule in the last week. While it was
clear that we needed to slip the FC milestone so that all required
features could make it, we wanted to review the entire schedule so that
the various parts (desktop, server and web UI) could readjust their own
schedule and feature set.
We now agreed on such a schedule. Not only did we changed some dates and
durations but we also added details to what happens during the various
inter milestones periods as well as added one milestone.
So, for Chandler desktop, here are the main changes:
- added 3 weeks to the FC (3/26)
- added a 3 weeks "Performance tuning" period dedicated to performance
improvement
- increased the debug period to 8 full weeks
- added precision to the milestones exit criteria so that we can qualify
if a milestone is reached or not (see
http://wiki.osafoundation.org/Projects/MilestonesDefinitionAndExitCriteria)
Putting things in few lines, here's how the schedule looks like right
now (more details
http://wiki.osafoundation.org/Projects/ChandlerMilestoneSchedule):
- Feature Freeze: 03/26 : all "tasks" in ready to be tested
-> 3 weeks of perf work
- Performance Milestone (new): 04/16 : perf work done for most devs
(some might still work on this during the debug period depending on what
we discover during the 3 weeks perf tuning period)
-> 8 weeks of bug fixing
- Code Complete: 06/11
-> 2 weeks of critical bugs and blockers test/fix
- Release Candidate: 06/25
-> 1 week of RC test and pre launch activities
- Launch: 06/29
We feel that this schedule is more realistic and will allow us to reach
the feature and quality bar we want for this Preview. Sheila will be
talking in more details about the entire Preview Countdown schedule and
activities during tomorrow's staff meeting.
Cheers,
- Philippe
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Open Source Applications Foundation "chandler-dev" mailing list
http://lists.osafoundation.org/mailman/listinfo/chandler-dev
