Hi,
Sheila presented the Preview Countdown
(http://wiki.osafoundation.org/Projects/ChandlerMilestoneSchedule) which
includes a new updated schedule and detailed milestones. We discussed
yesterday during the Chandler Engineering meeting what those milestones
are so that we're all on the same page (see
http://wiki.osafoundation.org/Journal/EngineeringMeetingNotes20070208).
It is important to remind ourselves that this release will be different:
it's a user usable release and the quality bar is high, we need to get
to a release that is usable, stable and demonstrate the long term
potential of the project. I think we have all the features in Chandler
and Cosmo right now to deliver just that so we need to pace ourselves so
that we can deliver something in a reasonable time frame.
I'm summarizing here under those milestones, definitions, exit criteria
and what happens between them:
* Feature Freeze: 3/6: All "task" fixed or moved to Future (cut
from the release), code committed and ready to be tested by QA.
*Exit Criteria: if there are "task" open in Bugzilla and that
those "task" can't be pushed out of Preview, the milestone is not
reached and the schedule needs to be adjusted
* Inter milestone period: After Feature Freeze, there's no new
feature work unless it is approved by the bug council. Such feature work
must be motivated by being required for Preview to be usable.
Performance work including potentially architecture change will happen
during that period.
* Code Complete: 3/28: All code in, architecture and feature tweak
completed, perf work completed.
* Exit Criteria: if the perf targets are not met or some
feature rework is still needed, the milestone needs to be pushed
* Inter milestone period: After Code Complete, only bug fix work
and stabilization can be done. Bugs must be approved by Bug Council.
Code changes need peer review before commit.
* Code Freeze: 4/19: All bugs fixed.
* Exit Criteria: if there's more than 10 blocking bugs
outstanding, the milestone is not reached.
* After Code Freeze, only "recall class bugs" and blockers can be
fixed. Bugs are triaged daily, as in previous period, code changes need
to be peer reviewed before commit.
Let me know (on this list preferably) if there's something that's
unclear or problematic.
Cheers,
- Philippe
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Open Source Applications Foundation "chandler-dev" mailing list
http://lists.osafoundation.org/mailman/listinfo/chandler-dev
