From: "Joseph S. Myers" <joseph@codesourcery.com>
To: "Frédéric Buclin" <LpSolit@netscape.net>
Cc: "Gerald Pfeifer" <gerald@pfeifer.com>,
"Manuel López-Ibáñez" <lopezibanez@gmail.com>,
"Steve Kargl" <sgk@troutmask.apl.washington.edu>,
"Jakub Jelinek" <jakub@redhat.com>,
gcc@gcc.gnu.org, gcc-patches@gcc.gnu.org
Subject: Re: Confirming a bug in new bugzilla?
Date: Mon, 11 Apr 2011 00:03:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.64.1104102358550.10984@digraph.polyomino.org.uk> (raw)
In-Reply-To: <4DA23482.4000400@netscape.net>
[-- Attachment #1: Type: TEXT/PLAIN, Size: 1150 bytes --]
On Mon, 11 Apr 2011, Frédéric Buclin wrote:
> Le 10. 04. 11 02:19, Joseph S. Myers a écrit :
> > Likewise. We don't use VERIFIED and CLOSED in GCC, proper text should
> > reflect the existence of only one closed state with a genuine meaning and
> > not mention the others (ideally they'd be completely hidden).
>
> That's not true. VERIFIED and CLOSED are valid bug statuses used in the
> GCC Bugzilla. There are 517 bugs with one of these statuses.
They are not *meaningful* statuses. The standard Bugzilla descriptions
are written in terms of a QA setup that simply does not exist for GCC and
there is no GCC-specific policy, written or unwritten, for these statuses.
The standard "ASSIGNED" description is another one that does not fit well
with GCC; the meaning is supposed to be that the assignee is working on a
fix ("the proper person" is not a meaningful concept here), and the normal
return to NEW is not "given to another person" but the assignee admitting
they are no longer working on a fix and removing themselves as assignee
without adding someone else.
--
Joseph S. Myers
joseph@codesourcery.com
prev parent reply other threads:[~2011-04-11 0:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20100925054454.GA81084@troutmask.apl.washington.edu>
[not found] ` <20100925084632.GK2652@sunsite.ms.mff.cuni.cz>
[not found] ` <20100925142844.GB83390@troutmask.apl.washington.edu>
[not found] ` <AANLkTimOy+Vqu9VW0RY+FL6N+8CZw0HTxWCO72Z_qQJc@mail.gmail.com>
2011-04-09 19:51 ` Gerald Pfeifer
2011-04-10 0:19 ` Joseph S. Myers
2011-04-10 22:51 ` Frédéric Buclin
2011-04-10 23:33 ` Jonathan Wakely
2011-04-10 23:42 ` Frédéric Buclin
2011-04-11 0:03 ` Joseph S. Myers [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Pine.LNX.4.64.1104102358550.10984@digraph.polyomino.org.uk \
--to=joseph@codesourcery.com \
--cc=LpSolit@netscape.net \
--cc=gcc-patches@gcc.gnu.org \
--cc=gcc@gcc.gnu.org \
--cc=gerald@pfeifer.com \
--cc=jakub@redhat.com \
--cc=lopezibanez@gmail.com \
--cc=sgk@troutmask.apl.washington.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).