About 6 weeks ago, I wrote a post announcing the availability of TFS 2018 RC1. In the comments, there ensued a sizeable conversation about the requirement for SQL Server 2016 or later (rather than also supporting SQL Server 2014).
This week we are deploying our sprint 124 work. You can get all the details in our release notes.
I’m running late this sprint so I’m going to keep my summary short.
The biggest change this release is in the work items and code search experiences.
Today we shipped the second release candidate for Team Foundation Server 2018. If all goes well, this should be the final release candidate. We’ll make sure that all the issues you report are addressed and we’ll ship the final version in a couple of months.
Today we released the Release Candidate for Team Foundation Server 2017 Update 3. Following the pattern of all of our Update 3 releases, TFS 2017 Update 3 is a small release, focused on bug fixes – mostly a roll up of fixes for issues that we’ve uncovered as increasing numbers of customers have adopted the TFS 2017 wave of releases.
Today we launched our latest Visual Studio Team Services instance in the Canada Central region. This adds to our instances in the United States, Europe, Brazil, Australia, and India.
I’ve had numerous conversations with customers who really wanted to have a VSTS account on Canadian soil and Canada was by far the most requested region for a new VSTS instance (and the 17th most popular request all up) on Visual Studio Team Services User Voice.
This week we are deploying our sprint 123 work. Check out the release notes. There are a few things I want to highlight…
New queries hub – We are on a journey to rework how some key elements of our navigation/data model work.
Team Foundation Server 2018 RC1 is now available for download. This is the first available build for what we have been calling TFS V.next. And, as you can tell from the title of this post, the official name will be TFS 2018.
I’m going to try something very non-traditional for my blog. I don’t know if it’s a good idea or not but we’ll give it a go and if everyone hates it, I’ll find a different vehicle. I’ve had a career of roughly 30 years now and I’ve been in countless situations from developer in a small startup,
Six months ago I wrote a post on Taking Feedback. Several people asked me to write a follow up on giving feedback. Amazing how time flies and somehow I just haven’t gotten around to it – so I’m doing it now.
After more than 23 years at Microsoft, I’ve decided it’s time for me to take a break. Starting March 12th 2018, I’ll be taking a leave of absence for a year. Deciding to do this has been one of the most gut-wrenching decisions of my life.
This week we began rolling out the sprint 131 updates. You can get the details in the release notes.
There are some good things in this sprint payload (a good start at a new Work items hub,
I wanted to call your attention to a good incident postmortem done by Taylor Lafrinere this week. Taylor sits in my team room and, for a week, I saw him bent over his keyboard, often with two or three people staring over his shoulders trying to figure out what had caused this incident and what we needed to do to prevent it in the future.
On Wednesday, we released a roll up of fixes for security vulnerabilities for several versions of Team Foundation Server. There are no new features in this update. Most of the vulnerabilities are related to cross site scripting (XSS), some of which were customer reported. The others include an improperly encoded API, a service endpoint editing experience which exposes a previously configured password, and a regex denial of service vulnerability in our web portal. We recommend customers install these updates. These fixes are included in the recently released Team Foundation Server 2018 Update 1. The release on Wednesday was for older versions and for customers who are not yet ready to update to the TFS 2018.
This week we updated the roadmap (Feature Timeline) for Visual Studio Team Services and Team Foundation Server. Check it out to see many of the significant improvements we are working on/planning. If you have feedback or suggestions for other improvements that are important to you,
Today we released the final build of Team Foundation Server 2018 Update 1. I've shared some key links in this post.
Let me start with a little background. Every year, we have new goats born on the farm – generally in March/April. Last year, we had about 10 or so. They live in the field with their moms until breeding season –
Today we released the release candidate for Team Foundation Server 2018 Update 1. I've shared some important links in this post.
One of the cool things about having VSTS used across all of Microsoft is that when there’s some useful missing feature, one of the many teams using it might fill the gap and we get to harvest it and make it available to all VSTS customers.
VS Team Services
Please read my post from yesterday first. Unfortunately I had a family commitment and had to leave early Friday afternoon before the post was complete. I asked someone on my team to finish it and he did an excellent job and I’m grateful.