On Oct 10, 2012, at 4:33 PM, Tim Flink wrote: > What do you mean by 'triaged order'? I can think of a couple ways that > could be read but I'm not sure which one you were thinking of. Magical Rainbow Pooping & Sorting Unicorn that groups all (e.g. anaconda) bugs together, and also in some kind of sequence perhaps from…. nevermind. Not going to happen. From my limited review experience, most bugs are fairly quickly sized up and slotted as blocking or not. A not insignificant minority cause a lot of head scratching. Instead, for now, let me suggest a change to Proposing blocker bugs section of this: http://fedoraproject.org/wiki/QA:SOP_blocker_bug_process Current: To propose a bug as a blocker for a release, mark it as blocking the tracker bug for blocker bugs in that release. To do this, enter the alias or bug ID of the tracker bug into the Blocks: field in Bugzilla. The aliases for the tracker bugs follow a consistent naming scheme. The Alpha tracker will always be called FXXAlpha, the Beta tracker will always be called FXXBeta, and the final release tracker will always be called FXXBlocker, where XX is the number of the release in question. So, to mark a bug as blocking the release of Fedora 18 Beta, you would set it to block the bug F18Beta. When proposing a bug as a blocker, you should always explicitly state which of the Fedora_Release_Criteria you consider it to be infringing (see example). Revision: Proposing a bug as a blocker for release involves two requirements: mark the bug as blocking the tracker bug for that release, and explicitly state which of the Fedora_Release_Criteria you consider it infringes (see example). These requirements can be met in a single submission step. To do this: 1. Enter the alias or bug ID of the tracker bug into the Blocks: field in Bugzilla. The aliases for the tracker bugs follow a consistent naming scheme. The Alpha tracker will always be called FXXAlpha, the Beta tracker will always be called FXXBeta, and the final release tracker will always be called FXXBlocker, where XX is the number of the release in question. e.g. to mark a bug as blocking the release of Fedora 18 Beta, you would set Blocks: F18Beta. 2. Enter a statement in the Additional Comments: field, that includes the Fedora_Release_Criterion you consider to be infringed by this bug. At the very least, please include of a concise explanation of the operational or user experience consequences of this bug. 3. Click the Save Changes button. The NTH section on proposing probably needs a similar update. Chris Murphy -- test mailing list test@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
