>> It might be better to add a flag for this istead of using the priority >> field.
>I think it's an appropriate use of the priority field; the priority >field is supposed to say how important the bug is, which is another way >of saying how excited we should be about fixing it in an upcoming release. But fields are not a good way to request something should be blocking a release. Right now we have to CC you and then wait for you to reply and there is no way to keep track of this manually. With a flag of 4.1blocker, we have + (it is a blocker), - (it is not a blocker), ? (request for this bug to be a blocker), and not set. You can set up flags so only one person is able to set it and only a group of people can request it. These seems like a better way than figuring out what the priotity means. -- Pinski
