This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: GCC 4.3 release schedule
- From: Andrew MacLeod <amacleod at redhat dot com>
- To: Gerald Pfeifer <gerald at pfeifer dot com>
- Cc: Jason Merrill <jason at redhat dot com>, Benjamin Kosnik <bkoz at redhat dot com>, gcc at gcc dot gnu dot org, Richard Guenther <richard dot guenther at gmail dot com>, mark at codesourcery dot com
- Date: Thu, 01 Nov 2007 11:57:11 -0400
- Subject: Re: GCC 4.3 release schedule
- References: <20071029102207.4750c4a2@concorde.artheist.org> <4725FF81.6050208@redhat.com> <47261C39.7090009@redhat.com> <Pine.LNX.4.64.0711011645190.26054@acrux.dbai.tuwien.ac.at>
Gerald Pfeifer wrote:
On Mon, 29 Oct 2007, Jason Merrill wrote:
I think I prefer Richard's suggestion of not branching until we're ready to
make the .0 release. The effect should be the same except that people don't
have to deal with checking patches in on the branch vs. the trunk until after
4.3.0 goes out.
I like this approach.
So have we come to some sort of consensus here? We leave mainline as
stage 3 until we release? or at least have a somewhat final release
candidate?
Once we hit the target of 100 open PRs,( or whenever we would have
originally cut a stage 3 release branch), we firm up stage 3 so that
*really* only bugfixes go in. Then we work toward a release candidate,
etc etc.?
We can play it by ear, but do you want to wait to open stage 1 until we
actually release 4.3, or do it after RC2 or something like that where
there isn't much else going to happen to it? Either works for me, but
I don't see that opening stage 1 before we actually release buys us much.
Andrew