New Ranger Project – Branching Guidance 2010 v2

We are please to announce a sequel to our blockbuster project


The abstract below has been copied “as is” from Bijan’s announcement email:

We are planning the fourth release of Rangers Branching Guidance. The last release of Rangers Branching Guidance 2010 was extremely well received. It consistently ranks as the third most popular download of all the active Rangers projects on CodePlex and surpassed the 100K download with three releases a few months ago. We also have an active discussion forum on CodePlex. Based on feedback we have received from the community and ideas from the Rangers teams, we would like to begin the next round.

We don’t anticipate any major rewriting of this successful guidance but some ideas to add best practice guidance for more complex scenarios:

  • Feature team development
  • Parallel development support for multiple versions
  • Approaches for Sharing Common Code (shared source, shared binaries, etc.)
  • How to improve and support development activities in other ALM areas like DB dev and architecture with branching techniques

As the guidance matures, we also want to improve the guidance around process and branching strategy best practices.

We also want to review all of the current guidance to ensure it is internally consistent and reflects the current thinking of the Rangers team.

We are actively seeking additional ideas for improving and extending the guidance. Please forward any ideas you may have along to the team.

As usual and in compliance with Ranger quality standards, the package will include white paper, deck, hands-on labs, custom VM, and a pair of TechReady13 session and HOL.

Core Team

We have a phenomenal core team made up of Bill Heys (shown below), Oliver Hilgers, Neno Loje and Bijan Javidi.

Comments (4)

  1. Allen Feinberg says:

    I'm really looking forward to a feature builder HOLs running directly inside of Visual Studio for training purposes.

  2. Stacy Cheatam says:

    Is this available?

  3. Stacy … No, we announced the start of the project, which is an opportunity for the community to give feedback to the team as to what is important to consider for the guidance. Keep an eye on our monthly flashes (…/highlights) which included a status update on all active projecs or the project tag (…/tfsbg) for ongoing news. When we ship early BETAs or the final product, we will blog proactively 🙂

  4. Allen … are you refering to the FB HOLs style we introduced with the Architecture Tooling Guidace v2.1? (…/architecture-tooling-guidance-version-2-1-abe-is-available.aspx) If yes, then I will discuss the option of introducing these labs with Bill (dev lead).

Skip to main content