Community technical support mailing list was retired 2010 and replaced with a professional technical support team. For assistance please contact: Pre-sales Technical support via email to sales@march-hare.com.
Oliver Giesen wrote:
> S Wagle wrote:
>
>> Lately I have been debating whether to go with CVSNT or Subversion.
>>
>> I have never actually used Subversion but just heard about it:
>> http://subversion.tigris.org/.
>>
>> So I was wondering if others have used it before and have any
>> thoughts to share.
> For a comparison take a look at: http://www.cvsnt.com/cvspro/svn.htm
> (right hand side of the page).
>
> Note that the above list does not contain any features that SVN has but
> CVSNT doesn't, ...
It also seems to be a bit outdated WRT SVN. SVN is under constant
development. See here some comments on this comparison:
http://lists.boost.org/boost/2005/04/24960.php
Another interesting link that came up when googling for "subversion cvsnt
comparison" is http://www.dwheeler.com/essays/scm.html
> That said, I also don't use SVN myself
Neither do I, but I'm seriously considering it. The main reason for that is
that I'm slowly losing trust in the development process of cvsnt. Binaries
for previous stable builds are not available anymore (so you need to keep
your own copies around), there's no publicly available bug database (so you
need to keep your own log, extracted from the mailing list about what works
and what doesn't in every stable build you may consider for updating),
there have been some showstopper bugs in releases called stable ("&" in
file names messed up the meta files), and so on... It seems cvsnt is in a
constant flow, fixing some bugs while introducing others, and there's never
a stable point where you can take a build and deploy it with confidence. By
the time it's confirmed that a build works, it's not available anymore...
or better, by the time it's confirmed what exactly doesn't work in a stable
build, these bug fixes get included in the current development cycle,
which, of course, when it gets released as stable, has its own new bugs. So
I get the feeling that whenever I think of updating my server, I'm in for a
deep plunge, with the fix usually being to update to the latest development
build, with the associated risks.
Gerhard