Date: Wed, 11 Jun 2003 16:35:27 -0400
Message-Id: <200306112035.h5BKZReG030855@envy.delorie.com>
From: DJ Delorie <dj AT delorie DOT com>
To: djgpp-workers AT delorie DOT com
Subject:  Fwd: GCC 3.3.1 and GCC 3.4 Schedule
Reply-To: djgpp-workers AT delorie DOT com


It would be *really* nice to be able to build 3.3.1 "out of the box"
(er, at least as far as gcc's release goes, which means plus-or-minus
libc changes ;)

From: Mark Mitchell <mark AT codesourcery DOT com>
To: gcc AT gcc DOT gnu DOT org
Subject: GCC 3.3.1 and GCC 3.4 Schedule


After a bit of discussion with the GCC Steering Committee, we've set
target dates for GCC 3.3.1 and the mainline.

We will target GCC 3.3.1 for Friday, July 18th.  That means that we
will freeze the GCC 3.3.1 code base on Friday, July 11th.  There are
relatively few open high-priority bugs for GCC 3.3.1, so I expect this
release to go relatively smoothly.

Stage 1 for GCC 3.4 will come to an end on Friday, July 4th.  It has
already gone on for quite some time, but it's important that we give
enough notice for people to get their last projects completed.

After Stage 1 comes to a close, we'll start on Stage 2.  This time,
we'll not branch for Stage 3 until we've already gotten the bug count
down to a manageable number.  We'll also need to make some progress on
compile-time issues before we branch; we've simply got to get that
problem under control.  [Nathan, Zack, and I have a couple of good C++
tricks up our sleeves that we'll be implementing.]

GCC 3.5 is expected to contain the tree-ssa merge.  At the GCC Summit
it was clear that many people felt that the tree-ssa work is of vital
importance to GCC's future.  I expect to work closely with the
tree-ssa people as we get closer to GCC 3.5 to set schedules that work
well for that group.

Yours,

--
Mark Mitchell
CodeSourcery, LLC
mark AT codesourcery DOT com