From: Nathanael Nerode <neroden@doctormoo.dyndns.org>
To: gcc@gcc.gnu.org
Subject: Re: Bug tracking / Release Quality Assurance
Date: Thu, 10 Oct 2002 08:01:00 -0000 [thread overview]
Message-ID: <20021010040000.GA7859@doctormoo.dyndns.org> (raw)
Mark Mitchell quoth:
>If you are laboring along on a branch, please take the time to work on
>fixing a few bugs. If we all fix three or four, we'll be done in
>no time. Your branch isn't going to be released until we are done with
>this release, so your work is going to see the light of day much sooner
>if you pitch in now.
Looking at the high priority bugs, I figure:
26 c++ bugs (including *all* the rejects-legal bugs)
A number of the bugs in other categories are actually C++ specific as
well. A number of the bugs in other categories have already been fixed.
A number of the bugs in other categories seem to be obsolete
or unreproducible.
Most of the remaining non-C++ bugs are target-specific (with a number
that are host-specific). Then there are the open-ended bugs (such as
'undocumented options' and 'make sure all ada patches to branch get into
mainline').
Unfortunately, this looks like the kind of situation where most of the
bugs are actually quite hard to take on without intricate knowledge of
specific files. More people working on these bugs will probably not get
them fixed any faster, unless they happen to be the people who are expert
in the correct areas (like the C++ front end).
More people working on bug-fixing is wonderful, of course; I'm just
warning that it may have a significant delay before having any positive
effects, due to people investigating areas of code they're not used to.
--Nathanael
next reply other threads:[~2002-10-10 4:04 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-10 8:01 Nathanael Nerode [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-12-09 10:14 Volker Reichelt
2002-12-09 10:42 ` Mark Mitchell
2002-10-08 7:31 Roger Sayle
2002-10-08 8:53 ` Neil Booth
2002-10-08 8:59 ` Roger Sayle
2002-10-07 9:38 Gerald Pfeifer
2002-10-07 9:42 ` David S. Miller
2002-10-07 10:26 ` Jakub Jelinek
2002-10-07 9:50 ` Nathan Sidwell
2002-10-08 12:38 ` Mark Mitchell
2002-10-08 16:07 ` Pop Sébastian
2002-12-07 6:53 ` Gerald Pfeifer
2002-12-08 19:16 ` Mark Mitchell
2002-10-08 0:43 ` Gabriel Dos Reis
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=20021010040000.GA7859@doctormoo.dyndns.org \
--to=neroden@doctormoo.dyndns.org \
--cc=gcc@gcc.gnu.org \
/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).