From: Theodore Papadopoulo <Theodore.Papadopoulo@sophia.inria.fr>
To: Gabriel Dos Reis <gdr@integrable-solutions.net>
Cc: Wolfgang Bangerth <bangerth@ices.utexas.edu>,
Joe Buck <Joe.Buck@synopsys.COM>,
gcc@gcc.gnu.org
Subject: Re: GCC-3.3.4 release status report
Date: Tue, 30 Mar 2004 19:19:00 -0000 [thread overview]
Message-ID: <200403301337.i2UDbXY8001117@mururoa.inria.fr> (raw)
In-Reply-To: <m31xnay2c9.fsf@uniton.integrable-solutions.net>
bangerth@ices.utexas.edu said:
> 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.
I, actually, believe that the reverse is true. Despite all the effort
that have been made to make 3.4 as robust and good as possible, this
release contains several improvements that have not been exposed to
the wild yet. The better (more strict) C++ parser is certainly
something that will make people encounter problems with 3.4.0, and I
bet several regression will still be found after 3.4.0 is out (a lot
of people out there also believe that the .0 releases are not for the
mainstream).
Thus, in my opinion, a good 3.3.x is needed at least till 3.4 has got
some much broader testing. Thus, the need to correct as much bug as
possible on 3.3 (while keeping it as stable as possible). And I have
no reasons to complain about the stability of 3.3 so far.
Theo.
--------------------------------------------------------------------
Theodore Papadopoulo
Email: Theodore.Papadopoulo@sophia.inria.fr Tel: (33) 04 92 38 76 01
--------------------------------------------------------------------
next prev parent reply other threads:[~2004-03-30 13:38 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
2004-03-30 19:19 ` Theodore Papadopoulo [this message]
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=200403301337.i2UDbXY8001117@mururoa.inria.fr \
--to=theodore.papadopoulo@sophia.inria.fr \
--cc=Joe.Buck@synopsys.COM \
--cc=bangerth@ices.utexas.edu \
--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).