From: Mark Mitchell <mark@codesourcery.com>
To: Gerald Pfeifer <pfeifer@dbai.tuwien.ac.at>
Cc: "gcc@gcc.gnu.org" <gcc@gcc.gnu.org>
Subject: Re: Release schedule
Date: Sat, 28 Sep 2002 10:06:00 -0000 [thread overview]
Message-ID: <43770000.1033231087@warlock.codesourcery.com> (raw)
In-Reply-To: <Pine.BSF.4.44.0209281604040.21836-100000@pulcherrima.dbai.tuwien.ac.at>
--On Saturday, September 28, 2002 04:15:29 PM +0200 Gerald Pfeifer
<pfeifer@dbai.tuwien.ac.at> wrote:
> On Wed, 25 Sep 2002, Mark Mitchell wrote:
>> After GCC 3.2.1 goes out, we will branch for GCC 3.3. Are there changes
>> that need to get in before we make that branch?
>
> I believe it would be a huge mistake branching with the high a number of
> _known_ regressions we currently have. We should strive to fix most of
> these in stage 3, not on the release branch again.
I agree. We neeed to do some bug-fixing work before we branch.
If necessary, I will ask the SC to close the various other development
branches. Part of our problem is that we are all working on new C++
parsers, SIMPLE, loop optimizers, and all kinds of fun stuff -- not
fixing bugs.
We need to remind ourselves that teamwork requires the tedium of drills
in addition to the fun of playing games.
Thank you for the list of PRs.
--
Mark Mitchell mark@codesourcery.com
CodeSourcery, LLC http://www.codesourcery.com
next prev parent reply other threads:[~2002-09-28 16:40 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-25 11:53 Mark Mitchell
2002-09-25 11:55 ` Dale Johannesen
2002-09-25 12:42 ` Michael Matz
2002-09-29 12:07 ` Richard Henderson
2002-09-30 7:21 ` Michael Matz
2002-09-25 13:19 ` David Edelsohn
2002-09-25 13:53 ` Frank Ch. Eigler
2002-09-25 14:45 ` Geoff Keating
2002-09-25 15:05 ` Devang Patel
2002-09-26 11:45 ` Eric Botcazou
2002-09-25 13:43 ` David S. Miller
2002-09-26 3:32 ` David S. Miller
2002-09-25 16:00 ` David Edelsohn
2002-09-29 12:58 ` Richard Henderson
2002-09-26 2:03 ` Richard Earnshaw
2002-09-26 9:25 ` Alexander Kabaev
2002-09-26 14:46 ` Florian Weimer
2002-09-26 14:59 ` Joseph S. Myers
2002-09-26 15:16 ` Zack Weinberg
2002-09-28 7:41 ` Gerald Pfeifer
2002-09-28 7:54 ` Gerald Pfeifer
2002-09-28 10:06 ` Mark Mitchell [this message]
2002-09-28 13:26 ` David Edelsohn
2002-09-28 14:52 ` Steven Bosscher
2002-09-28 16:00 ` David Edelsohn
2002-09-30 10:34 ` Mike Stump
2002-09-30 9:20 ` Richard Zidlicky
2002-09-30 10:30 ` Andrew Pinski
-- strict thread matches above, loose matches on Subject: below --
2002-09-30 16:02 S. Bosscher
2002-09-30 16:06 ` Pop Sébastian
2002-09-30 20:05 ` Joe Buck
2002-10-01 16:03 ` Stan Shebs
2002-09-28 13:06 Roger Sayle
2002-04-26 0:30 Release Schedule Jim Blomo
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=43770000.1033231087@warlock.codesourcery.com \
--to=mark@codesourcery.com \
--cc=gcc@gcc.gnu.org \
--cc=pfeifer@dbai.tuwien.ac.at \
/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).