RE: cost/benefit of moving CVS server (on RH 7.3) from version 1.11.1p1to version 1.11.21 or version 1.12.13? Migrate to Subversion?Migrate to Perforce?

[Arthur Barrett]

Ken,

 

If you are expanding your choices to things like SVN and Perforce, then CVSNT (free, GPL, Linux/Unix/Windows/etc) may be worth considering.  CVSNT also has a commercial variant if you need support (CVS Suite).

 

Personally I think that choices of SCM ought to be made on business benefit, not on technical bullet points.  So how is your organisation hoping to benefit from SCM?  Eg: Quality, Cost, Market Diferentiation etc?  Then look at the process that wil help you achieve that result, then look at the tools that support that process.

 

Upgrading to CVS 1.12, CVSNT 2.5, SVN or Perforce is not a "magic bullet" - you'll most likely end up with the same situation you have today without any additional business benefit and having spent a whole lot of somebody's time.

 

With the CVSNT project we've tried to focus on features that do provide a business benefit, such as Audit, change sets, mergepoints (tracking when / where merges were made), and various Integrations: email, shadow, bugzilla, SCCI, etc.  CVSNT also supports atomic checkout, rename, "hot standby" etc etc.  CVSNT 2.6 is just starting test cycle and improves rename, tagging etc.

 

Regards,

 

 

Arthur Barrett

 

 

-----Original Message-----
From: address@hidden [mailto:address@hidden On Behalf Of Kenneth Wolcott
Sent: Saturday, 13 May 2006 4:19 AM
To: address@hidden
Subject: cost/benefit of moving CVS server (on RH 7.3) from version 1.11.1p1to version 1.11.21 or version 1.12.13? Migrate to Subversion?Migrate to Perforce?

Hi;

  What is cost/risks/benefit of moving CVS server (on Red Hat Linux 7.3) from version 1.11.1p1 to version 1.11.21 or version 1.12.13?

  Of course I'm considering moving to a more recent version of Linux :-)

  I have some developers who are strongly encouraging me to migrate from CVS to Subversion.

  Other developers strongly suggest that we migrate from CVS to Perforce.

  Has anyone here moved from CVS to Subversion and regretted it and moved back to CVS?

  We are eager to move to an atomic commit functionality.

  We are also eager to move to a versioned directory functionality to facilitate code restructuring.

  There are those who belief that branching and merging are easier/more intuitive with Perforce and/or Subversion as compared with CVS.
 
Thanks,
Ken Wolcott