From: "Dennis Clarke" <dclarke@blastwave.org>
To: "David Daney" <ddaney@avtrex.com>
Cc: "Mark Mitchell" <mark@codesourcery.com>,
"Andrew MacLeod" <amacleod@redhat.com>,
"Richard Guenther" <richard.guenther@gmail.com>,
"GCC" <gcc@gcc.gnu.org>
Subject: Re: GCC 4.3 release schedule
Date: Fri, 26 Oct 2007 16:45:00 -0000 [thread overview]
Message-ID: <1524.72.39.216.186.1193416503.squirrel@mail.blastwave.org> (raw)
In-Reply-To: <472213F6.1040000@avtrex.com>
> Mark Mitchell wrote:
>> As I said in
>> my status report, our practice has been to cut the release branch when
>> we reach 100 regressions, and release 2-4 months after that point,
>> depending on quality on the branch. To be honest, I'd rather wait
>> longer to make the branch -- but there tends to be intense pressure in
>> the developer community to make a branch so we can get on to the next
>> round of major features.
>
Is "correctness" a feature ?
I would like to see a nice clean GCC 4.2.x before GCC 4.3.zero even gets
thought of. Why would one simply branch towards the next release when
the previous one still needs some work? To appease sales people and
developers making noises for features?
> I don't want to start a flame-fest, but perhaps we could reconsider the
> release-branching criteria.
I will read intently.
Dennis Clarke
next prev parent reply other threads:[~2007-10-26 16:38 UTC|newest]
Thread overview: 53+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-26 13:21 Andrew MacLeod
2007-10-26 14:05 ` Richard Guenther
2007-10-26 14:40 ` Andrew MacLeod
2007-10-26 15:54 ` Richard Guenther
2007-10-26 16:04 ` Dennis Clarke
2007-10-26 16:11 ` Richard Guenther
2007-10-26 16:32 ` Dennis Clarke
2007-10-26 18:06 ` Eric Botcazou
2007-10-26 18:14 ` Dennis Clarke
2007-10-26 18:20 ` Eric Botcazou
2007-10-26 18:41 ` Dennis Clarke
2007-10-26 21:02 ` Janis Johnson
2007-10-26 21:10 ` Eric Botcazou
2007-10-26 18:28 ` Martin Michlmayr
2007-10-26 19:03 ` Joe Buck
2007-10-26 20:49 ` Martin Michlmayr
2007-10-26 22:06 ` Joe Buck
2007-10-27 7:45 ` Martin Michlmayr
2007-10-31 19:10 ` Matthias Klose
2007-10-26 16:08 ` Mark Mitchell
2007-10-26 16:21 ` Richard Guenther
2007-10-26 16:21 ` David Daney
2007-10-26 16:45 ` Dennis Clarke [this message]
2007-10-28 16:34 ` Jason Merrill
2007-10-26 21:07 ` Andrew MacLeod
2007-11-01 16:50 ` Andrew Pinski
2007-11-01 17:38 ` Andrew MacLeod
2007-11-01 17:55 ` Jack Lloyd
2007-11-01 18:00 ` Daniel Jacobowitz
2007-11-01 18:27 ` Richard Guenther
2007-11-01 20:55 ` Gerald Pfeifer
2007-11-01 18:37 ` Andrew MacLeod
2007-10-29 15:24 Benjamin Kosnik
2007-10-29 15:54 ` Andrew MacLeod
2007-10-29 16:07 ` Benjamin Kosnik
2007-10-29 16:20 ` Richard Guenther
2007-10-29 18:04 ` Jason Merrill
2007-10-29 18:14 ` Andrew MacLeod
2007-10-29 18:29 ` Richard Guenther
2007-10-29 18:57 ` Andrew MacLeod
2007-10-29 19:37 ` Richard Guenther
2007-10-29 21:20 ` Eric Weddington
2007-10-29 22:18 ` Benjamin Kosnik
2007-10-29 22:43 ` Richard Guenther
2007-10-30 6:34 ` Mark Mitchell
2007-10-30 14:50 ` Jason Merrill
2007-10-30 15:18 ` Mark Mitchell
2007-11-01 15:45 ` Gerald Pfeifer
2007-11-01 16:01 ` Andrew MacLeod
2007-11-01 16:31 ` Benjamin Kosnik
2007-11-01 18:25 ` Richard Guenther
2007-11-01 21:39 ` Diego Novillo
2007-10-29 23:10 J.C. Pizarro
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=1524.72.39.216.186.1193416503.squirrel@mail.blastwave.org \
--to=dclarke@blastwave.org \
--cc=amacleod@redhat.com \
--cc=ddaney@avtrex.com \
--cc=gcc@gcc.gnu.org \
--cc=mark@codesourcery.com \
--cc=richard.guenther@gmail.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).