Hi,
We had a Bug Council and an Engineering Meeting today where we focused
on Alpha4. The skinny is as following:
- we identified 13 blockers
- the global consensus is that we need 1 more week to fix those cleanly
- we are concerned by the lack of stability of Chandler right now and
thought we should identify when this find rate really drops before
declaring alpha4. We propose that a 2 days period without any blockers
being identified and logged is a minimum requirement, especially since
we want alpha4 to be seriously dogfoodable.
With all that, we propose to:
- move alpha4 by 1 week to Tuesday October 24th
- we'll slip the date again if we don't have a 2 days "quiet period" by then
The Bug Council will track the "quietness" daily during its 11am daily
meeting (i.e., we'll need to see 2 days where we don't take any blockers
in before we can declare alpha4 release worthy... of course, we'll use
sound judgement and not count as a blocker the stray one liner fix that
"we take because we can" otherwise, we may likely never finish...).
Detailed notes of the meeting can be found here:
http://wiki.osafoundation.org/bin/view/Journal/EngineeringMeetingNotes20061012
Cheers,
- Philippe
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Open Source Applications Foundation "chandler-dev" mailing list
http://lists.osafoundation.org/mailman/listinfo/chandler-dev
