This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: Suggested 'plan of attack'
- From: Mark Mitchell <mark at codesourcery dot com>
- To: Nathanael Nerode <neroden at twcny dot rr dot com>, "gcc at gcc dot gnu dot org" <gcc at gcc dot gnu dot org>
- Date: Mon, 16 Dec 2002 11:46:06 -0800
- Subject: Re: Suggested 'plan of attack'
--On Sunday, December 15, 2002 09:24:29 PM -0500 Nathanael Nerode
<neroden@twcny.rr.com> wrote:
This is just a scheduling idea I'm throwing out to Mark.
For each branch (or other big destabilizing stage 1 type change) which
is ready to merge, put it on the end of a list:
B-I-B
cp-parser
PCH
?-branch
For each branch, have a set period devoted to merging the branch:
First one or two days when only the branch merging person can commit to
the trunk or branch, so they can get it done right.
Then a two to four day period of bug fixing only.
Then a short period open for all 'stage-2-worthy' patches (to relieve
patch list pileups). During this period, the 'next' branch will be
updated to the new trunk so that it will be able to merge fairly
cleanly.
This is approximately what I have in mind; I'll try to manage the merge
stages for each branch that wants to come in. The whole point of our
development plan is to make major changes in stage 1, so we have to let
that happen now, and we'll make sure that things that are queued up and
ready to go get a chance to come in.
Thanks for thinking this through.
--
Mark Mitchell mark@codesourcery.com
CodeSourcery, LLC http://www.codesourcery.com