Office hours are back!
Branching strategy is one of the most important aspects of TFS deployment. The right strategy can lead to optimized team cooperation, increased productivity and a successful adoption. On the other hand, a bad branching strategy can cause frustrations, damage production and derail TFS adoption in an organization. We have therefore put a lot of effort in creating a set of practical guidance to educate our customers and partners and support their VSTS adoption efforts.
The 2nd major release of the TFS Branching Guide has been posted HERE on Codeplex.
An important goal for this release is to go beyond just publishing this guide and create a living and ticking community. With your help and contribution, we would like to incrementally grow our libraries for scenarios, Q&As and labs. If for example, you are not able to find a suitable scenario for your branching needs, we encourage you to post a request for a new scenario. This will trigger a small process with a team which owns the development of the new scenario with your cooperation. Your name will then appear as the coauthor of that scenario.
Release 2.0 scenarios
The following scenarios are included in this release:
Why the 2nd release?
Since the first release, we have received lots of feedback and change requests. Most feedback indicated a desire for a more practical approach to branching compared to the first release which is more theoretical. With that in mind, we decided to reduce the conceptual part and focus on branching practices with Team Foundation Server.
What is in the package?
Again, it can be downloaded here: http://www.codeplex.com/TFSBranchingGuideII
If you’ve ever wondered just how much effect a TFS proxy will have on your TFS performance, the article linked below might help give you some perspective.
I find this information to be very helpful when discussion TFS performance with customers. Some seem to feel that it’s imperative that a proxy be installed in their environment (this seems to be due to experience with past SCM systems (Rational) that virtually required their multi-site setup to be implemented for remote teams).
I highly encourage you to take a look at this article, which addresses the following points:
Here’s the article link: http://www.codeproject.com/KB/architecture/TFSProxyEfficiencyTesting.aspx
I won’t duplicate content too much, but there are 4 updated virtual images for you to play with. They expire on 12/31/2009.
Here’s the link to the announcement: http://www.pluralsight.com/community/blogs/brian/archive/2008/12/24/happy-holidays-and-look-what-santa-s-brought.aspx