On Tue, 2011-10-04 at 22:24 -0700, Maciek Sakrejda wrote:
> Yes, absolutely. The repo doesn't even have to be public initially
> (i.e., you just do the export by creating a new repo on your
> workstation and only share it when you're happy with it). The nice
> part about this is that we can attempt migration several times (if
> necessary) without having to babysit it, and abandoning a failed
> migration doesn't impact the current CVS repo. The only issue is that
> a full export makes the CVS server sweat a little bit.
>
> In fact, the process probably should be such that someone comes up
> with a converted repo and semi-automated verification steps. This can
> be inspected and verified by anyone interested, and once there's
> consensus, we can start talking about blessing that particular export
> as the new official one, and pushing that to the official repo. The
> CVS repo is fairly low-volume, so manually re-applying any intervening
> patches should not be a problem.
Is it possible to put a snapshot copy of the cvs-directory somewhere, so
people who is interested can download the cvs-repo and set it up locally
for test-mirgrations?
Mvh
Kny
