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 »
Today, fast on the heels of Update 1, we released the first CTP of VS/TFS 2013 Update 2. Although Update 1 was a pretty small release, Update 2 is much larger. This CTP is *not* feature complete and it is *not* “go-live”. It is an opportunity for you to get a peek at some of the things we are planning to release in Update 2. The next CTP (at least of TFS) will be feature complete and “go-live”.
In this post, I’m going to talk mostly about Application Lifecycle Management (ALM) related improvements coming in Update 2. For the most part, we focused on continuing to “round out” features that have been previously introduced.
In TFS 2012.2, we introduced lightweight work item tagging to easily categorize and find work items. We’ve generally gotten good feedback on the feature but plenty of requests for enhancements. Here’s some things we are adding in this release:
We took a bunch of small, but popular requests off our backlog that involved helping you manage your backlog, including:
We introduced charting in VS 2013 and we’ve done some work in Update 2 to make charts a little more useful.
We’ve refreshed the layouts of the account and project home pages to try to make them even more useful.
You can now export your test plan to HTML for offline reading/sharing, printing, etc. You can choose the level of detail you want to include in the document.
We added a new concept of “Tags” (different than work item tags, just to confuse you) that enables you to tag deployment targets. Tags can be used to treat a set of machines the same. For instance, this allows you to easily deploy the same software to all the machines in a web farm without having to author anything redundantly – just by tagging all the machines the same way.
These really only get an honorable mention. I include them only because in a previous post, I had mentioned that Git improvements was an area we are focused on. Unfortunately the Git improvements just barely missed the cut-off for Update 2 CTP1 so they aren’t in this CTP but will be in CTP 2. So you won’t find them in this build but expect them soon.
Of course, we also fixed quite a few bugs but I’m not going to try to include a full list here.
I’m looking forward to getting a go-live release in your hands so you can give it a go for real but, if you are brave and willing manage through some known issues (see the KB article), check out the CTP and make sure the features work the way you want.