Hi there,
I'm currently investigating on some candidate version control systems for
deployment in our company, and Subversion is included in the list. I already
did some testing on svn and found it pretty easy to use. I tested the
combination Subversion+TortoiseSVN connected to Subversion/Apache2.
Everything seems to be there and readily available. But of course, testing
is on small repos, not on the real-life big ones.
I found out that many people complain about Subversion's branching/tagging
mechanism. For one thing, this seems to become the most dominant issue about
Subversion. I compared it with other tools (BitKeeper, Perforce, ClearCase,
Surround SCM) and they claim to do a better job.
Here are some references that discourage the use of Subversion:
http://www.bitkeeper.com/Comparisons.Subversion.html
http://www.maynidea.com/topics/subversionstinks.html
http://www.pushok.com/soft_svn_vscvs.php?PHPSESSID=392eaa27da6675121041fa261
c30fa49
They all complain about missing features that are already fixed, but
branching remains an issue. I also received a confidential note from Seapine
(Surround SCM) in which branching in Subversion is said to be a disaster.
But I like Subversion! Anyone there with a good opinion on how to
successfully use branching in a team with some 15 developers on the same
code base?
Thanks in advance,
Onno
----------
Onno Verkerk,
Senior Software Engineer
Optelecom-NKF B.V.
The Netherlands
www.optelecom-nkf.com
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Mon Jul 4 13:16:49 2005