[lmi] Converting...to svn? [Was: Savannah status]

[Greg Chicares]

On 2009-06-01 13:20Z, Vadim Zeitlin wrote:
> On Mon, 01 Jun 2009 13:14:44 +0000 Greg Chicares <address@hidden> wrote:
> 
> GC> We committed only eighteen changes in May, which we can recreate
> GC> if necessary. I guess it wouldn't be a bad idea to mirror the
> GC> repository periodically
> 
>  FWIW I do have an automatically updated bzr (http://bazaar-vcs.org/)
> LMI repository mirror at
> 
>       http://bzr.tt-solutions.com/lmi/upstream/
> 
> which is, I think, up to date as it was updated every hour before cvs
> master went offline. The last change in it is
[...]
>         [lmi @ 2009-05-26 13:31:26 by chicares]
>         Use dates instead of durations for inforce

That was indeed the last update.

> I use tailor (http://progetti.arstecnica.it/tailor) to convert cvs to bzr
> but it is also possible to do the reverse and recreate the cvs repository
> from bzr (with the full history, as opposed to just the latest working
> copy) if necessary.
> 
>  Please let me know if you'd like me to do anything like this,

That would be a big help.

Actually, would this be a good time to upgrade to a better version-control
system? In the past, we discussed using svn; to paraphrase our private
discussion of 2008-01-28T19:16Z:
 - its interface is very similar to cvs's, so it'll be easy for us to
     learn (BTW, we use no GUI for cvs, just the command line);
 - lmi is a simple project with relatively few files and directories;
 - we rarely use branches;
 - svn allows renaming files (and we rename them often); and
 - svn has a native http interface, which solves the problems we've
     encountered when trying to use cvs pserver from behind a firewall.
It just so happens that the MEC-testing work we've planned for June
is mostly brand new and needn't be committed in pieces over time; and
cvs.savannah.nongnu.org is out of commission for now; so all omens seem
to augur well for converting now. What do you think?