I've been in Orlando this week, speaking at SQL Connections and have been derelict in my blogging duties, especially with regard to VSTS.

• Microsoft announced on Monday that they had acquired DevBiz (the company that produces TeamPlain), which has been the leader in browser-based access to Team Foundation Server, further boosting cross-platform access (and adoption). TeamPlain Web Access also enables a peripheral team member to browse project information and manipulate work items, source code, etc. I believe the new, official name will become "Microsoft Visual Studio Team System Web Access" (another mouthful). This acquisition also means that we will get to use TeamPlain for FREE (assuming we have a proper client access license for TFS). Read more about the acquisition on Brian Harry's blog and Microsoft PressPass.
  
  
• Microsoft published their Visual Studio Team System "Future Releases" roadmap, even beyond Orcas. So now, we can all speak the words "Rosario" in public. Rosario is the codename for the version of VSTS beyond Orcas. The roadmap is very thorough, even listing service packs and power tools, so you know exactly what delivery vehicle your feature or fix will be arriving in.
  
  
• Gert Drapers (the data dude) announced Service Release (SR) 1 for VSTS Edition for Database Professionals. He says that it's "in the works" and will be published sometime in Q2 of 2007 (let's hope April). He lists a few of the fixes and features that will be in the SR in a recent blog posting.
  
  
• Yesterday, Microsoft announced that unit testing will become a feature of the Professional edition of Visual Studio Orcas. This has been a passionately-requested feature by everyone in the world not running Dev, Test, or Team Suite editions. Finally, everyone who has Professional edition and up will be able to write and run unit tests. What about code coverage, that's still a question.
  
  
• The Patterns and Practices team has released updated prescriptive guidance on VSTS. JD Meiers lists many of the improvements on a blog post and you can find the guidance itself on CodePlex.
  
  
• Speaking of guidance, Microsoft recently published a 40-page branching guidance document which does a very good job of explaing branching and merging strategies for various size teams.