From: Wolfgang Bangerth <bangerth@ices.utexas.edu>
To: Joe Buck <Joe.Buck@synopsys.COM>,
Gabriel Dos Reis <gdr@integrable-solutions.net>
Cc: gcc@gcc.gnu.org
Subject: Re: GCC-3.3.4 release status report
Date: Tue, 30 Mar 2004 00:20:00 -0000 [thread overview]
Message-ID: <200403291410.59630.bangerth@ices.utexas.edu> (raw)
>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. We already have some regressions with
respect to previous 3.3.x releases due to this. See for example PR 14640.
I personally think that it is not a huge problem if we don't fix every single
PR in 3.3.4 given that 3.4.0 is close. In fact, I find it a nuisance to have
to look at all the PRs targeted for 3.3.x if I want to find out what needs to
be done for 3.4. We should be more willing to retire PRs if they are already
fixed in 3.4.
W.
-------------------------------------------------------------------------
Wolfgang Bangerth email: bangerth@ices.utexas.edu
www: http://www.ices.utexas.edu/~bangerth/
next reply other threads:[~2004-03-29 20:11 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-30 0:20 Wolfgang Bangerth [this message]
2004-03-30 18:56 ` Gabriel Dos Reis
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=200403291410.59630.bangerth@ices.utexas.edu \
--to=bangerth@ices.utexas.edu \
--cc=Joe.Buck@synopsys.COM \
--cc=gcc@gcc.gnu.org \
--cc=gdr@integrable-solutions.net \
/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).