[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Subversion Vs. Microsoft Team Foundation Server

From: Les Mikesell <lesmikesell_at_gmail.com>
Date: Fri, 06 Mar 2009 12:56:36 -0600

David Weintraub wrote:
>> One of our development teams is planning to move to Subversion from
>> Microsoft Team Foundation Server , for many obvious reason, one being the
>> cost. However, in order to justify the move to powers-that-be we need some
>> sort of comparison report. I have been looking at all the posts on the net
>> and have not found one. Has anyone in these email list done such a
>> comparison and if so, can you tell me what have you found. Most reports I
>> have seem to suggest the TFS is far better than SVN ( of course this comes
>> from Microsoft site itself ).
> TFS has a lot of bling and whistles, so a simple straight comparison
> will make it shine.
> The big question is why are you moving from TFS in the first place. Is
> it because you're simply more familiar with Subversion? Or, have you
> had problems with TFS -- maybe difficult to use or slow? Have you lost
> data with TFS or find that it doesn't integrate well with other
> systems you have? Or, is it simply a matter of cost? You can no longer
> justify the spending of $X for each and every developer because it
> takes up so much of your budget.
> That is much more important than some sort of feature check-off chart.

In the bigger picture you probably do need to look at the features you
use and need, and while subversion provides only version control you can
use your choice of other packages for the rest. For example you might
want to use Trac for bug tracking and Hudson as a build system.

   Les Mikesell
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-03-06 19:57:49 CET

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.