What are Microsoft's plans for distributed source control?

As far as I have heard, a lot of development is moving to Team Foundation Server internally. This post on the Team Foundation Server Blog supports that: http://msmvps.com/blogs/vstsblog/archive/2008/08/17/how-microsoft-uses-team-foundation-server-internally.aspx

As far as the article you reference, it makes some statement about it being "April 1st" at the bottom, though the article is dated March 25th, so I'm not sure what the deal is with that. At this point, I would not trust a blogspot blog over an MS TFS blog.

I'm not sure it is in Microsofts interest to provide a distributed version control system. If people are interested, there are other systems that already exist. The world doesn't need to and shouldn't wait for Microsoft to give a system/idea/tool their blessing by developing a competitor to an existing project. In fact, people are so familiar with the Team Foundation Server/ Visual Source Safe methods of version control from Microsoft, that a paradigm shift of this kind would probably alienate their customer base. On the other hand, so many drink the MS kool-aid religiously, and won't do anything that isn't officially Microsoft, that the change would open the eyes of a lot of developers to alternatives. And how could Microsoft be wrong? They are the biggest software organization in the world.

I have some thoughts on using Distributed Version Control (specifically git) in the corporate workplace on my blog here: http://nerdfurio.us/blog/post.aspx?id=c64bf098-7a5a-de11-aa53-001143eed2d5

Its your blog, so you can certianly write about whatever topic strikes your fancy. However, as a source of info for others, you kinda lost me right here: "I'm writing this as someone who has never used Git, and does not completely grok how Git or Distributed Source Control works". Come on! At least figure out how it works before trying to tell everyone else that it won't (or will) work.

T.E.D. 2010-09-08 21:59:36

I don't have to grok something to understand fundamentals, and Git is only a tool that implements the concepts of distributed source control. Replace Git with Mercurial or Bazaar, and the same argument exists. To grok something takes lots of experience. I was open and honest that it was an opinion, and stated my experience. I have since used Git, and while I like it, my opinion stands that it will be a hard sell to enterprise dev shops. They are happy with TFS, which requires a connection to the server at all times, or good luck getting changed code checked in.

NerdFury 2010-09-09 13:38:57

ansaurus

tags:

views:

answers:

What are Microsoft's plans for distributed source control?

related questions