Brian Harry's Blog

Everything you want to know about Azure DevOps and Farming

April 2016 - Brian Harry's Blog

Update on TFS 2015 Update 2.1

April 28, 2016 Apr 28, 2016 04/28/16
Brian Harry
Hmm, it's been a few days of reflection.  I don't think I expected my post on the bugs we were fixing in Update 2.1 to generate so many comments about other bugs that people are hitting.  Let me share some questions that have been on my mind and my thoughts on them... Why did I get so many bugs reported as comments on my blog? In the end, my...

Team Services in India

April 26, 2016 Apr 26, 2016 04/26/16
Brian Harry
Today, we opened up an instance of Visual Studio Team Services in India (Chennai).  This builds on the instances we already have in the US, Europe and Australia and is the next step in our journey to making instances available all over the world. You can create an account in India by just choosing the India region during the Team Services ...

Heads up: TFS 2015.2.1 coming

April 26, 2016 Apr 26, 2016 04/26/16
Brian Harry
By now, I suspect, everyone is pretty used to our cadence for shipping Team Foundation Server.  We ship a "major" release every year or so and then we ship "Updates" about once a quarter.  We just shipped TFS 2015 Update 2 a few weeks ago (otherwise known as TFS 2015.2).  We've been watching the feedback on that release closely and we've ...

VS Team Services Update – April 13

April 13, 2016 Apr 13, 2016 04/13/16
Brian Harry
This week we are deploying our sprint 98 work to Visual Studio Team Services.  You can read the release notes for details of what's included. From time to time, I like to cross reference the work we are releasing with UserVoice to make sure we are actually making progress on the top requests from our users.  It's good to see that we knocked ...

Team Services and TFS Roadmap update – Apr 2016

April 13, 2016 Apr 13, 2016 04/13/16
Brian Harry
Today, we refreshed the roadmap for Visual Studio Team Services and Team Foundation Server.  We've retired the items that were scheduled for Q1/Update 2, updated the items scheduled for Q2 and added the plan for Q3. We completed a significant majority of the things we planned to.  A few things did not complete in Q1 and have been rescheduled...