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
test 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.
At home:
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.
Regards, Guy
[ February 15, 2006: Message edited by: Guy Allard ]