Progress migrating projects away from CVS and next steps

Erik Huelsmann ehuels at gmail.com
Thu May 7 10:10:07 UTC 2015


Hi all,


Next week, the last batch of CVS repositories will be migrated. Based on
feedback on earlier batches, they will most likely be migrated to Git (so
far, there were no projects opting for Subversion instead of Git).

After that step has been completed, work will move on to migrate Darcs
repositories to Git so we can phase out Darcsweb. Preparations for this
migration can't be started while the CVS migration is on-going due to time
constraints on my part. This means that it'll take a while before any
visible progress will be made.
As for the procedure to be used, I've yet to decide whether to go with the
CVS approach where we did batches or to go with the Git approach where we
did everything at once. Given that there are Darcs repositories litterally
all over the place, I'm currently leaning to a phased migration.

There are somewhere between 280 and 600 darcs repositories to be migrated.
By looking at the paths in the server, it looks like there are over 600
darcs repositories, however, it seems that some of them are 'public_html'
clones serving the purpose of being the document root.

With the knowledge I currently have about the darcs repositories, current
users of the system can really, really help by cleaning out any Darcs
repositories they have laying around which they don't need any more and
which need not be migrated to Git.

Projects could help by indicating which repositories they consider the
canonical source and which ones are simply used as workspaces to serve
anything from.

Anybody who wants to help create a list of Darcs repositories which should
and which ones shouldn't be migrated: your efforts and inputs are greatly
welcomed!


Kindest regards,


-- 
Bye,

Erik.

http://efficito.com -- Hosted accounting and ERP.
Robust and Flexible. No vendor lock-in.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mailman.common-lisp.net/pipermail/clo-devel/attachments/20150507/9d9e337f/attachment.html>


More information about the clo-devel mailing list