- Our goal was to go through *all* of the 0.7 release bugs. We viewed bugs person by person.

- We skipped Dan and Bear (Aparna will meet with Dan and Heikki will meet with Bear to do another pass at those lists).

- We went alphabetically, and got up to rae (Reid). We'll meet again tomorrow @3 and go through the remaining people.

- We started at 152 bugs and went to 116 bugs.

- We moved all bugs related to recorded scripts to 0.7.1. This release now includes both interop work and work on the test framework, as we know these will both be high priorities immediately after we hit Preview. (And won't require design cycles to make decisions).

- We tended to either bump up the priority to P2 or move bugs to Future. We left a few P3s, but these will get moved to Future as soon as we hit Code complete. If you have a P3 and you don't think it will make it, go ahead and move it to Future.

- We moved out 2 Zanshin bugs related to clarifying error messages, so we can go ahead and push Zanshin with its one (important) fix.

- We added a 0.7.1 target for vobject.

Cheers,
Katie

Philippe Bossut wrote:
Hi Bug Council members,

We should have our regular Bug Council tomorrow @ 4pm to review untargetted bugs. Since we are approaching Code Complete (July 16th) we should also scrub the P3 and reduce the count to what's really necessary to fix for Preview.

Considering our experience with previous scrubbing exercise, I propose that we start @ 3pm and extend the exercise till 5pm. I feel it's pretty important we work now to reduce the list of bugs to the "must fix" so that we can focus and get this baby out of the door.

Let me know if that timing works for you guys.

Cheers,
- Philippe
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

Open Source Applications Foundation "chandler-dev" mailing list
http://lists.osafoundation.org/mailman/listinfo/chandler-dev

_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

Open Source Applications Foundation "chandler-dev" mailing list
http://lists.osafoundation.org/mailman/listinfo/chandler-dev

Reply via email to