> I have been clear in the past (March it was!), but that didn't happen.
> I also read on infrastructure@ "Helping hands needed", which seems to
> indicate that infrastructure@ guys are over-loaded, and could well
> explain the 'non-action' in March.
Actually, no. Fitz was working on improving cvs2svn, and I suppose just
kind of lost track. I really don't have another answer for it, and don't
think it constructive to belabor it.
> I think I made it fairly clear in the last post that any migration
> SHOULD not happen during the release process, especially since it
> is common sense.
That's perfectly reasonable, which is why migration is being delayed until
after the Release Manager tags CVS, and informs us that the Release is
final.
> I can prepare the structure, which will be significantly different
> (can be seen in svn://repos/test/avalon), in advance, and not have
> figure out branching and merging on Day 1 (took me several years
> before I tried that on CVS).
Actually, it is really easy in Subversion. Branches, tags, even the "trunk"
are really just directories containing lightweight copies. A branch is just
a directory in which you continue development; a tag is a directory that you
don't change. The fact that one branch is the trunk, and another is a
branch is a semantic of use.
--- Noel
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
