I like to write, from time to time about our experiences, successes, failures and learnings from delivering Visual Studio Team Services (VSTS), a large scale service, on a cloud delivery cadence. My most recent post reflected on how cool it is to be able to deliver customer fixes within a day or two.
Today we shipped the second release candidate for TFS 2017.2. This post shares some info about this release.
Spring is hay season and it puts a significant strain on my managing the balance between work and farm. For the past several weeks, I’ve been stealing away every spare minute I can to cut, rake, bale and haul hay. I’ve hayed about 75 acres and that yields one heck of a lot of hay.
I want to share an experience that highlights why I am so proud of the organization I work in. The experience is expressed in the form of an email thread that I had this week. Times/timezones are a little whacky because there were 3 –
Yesterday, we released the first release candidate for TFS 2017 Update 2 (TFS 2017.2). This is a “go-live” release and is ready to be used in production environments. We’ve already installed it on 2 of our ~50 production TFS servers and it’s looking solid.
Sheesh, it’s another huge update this sprint. I expected a bit of a lull after all the work we put out along with the Build conference but things don’t seem to be slowing down much (or at least they’ve picked back up with a vengeance).