This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: Help with changing snapshot mechanism
- From: Gerald Pfeifer <gerald at pfeifer dot com>
- To: Mark Mitchell <mark at codesourcery dot com>,"Joseph S. Myers" <jsm28 at cam dot ac dot uk>
- Cc: gcc at gcc dot gnu dot org
- Date: Sat, 17 Jan 2004 20:31:46 +0100 (CET)
- Subject: Re: Help with changing snapshot mechanism
Mark Mitchell wrote:
> Does anyone know what should be done to switch snapshots to the GCC 3.4
> branch?
Yes, at least I hope so. :-) Mind if I take care of the snapshot issue?
Joseph S. Myers wrote:
> Gerald did the work to support snapshots from both mainline and branches
> simultaneously, but it may not have been finished since that
> documentation wasn't updated and there are some un-checked-in changes in
> ~gccadmin/scripts/.
It ought to be finished (apart from one minor issue concerning prereleases
which I had postponed until the generation of the 3.4 branch and will
discuss with Mark now). The diffs you have been seeing were purely
cosmetic, and I committed them now.
> Changing the crontab (in CVS, in ~gccadmin/scripts/ and in the installed
> crontab for gccadmin) where it reads "-s 3.4:HEAD" to read "-s
> 3.4:gcc-3_4-branch" will do the part of causing branch snapshots. I
> think they should even get diffs smoothly generated from the last
> mainline 3.4 snapshot.
Yes, that should work fine.
> (Stopping 3.3 snapshots is a separate matter for when that branch is
> closed; there should be no intrinsic problem with having three sets of
> snapshots going as long as whoever deletes old snapshots to keep down
> disk space usage does so more frequently.)
The policy I had in mind was not making snapshots from mainline until
x.y.0 has been released, to put a stronger focus on release work and
especially testing, so for now I'd like us to only provide snapshots
of the 3.3 and 3.4 branches.
> But mainline 3.5 snapshots should also be started up, and the first of
> them should have diffs from 3.4-20040114, and I don't know what the
> correct mechanism for arranging these diffs (from a different version
> number) is, but it should go in the branching checklist.
I think I can make this work (even though I have never used this aspect
of the script before. How about me running a manual first snapshot for
3.5, to get the branching done right, even if we won't provide regular
snapshots until 3.4.0 has been released?
Gerald
--
Gerald Pfeifer (Jerry) gerald@pfeifer.com http://www.pfeifer.com/gerald/