This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: Use of Bugzilla fields
- From: Daniel Berlin <dberlin at dberlin dot org>
- To: Andrew Pinski <pinskia at physics dot uc dot edu>
- Cc: gcc at gcc dot gnu dot org
- Date: Sun, 30 Oct 2005 18:23:06 -0500
- Subject: Re: Use of Bugzilla fields
- References: <200510302248.j9UMmIsf007038@earth.phy.uc.edu>
On Sun, 2005-10-30 at 17:48 -0500, Andrew Pinski wrote:
> >> 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.
Andrew, i see you have gone and created flags anyway, and have started
setting them.
Flags may be a technically better way of representing this, but he is
the Release Manager, and you are not.
You should not be doing this stuff unilaterally, it's not your choice to
be making.
What you are doing is confusing Mark, as he says in
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=15082
Please stop.
Mark can change bugzilla policy, because he is the RM, and trying to
make a release. You can not.
--Dan