This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: branch merging
- From: Mark Mitchell <mark at codesourcery dot com>
- To: Alexandre Oliva <aoliva at redhat dot com>, Richard Kenner <kenner at vlsi1 dot ultra dot nyu dot edu>
- Cc: "jh at suse dot cz" <jh at suse dot cz>, "gcc at gcc dot gnu dot org" <gcc at gcc dot gnu dot org>
- Date: Mon, 19 Nov 2001 13:35:26 -0800
- Subject: Re: branch merging
>> This has also been my concern for a while. The situation is likely to be
>> made worse during the December 15 to February 15 period since people will
>> then need branches to do *any* development work.
Fundamentally, there are two possibilities:
- There are capable people available to produce a stable 3.1 release.
- There are not.
If everyone (and believe me when I say I understand) is busy with
other projects, other than producing a release, and nobody has time
to contribute toward the release, then we will be in trouble.
There will be lots of branches. Nobody will fix bugs in the mainline.
The branch will get created, but nobody will fix bugs there either.
There will either not be a release, or it will not be a good one.
However, let's be optimistic, and assume that people will pitch in
to help. Hopefully, the companies that employ many of our best
contributors will realize that GCC benefits in the long run from
having releases, so they will be willing to help with some
bug-fixing. Maybe some organizations will even fund this kind of work,
as they have in the past.
In that scenario, we'll get a good release.
Then, the merging will happen during the first two months of the
next release cycle. There will be some temporary instability,
but hopefully not too much.
If this does not work, we will have to cross that bridge when we
get there.
--
Mark Mitchell mark@codesourcery.com
CodeSourcery, LLC http://www.codesourcery.com