Everything you want to know about Visual Studio ALM and Farming
Brian Harry is a Microsoft Technical Fellow working as the Product Unit Manager for Team Foundation Server. Learn more about Brian.
More videos »
Jeff Beehler wrote a good post on what it means to "go-live" on Beta 2 and steps you need to take in order to get support. The only thing I'd add to his post is a little tempering of "high standards of quality". I want everyone to understand that it is a Beta. If you are going to go live on it, you need to be prepared to live with some bugs. Last I checked the TFS product still has about 300 known bugs to fix after Beta 2 and we are doing another test pass right now that will yield more bugs to fix.
Just yesterday we were having a discussion with our MVPs about a bug where bulk saving work items (like from Excel) where there are multiple different types of work items in the list will cause gaps in the assigned work item IDs. It's annoying to see your work items numbered 1, 3, 7, 8, 10, etc instead of 1, 2, 3, 4, 5 but causes no real harm. It's a known bug and will be fixed before release. However there was an interesting discussion about how this kind of thing could cause some customers to "lose confidence" in the Beta.
My feedback is if annoying things like this will cause you much consternation, don't go live on the Beta. There's a lot of cool stuff in the Beta and I believe that you'll benefit tremendously from using it but be prepared to live with working around or turning a blind eye to some defects. It is a Beta, after all, not a released product. We'll have worked out the remaining issues by the time we release. The Beta is an opportunity for you to help make sure that the product will work very smoothly in your environment and your scenarios by the time we are done.