if you look at "all the possible solutions available", you will never
choose because there are at least dozens and maybe more. my advice is
to evaluate systems until you find at most 3 that meet your known needs
(including future), then stop looking and pick one. unless you are
really, really special I don't think it would be difficult to come up
with three good candidates.
I'll even seed the flamewar: look at git, svn and perforce. like
gigantic systems that require multiple adminstrators? substitute
clearcase for one of the above. don't care about atomic commits and
speed of remote diffing? substitute cvs for one of the above.
dxc
Kenneth Porter wrote:
> Another advantage of SVN over CC and Perforce is its open source and,
> therefore, open standards nature. Your data isn't "locked up" inside a
> proprietary system as it has been with VSS and would be with CC and
> Perforce.
>
> But this advantage isn't limited to SVN. You should also look at other
> OSS source control systems. Some are built on top of SVN, while others
> are independent. They may suit your desired development model better.
>
> I'm happy using SVN in my shop and I helped a small corporate software
> group migrate from VSS to SVN, with which they're happy. But your needs
> may be different from mine, so you should look at all the possible
> solutions available.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: users-help@subversion.tigris.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu May 10 02:57:18 2007