Hi,

During yesterday's Desktop Release Engineering meeting (http://wiki.osafoundation.org/Journal/EngineeringMeetingNotes20070517), we discussed the use of the various "blocking flags" and how they're used by QA, PPD and Devs. It appears that my and others understanding of those flags were in contradiction to what I said during Tuesday's Desktop meeting (http://wiki.osafoundation.org/Journal/AppsMeeting20070515) so it looks like important to make things clear here.

So, this is what we settled on:

- we're tracking 2 "milestones" right now, or rather, 2 different checkpoints: - migration checkpoint: this is the one that we'll be deeming "OK for migration" and will ask all dogfooders to use for migration to the Cosmo 0.6.1 hub.chandlerproject.org server using MorseCode - dogfooder checkpoint: this is the one that we'll ask dogfooders to start using to put Preview to the test (pre Code Complete)

- with that in mind, here's what the various Bugzilla flags/fields mean:
- blocking0.6.1 : this flag raised means that the bug is blocking the migration checkpoint. Those bugs must be dealt with with highest priority (we're trying to get to a checkpoint now and are just 3 bugs away from one...) - blocking0.7: currently, this flag raised means that the bug is blocking the dogfooder checkpoint. Those bugs are also very high priority, only slightly lower than the other one. We've currently 3 bugs flagged that way - severity = blocker: this field is rarely used and should be used only for something that should be fixed immediately 'cause it's breaking build or TBoxes or blocking QA in a major way.

OK, I know that "blocking0.7" is somewhat bending the rule a bit (since we'll use that same flag again later when shipping Preview...) but, since this flag is unused right now, that seems fine. What really matter is that we all agree on how it's currently used...

Sorry for spreading some wrong info Tuesday...

Cheers,
- Philippe

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

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

Reply via email to