This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: Bugzilla and setting priorities
On Fri, Jan 29, 2010 at 1:00 PM, Richard Earnshaw <rearnsha@arm.com> wrote:
>
> On Fri, 2010-01-29 at 12:24 +0100, Richard Guenther wrote:
>> On Fri, Jan 29, 2010 at 12:26 PM, Dave Korn
>> <dave.korn.cygwin@googlemail.com> wrote:
>> > On 29/01/2010 11:03, Richard Guenther wrote:
>> >
>> >> This should ideally be documented in
>> >> http://gcc.gnu.org/bugs/management.html
>> >
>> > ?Both the way that page is named, and the way the link to it is indented
>> > under the link to the BZ frontpage in the side navbar on the gcc.gnu.org front
>> > page, make it look very much like it's intended for BZ admins, rather than
>> > ordinary bug-reporting users. ?Maybe that needs a bit of tweaking too? ?Or
>> > perhaps a prominent link from the "How to report" page?
>>
>> Sure - patches welcome ;)
>>
>> Attached is what I will install barring any negative comments.
>>
>> Richard.
>
>> + ? ?A P1 bug blocks the release.
>
> Do you really mean that, or do you mean a P1 regression? ?Maybe it
> should read:
>
> ? ? ? ?A P1 regression blocks the release; any other P1 bug will hold
> ? ? ? ?up the release until this issue has been fully reviewd.
Priorities do not mean anything for a release if they are not
regressions. Note how everything in the priority section talks
about regressions only. I'll adjust the wording to "A P1 regression
blocks the release.".
Thanks,
Richard.