From: Gabriel Dos Reis <gdr@integrable-solutions.net>
To: Wolfgang Bangerth <bangerth@ices.utexas.edu>
Cc: Joe Buck <Joe.Buck@synopsys.COM>, gcc@gcc.gnu.org
Subject: Re: GCC-3.3.4 release status report
Date: Tue, 30 Mar 2004 18:56:00 -0000 [thread overview]
Message-ID: <m31xnay2c9.fsf@uniton.integrable-solutions.net> (raw)
In-Reply-To: <200403291410.59630.bangerth@ices.utexas.edu>
Wolfgang Bangerth <bangerth@ices.utexas.edu> writes:
| >On Sat, Mar 27, 2004 at 11:09:52AM +0100, Gabriel Dos Reis wrote:
| >> The number of open PRs targetted for 3.3.4 has grown up to 46
| >> (from 41 last report).
| >
| > That is a *huge* number of bugs to attempt to fix in the fourth point
| > release; an attempt to fix even half that number will probably result in
| > 3.3.4 being less stable than 3.3.3.
|
| Indeed. My feeling is that way too many patches are going into 3.3.4 without
| any analysis as to the risk of them.
I believe that is too much a strong statement. No patch is blindly
applied to GCC-3.3.4
If your point is that any single patch has a potential risk for
unconvering other bugs, yes that is true and I'm well aware of that.
By the very nature of GCC, it is not always easy to tell *all* the
implications that any arbitrary patch will have, as side-effects.
The easiest and not very useful, IMO, position would be to close
the branch. After all, that is what had been decided.
But, I think there are room for improvements; I accept patches based
on their contents, descriptions of the problems they address and
impacts, and inputs from various maintainers.
I could come tomorrow with a release note saying that only two PRs are
targetted for 3.3.4; I doubt that would make GCC-3.3.4 better than it
looks now. I could also come and say I have 100 open PRs for
GCC-3.3.4; I doubt it would make GCC-3.3.4 worse than it is now.
-- Gaby
next prev parent reply other threads:[~2004-03-30 13:10 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-30 0:20 Wolfgang Bangerth
2004-03-30 18:56 ` Gabriel Dos Reis [this message]
2004-03-30 19:19 ` Theodore Papadopoulo
2004-03-30 23:59 ` Joe Buck
2004-03-31 2:50 ` Eric Botcazou
2004-03-31 3:10 ` Daniel Berlin
2004-03-31 11:24 ` Eric Botcazou
2004-03-31 12:42 ` Gabriel Dos Reis
-- strict thread matches above, loose matches on Subject: below --
2004-03-27 21:26 Gabriel Dos Reis
2004-03-29 19:17 ` Joe Buck
2004-03-30 0:24 ` Richard Guenther
2004-03-30 18:46 ` Gabriel Dos Reis
2004-03-31 1:15 ` Joe Buck
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=m31xnay2c9.fsf@uniton.integrable-solutions.net \
--to=gdr@integrable-solutions.net \
--cc=Joe.Buck@synopsys.COM \
--cc=bangerth@ices.utexas.edu \
--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).