Everything you want to know about Visual Studio ALM and Farming
Brian Harry is a Microsoft Technical Fellow working as the Product Unit Manager for Team Foundation Server. Learn more about Brian.
More videos »
It's been about 4 months now since I published the first Team Foundation Server roadmap. A lot has happened since then. For one thing, we've just about completed all of the feature work (final feature checkins will be this week). For another, we announced the acquisition of devBiz - which I knew was in the works when I wrote the first one, but couldn't talk about :(.
We're approaching releasing Beta 1. Not all of the TFS feature work that I describe here will be in Beta 1 - we forked off Beta 1 for stabilization a couple of months ago and have been working on the final features for Beta 2 in parallel. I'll talk about the full set of features here but try to be clear about what's in Beta 1 and what is not. You can look here for a broader VSTS roadmap, including comments on Rosario. This post will have a bit detail on TFS than the broader roadmap does, but as last time, I'm not going to say too much about Rosario - I plan on getting detailed about that in another few months.
TFS Power Tools
Our grand vision for Power Tools has also suffered somewhat from the demands of completing Orcas. We've had some good successes - we shipped an updated MSSCCI provider, the Process Template Editor, the checkin policy pack, enhancements to TFPT.exe and more but we haven't ben releasing updates as frequently as I had hoped. Here's an update on some of the stuff still in the pipe:
The list has gotten shorter because we shipped most of it and we haven't rebuilt the list. Over the next month or so, I hope to define what the next Power Tool release will be and develop a schedule for it.
I've described Orcas as a "minor" release for TFS but then we just kept adding features to it. In the grand scheme of things, it's still going to be a minor release but it's much bigger than we originally thought it would be. The focus is still on addressing key customer feedback and fixing adoption/deployment blockers.
I'm going to start with the bad news. There are a few things that we expected to be in Orcas (and I described them in the last roadmap) but had to be cut in order to make our schedule. I'm sure I'll take a beating for them because they are good features that I really want but they just didn't make it. We'll be looking at them again for Orcas SP1 and Rosario.
Features cut from Orcas
And on to the the more exciting list of features that will actually be in Orcas... I've marked significant additions since the last roadmap report with (new). I've marked things that are not coming until Beta 2 as (Beta 2).
Administration, Operations & Setup (Beta 2)
Work Item Tracking
Compatibility (no change since last time)
As Orcas is an adoption focused release, we have put a lot of emphasis on compatibility with VS2005. We are striving for near 100% compatibility. The Orcas client will be able to work with a VS2005 server and a VS2005 client will be able to work with an Orcas server. There are only a few compatibility issues.
The release after Orcas
As I mentioned, I'm not really going to talk much about this right now. See http://msdn2.microsoft.com/en-us/teamsystem/bb4073... for more info right now. I'll write a Rosario roadmap post in a few months.
To a first approximation, this will be the final Orcas feature list for TFS. While I have not included a thorough list of the thousands of small bug fixes/improvements that we've made, it represents the big things. I hope it is to your liking and we're looking forward to your feedback in Beta 1 and Beta 2.