From: Nathanael Nerode <neroden@twcny.rr.com>
To: giovannibajo@libero.it
Cc: gcc@gcc.gnu.org
Subject: Re: your RESOLVED->CLOSED changes
Date: Fri, 23 May 2003 07:39:00 -0000 [thread overview]
Message-ID: <20030523071817.GA17455@doctormoo> (raw)
>with these messages. May I ask you to discuss such issues on the main
>mailing list before doing it? We (bughunters) are trying to mantain
Sure.
>and unmantainable. Moreover, we have bugzilla rights to do such batch
>changes without spamming gcc-bugs.
I wasn't actually batching them, you know... I caught at least three
mis-resolved bugs in the process. :-/
I'm not sure why there's no way to poke a bug without flooding gcc-bugs
(or indeed everyone else on the CC list). And for that matter, if there
are privileges you have to avoid this that I don't, why that is. :-/ I've
poked large numbers of bugs in one day in the past as a matter of
routine maintenance, sorting, correcting.
>Besides, we were discussing the whole VERIFIED/RESOLVED/CLOSED issue
>off-list (and once we would have found an agreement among ourselves, we
>were going to bring the issue on the list of course). Theoretically,
>nobody
Honestly, better to discuss this one on-list. Probably better to have
discussed it before the switchover, as well, but that's water under the
bridge.
>decided yet if we wanted to mantain a difference between "closed"
>states or
>not, so we might have to revert all these changes eventually (even if
>we seem to agree that those states are useless and we simply want all
>bugs CLOSED). Bugzilla itself might need changes once a policy is
>adopted.
I think the verified/closed distinction is quite useful for noting bugs
which are fixed but not in a released version. (Of course some closed
bugs are present in 3.3 as of now, but that's an acceptable transition
state.)
Given the total lack of QA in GCC at the moment, perhaps 'resolved' is
not a very useful status, but it's certainly true that only some of the
currently 'resolved' bugs are actually resolved (I assume this is the
usual unavoidable conversion glitches).
--Nathanael
next reply other threads:[~2003-05-23 7:18 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-23 7:39 Nathanael Nerode [this message]
2003-05-23 8:55 ` Giovanni Bajo
2003-05-23 9:36 ` Gerald Pfeifer
2003-05-23 10:19 ` Giovanni Bajo
2003-05-23 14:18 ` Wolfgang Bangerth
2003-05-23 15:47 ` Nathanael Nerode
2003-05-23 19:23 ` Wolfgang Bangerth
2003-05-23 19:46 ` DJ Delorie
2003-05-23 19:56 ` Wolfgang Bangerth
2003-05-23 20:03 ` DJ Delorie
2003-05-23 20:14 ` Wolfgang Bangerth
[not found] ` <Pine.LNX.4.44.0305230908020.22023-100000@gandalf.ices.utex as.edu>
2003-05-23 14:19 ` John Anthony Kazos Jr.
2003-05-23 15:41 ` Nathanael Nerode
2003-05-23 15:33 ` Nathanael Nerode
2003-05-23 9:43 ` Joseph S. Myers
[not found] ` <Pine.LNX.4.53.0305231035220.4682@kern.srcf.societies.cam.a c.uk>
2003-05-23 9:53 ` John Anthony Kazos Jr.
2003-05-23 15:05 ` Daniel Berlin
2003-05-23 15:54 ` Nathanael Nerode
-- strict thread matches above, loose matches on Subject: below --
2003-05-23 15:29 Volker Reichelt
2003-05-23 16:18 ` Daniel Berlin
2003-05-23 19:23 ` Wolfgang Bangerth
2003-05-23 19:37 ` DJ Delorie
2003-05-23 14:55 Wolfgang Bangerth
[not found] <20030523062858.322.qmail@sources.redhat.com>
2003-05-23 6:59 ` Giovanni Bajo
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=20030523071817.GA17455@doctormoo \
--to=neroden@twcny.rr.com \
--cc=gcc@gcc.gnu.org \
--cc=giovannibajo@libero.it \
/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).