GCC 3.3 Branch

[Geoff Keating]

Zack Weinberg <zack@codesourcery.com> writes:

> Geoff Keating <geoffk@geoffk.org> writes:
> 
> > Does it have the necessary builds & tests on three platforms?
> 
> Not yet - the merged tree doesn't exist yet.  I can arrange testing on
> two platforms (although this will take longer than four hours); I'd
> need a volunteer for the third.  I don't want to keep the tree locked
> for too long, but I'm also worried about merge conflicts if people
> start checking in dev-stage-1 stuff on the mainline before
> basic-improvements is merged back.  Ideas?

The description says that it is the branch that must be tested, not
necessarily the merged tree, so what you probably want to do is freeze
the branch, test that on 3 processors, then create a merged tree, test
that on one platform quickly, then commit.

Of course, testing the merged tree is even better.  Better still would
be to freeze the branch, merge the current mainline to it, call for
testers, wait a few days or a week, and then if there are no
regressions found do the merge.  This is so much the preferred way to
merge a set of complex changes that I'd support making it mandatory;
no one person has access to as many machines and as much source code
as the group.

-- 
- Geoffrey Keating <geoffk@geoffk.org>