Re: Thoughts about migrating Mantis from CVS to Subversion

Hello,

I migrated the whole CVS repository of our company two years ago to Subversion 
and we are quite happy with it. The atomic commits spanning several files and 
much more features provide much better functionality than CVS. So I would also 
vote for the switch.

If we want to preserve the versioning history, tags and branches, there is a 
migration guideline at Sourceforge: http://sourceforge.net/docs/E09#import

If that's not needed, simply starting with an empty SVN repository and adding 
the current CVS code is enough. It may also be possible to additionally import 
selected tags for some recent releases.

Regards,

    Martin

On 28.10.2007 23:02:54 Victor Boctor wrote:
> Hi all,

> Justed wanted to know your thoughts about moving Mantis code base from
> CVS to Subversion.  I have been thinking about this for a while and
> have tested Sourceforge Subversion support on the MantisConnect
> project and it seems to work fine.

> I personally prefer Subversion compared to CVS any day. However, I
> would also like to know your opinions with regards to whether this
> will have any effect on contribution of patches, etc.
> Increase/decrease/no effect.

> When I migrated MantisConnect, I just re-added all the files to an SVN
> repository, so I haven't tried the migration process in Sourceforge.
> >From memory, this wasn't fully done by then.  So did anyone out there
> do such migration where the history is kept intact?


-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/