|
Hi,
Within our department we currently discuss two options for replacing VSS: Subversion and TFS.
Well, I know that TFS does much more, that it links changes with Work Items, does reports etc, etc.
But right now we are primarily concerned about version control capabilities.
I know that TFS does shelving, but a similar thing can be also accomplished with SVN: http://svnbook.red-bean.com/nightly/en/svn.branchmerge.tags.html
Are there any other advantages? Any clear reasons why NOT to go with SVN?
My managers are just primarily afraid of the MS slow development lifecycle.
Let's face it. It is the first version and most likely it will take *years* before we see SP1, as it was the case with VS.Net, VS 2003 or VSS. And most likely SP1 will be released only after a new, major version is out on the market available for purchase to those who believe that it fixes all those small, sometimes painful, issues they had to deal with for years with the current version. Again, as it was the case in the past.
Are there any *convincing* arguments that this, I believe business dictated policy, has changed? Any official statements? Any Official promise? Any signs that MS recognizes that this approach no longer works to MS sales advantage?
I personally believe that TFS would be a better choice but I need real, strong arguments.
Thank you,
Tomasz |