From: Gabriel Dos Reis <gdr@integrable-solutions.net>
To: Gerald Pfeifer <pfeifer@dbai.tuwien.ac.at>
Cc: gcc@gcc.gnu.org
Subject: Re: Bug tracking / Release Quality Assurance
Date: Tue, 08 Oct 2002 00:43:00 -0000 [thread overview]
Message-ID: <m3wuot4pbk.fsf@soliton.integrable-solutions.net> (raw)
In-Reply-To: Gerald Pfeifer's message of "Mon, 7 Oct 2002 18:03:28 +0200 (CEST)"
Gerald Pfeifer <pfeifer@dbai.tuwien.ac.at> writes:
| Checking the GNATS database which currently shows 62 high priority
| problems, there are some points I'd like to raise:
|
| 1. I believe we should not ship GCC 3.2.1 (or branch 3.3.) until this
| bug count has been significantly reduce.
Agreed.
Seems like, somewhere at some point, our development model failed to
cope with only-bug-or-regression fixes and improving (in the broad
sense) the development branch: Balance interests in fixing bugs and
adding new functionality. Clearly closing all branches won't
automatically make people fixing bugs, but somehow we need to improve
on the current situation.
Maybe more maintainers for some parts of the compilers?
[...]
| 3. We probably need some (further) volunteers who monitor GNATS more
| closely, ask submitters for further information/feedback and ping
| maintainers concerning problems in their areas.
Some maintainers have many things to sort out similtaneously so they
get quickly very busy...
-- Gaby
next prev parent reply other threads:[~2002-10-08 2:50 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
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-12-09 10:06 ` PATCH for " Gerald Pfeifer
2002-10-08 0:43 ` Gabriel Dos Reis [this message]
2002-10-08 7:31 Roger Sayle
2002-10-08 8:53 ` Neil Booth
2002-10-08 8:59 ` Roger Sayle
2002-10-10 8:01 Nathanael Nerode
2002-12-09 10:14 Volker Reichelt
2002-12-09 10:42 ` Mark Mitchell
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=m3wuot4pbk.fsf@soliton.integrable-solutions.net \
--to=gdr@integrable-solutions.net \
--cc=gcc@gcc.gnu.org \
--cc=pfeifer@dbai.tuwien.ac.at \
/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).