From: Gabriel Dos Reis <gdr@integrable-solutions.net>
To: "Giovanni Bajo" <giovannibajo@libero.it>
Cc: "Mark Mitchell" <mark@codesourcery.com>, <gcc@gcc.gnu.org>
Subject: Re: GCC 3.5 Status (2004-08-29)
Date: Mon, 30 Aug 2004 03:32:00 -0000 [thread overview]
Message-ID: <m3zn4dwcem.fsf@uniton.integrable-solutions.net> (raw)
In-Reply-To: <023b01c48e35$0f5ef9f0$8f432597@bagio>
"Giovanni Bajo" <giovannibajo@libero.it> writes:
| Mark Mitchell wrote:
|
| > If people want to put GCC 3.5 off until next
| > June, and SC approves, it's OK with me.
|
| I think this should be seriously considered. Given the large number of
| incomplete projects (partly merged like the vectorizer, or being worked on
| offline), and the fact that we are currently maintaing *two* stable release
| branches, I don't think we should *rush* at releasing 3.5. Waiting another 6
| months could be a good compromise. What do others think about this?
I agree with your general sentiment. We rushed to release 3.4.0
because it was thought 3.5.0 would bring the bonus of changes
happening in 3.4.0. As a matter of fact, we now get another set of
new things whose bonuses are promised for the future.
What are our release criteria? Sorry to ask the trivial, but it is
because I'm unclear about what we're after.
-- Gaby
next prev parent reply other threads:[~2004-08-30 3:10 UTC|newest]
Thread overview: 62+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-29 23:49 Mark Mitchell
2004-08-30 0:03 ` Andrew Pinski
2004-08-30 0:33 ` Mark Mitchell
2004-08-30 0:53 ` Daniel Berlin
2004-08-30 0:25 ` Steven Bosscher
2004-08-30 0:48 ` Mark Mitchell
2004-08-30 0:57 ` Steven Bosscher
2004-08-30 1:04 ` Mark Mitchell
2004-08-30 1:12 ` Andrew Pinski
2004-08-30 1:29 ` Mark Mitchell
2004-08-30 10:11 ` Joseph S. Myers
2004-08-30 2:46 ` Giovanni Bajo
2004-08-30 3:09 ` Matt Austern
2004-08-30 13:51 ` Speeding up C++ at -O0 (Was: GCC 3.5 Status (2004-08-29)) Giovanni Bajo
2004-08-30 18:02 ` GCC 3.5 Status (2004-08-29) Joe Buck
2004-08-30 3:32 ` Gabriel Dos Reis [this message]
2004-08-30 4:11 ` Mark Mitchell
2004-08-30 4:17 ` Gabriel Dos Reis
2004-08-30 4:43 ` Mark Mitchell
2004-08-30 5:09 ` Gabriel Dos Reis
2004-08-30 5:27 ` Mark Mitchell
2004-08-30 5:30 ` Gabriel Dos Reis
2004-08-30 6:57 ` Mark Mitchell
2004-08-30 9:24 ` Steven Bosscher
2004-08-30 10:13 ` Giovanni Bajo
2004-08-30 10:26 ` Steven Bosscher
2004-08-30 16:34 ` Jan Hubicka
2004-08-30 11:02 ` Paolo Bonzini
2004-08-30 10:03 ` Steven Bosscher
2004-08-30 15:11 ` Mark Mitchell
2004-08-30 15:21 ` Jan Hubicka
2004-08-30 17:46 ` Jeffrey A Law
2004-08-30 1:09 ` Daniel Berlin
2004-08-30 1:53 ` Mark Mitchell
2004-08-30 7:34 ` Steven Bosscher
2004-08-30 8:15 ` Mark Mitchell
2004-08-30 14:16 ` Daniel Berlin
2004-08-30 15:10 ` Mark Mitchell
2004-08-30 3:03 ` Daniel Berlin
2004-08-30 3:20 ` Mark Mitchell
2004-08-31 17:35 ` Joseph S. Myers
2004-08-30 10:50 ` Dorit Naishlos
2004-08-30 15:12 ` Mark Mitchell
2004-08-30 14:26 ` Jan Hubicka
2004-08-30 15:03 ` Mark Mitchell
2004-08-30 15:05 ` Jan Hubicka
2004-08-30 17:08 ` Diego Novillo
2004-08-31 3:25 ` Devang Patel
2004-08-30 0:59 Richard Kenner
2004-08-30 4:33 Nathanael Nerode
2004-08-30 10:17 Richard Kenner
2004-08-30 14:48 ` Mark Mitchell
2004-08-30 18:08 ` Mike Stump
2004-08-30 10:44 Richard Kenner
2004-08-30 11:27 ` Laurent GUERBY
2004-08-30 13:05 ` Jakub Jelinek
2004-08-30 18:28 ` Laurent GUERBY
2004-08-30 20:04 ` Jakub Jelinek
2004-08-30 20:25 ` Laurent GUERBY
2004-08-31 5:27 ` Eric Botcazou
2004-08-31 9:42 ` Arnaud Charlet
2004-08-30 20:14 ` Florian Weimer
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=m3zn4dwcem.fsf@uniton.integrable-solutions.net \
--to=gdr@integrable-solutions.net \
--cc=gcc@gcc.gnu.org \
--cc=giovannibajo@libero.it \
--cc=mark@codesourcery.com \
/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).