Manning's Countdown to 2014
. Use discount code crdotd14 all month for 50% off every deal.
A friendly place for programming greenhorns!
Big Moose Saloon
Register / Login
IDEs, Version Control and other tools
CVS vs Subversion
Joined: Feb 06, 2006
Feb 15, 2006 16:10:00
I've been working with CVS for quite a while, but I've been hearing
Can anyone tell me what pros and cons does Subversion has ?
Should I switch or should I stay with CVS ?
Joined: Nov 24, 2000
Feb 15, 2006 17:05:00
I'll describe two cases.
At work we:
Left currently existing CVS projects there, made little attempt to convert them, and continue to use it (particularly several "large" projects).
Converted a few small projects to SVN, just for parctice.
Used SVN for several small new projects. To
the waters. Interestingly, the non-Java (MS) folks in the group jumped on this with Ankh, because they hated VSS.
Are now using SVN for anything new.
I converted everything I had to SVN. Would not want to go back. I have gotten sloppy about directory names, because I can just rename and/or delete them (they are not really gone of course).
There is a *lot* I have not explored yet - particularly 'properties'. But I highly recommend SVN.
Repository backups are (of course) essential. From the SVN source distribution, you can get a 'hot-backup.py' script to give you some easy help with that.
I would say install it, play with it until you feel comfortable (or not). Then make a decision.
[ February 15, 2006: Message edited by: Guy Allard ]
It is sorta covered in the
JavaRanch Style Guide
subject: CVS vs Subversion
When i should use SubVersion ?
CVS & Eclipse
Setting up and configuring Subversion and Bugzilla
CVS extra files
experience with pre/post-commit hook to enforce code-conventions
All times are in JavaRanch time: GMT-6 in summer, GMT-7 in winter
| Powered by
Copyright © 1998-2013