GCC 3.3, GCC 3.4

Mark Mitchell mark@codesourcery.com
Sat Feb 1 01:32:00 GMT 2003



--On Friday, January 31, 2003 04:54:29 PM -0600 Benjamin Kosnik 
<bkoz@redhat.com> wrote:

>
> Agreed. Seems to be a common concern.
>
> Mark, I think keeping at least a month in between the two events is
> advisable.

That actually is our normal plan.

But it's a bit hard to have it both ways -- if we can't commit to a
3.3 date (as you suggested yesterday that we should not) then we can't
really schedule the 3.4 cutoff.

But, we have been in 3.4 stage one for quite some time now, and Geoff
and I both managed to get our work ready at that time.  Stage 1 isn't
really for *developing* new major changes, it's for *integrating* them.

We could just close the mainline during a release, but it's very clear
that nobody wants to do that -- we want to make sure development can
happen while a release is being prepared.  That inherently means that
there's going to be some division of people's time between the two
branches.

-- 
Mark Mitchell                mark@codesourcery.com
CodeSourcery, LLC            http://www.codesourcery.com



More information about the Gcc mailing list