Re: [wxCode-users] Moving wxCode components from CVS to SVN?

[Ulrich T. <ulr...@gm...>]

Hi Ronan,

> I am pro-Subversion (for me an obvious improvement), although my
> component is still under CVS. I also agree that having 2 different
> repositories makes little sense other than during a transition phase.

... and this transition phase lasted already several years (Francesco
introduced SVN to wxCode years ago). Now there are even developers
favoring Git or Mercurial above SVN.

> My only objection / concern is with history: components under CVS are
> logically the older ones, and in some cases (like mine) were inherited
> from other developers. The comments in CVS (assuming our predecessors
> have commited with comments) are sometimes the only information
> available as to why something was implemented in a certain way.
> 
> Therefore I am in favor of a migration CVS ==> SVN which ideally
> includes migrating history, at least in a dedicated branch; obviously
> more effort, and I have never done it myself.

Neither have I, but there is a tool cvs2svn which is said to support
migration including history. I'll have to dig through the documentation
to find out which steps are required to move components separately from
CVS to SVN without damaging the SVN repository.

> Happy to let you & the rest of the wxCode community decide, this was
> just some input.

I think I can at least move all currently unmaintained components. But
this has to wait until SourceForge's services are available again. I'll
announce on this list when I prepare the migration.

Regards,

Ulrich