Today the Git community disclosed an issue in Git that, in the worst case, could allow a developer’s machine to be taken over. This is an issue that manifests across much of the Git ecosystem and is not unique to Microsoft’s Git implementation or to Windows.
I mentioned this in my post on the sprint 75 deployment and I wanted to include a video but it wasn’t ready. Now it is and I want to share it. Keep in mind that the deployment is still in progress so it may not be available in your account yet.
This week we are deploying our sprint 75 results. You can read details on the VS Online release notes.
For whatever confluence of reasons, a lot of things came together in this sprint an there’s a ton of new stuff that I think you will like.
We are always working on ways to communicate more effectively with customers about what we have done, what people like and don’t like, what they want, what we’re planning, etc. A year or so ago we added a Features Timeline page to our News section of visualstudio.com as one step in that journey.
I’m excited to announce our acquisition of HockeyApp – the next step in our journey to turn Application Insights into the best tool in the world for helping you get insight into your applications. With HockeyApp we add great support for mobile devices,
Earlier this year, we started a process of reviewing our pricing and licensing for Team Foundation Server and Visual Studio Online. Our intent was to review all of the customer feedback we’ve received to look for changes that would simplify purchasing and make it more affordable for teams to include everyone in the broader organization who needs to interact with the development team.
This week we are rolling out the sprint 74 updates to VS Online. You can read details about the features on the service news page.
There’s nothing huge here. After the larger announcements we made at Connect(); in November, we’re back to iterating on and improving capabilities more incrementally.
Just Friday, the week before, I was speaking to Buck about the incident we had the previous week and expressing a strong desire to avoid another incident anytime soon. We agreed to postpone the VS Online deployment so that we didn’t have to rush it in a short holiday week and we could ensure that everyone needed was on hand in case something went wrong.