When would I use a Branch for Developer Scenario?

Question: Any opinion on branch per developer approach? This is the first time I have come across it someplace and feel that there’s just no reason too. I’ve been through the branching guidance and even use your article in MSDN magazine from earlier this year as reference. The development teams are offshore and not always…

3

VS ALM Rangers Branching Guidance–Shared Code and Dependency Management

As we begin planning the next release of the branching guidance, a top priority is to address how to manage shared code dependencies (the Dependency Repository / Shared Code issue). The newly release Build Customization Guide (now available for download from Codeplex) begins to address this issue, primarily from a build perspective. For the Branching…


VS ALM Rangers Branching Guidance – Ideas for the next release.

I think most would agree that the Rangers Team has already done a fantastic job with the Rangers Branching Guidance. This is not meant to be a self-serving comment, since the current branching guidance is the result of the hard work of many others in addition to myself. For the past couple of years I…

4

Isolating and Integrating Parallel Feature Teams working on Separate Overlapping Releases

Customer scenario: How should I isolate (and integrate) changes when working with: 3 parallel efforts (two parallel development efforts, working on separate releases of the product and production support) Production(version 2.0) with the need to issue hotfixes on then current production version Development Team 1, working on the next minor (Feature) release (version 2.1). New…


Branching–Sprint is Done, Some Features Are Not

Download the latest VS ALM Rangers Branching Guidance Here: http://tfsbranchingguideiii.codeplex.com/  Background – I keep getting this question: I have a quick question for you on branching in Scrum and feature management.  My client is using Scrum and if we look at the branching structure all sprints branch off of main.  I noticed in your blog…


Branching for Scrum

This article presents a perspective on Source Control Management (SCM) using Team Foundation Server (TFS) with Scrum projects. Although I start with a short overview of Scrum to lay the foundation for the concepts, the essence of this article is to present TFS Branching Concepts for Scrum projects, large and small. This article is an…

5

Parallel Feature Teams working on multiple releases in development. Monthly releases to production.

I recently received a question from a customer who is dealing with the need to support multiple feature teams working on multiple releases in development. They asked how to structure branching to support this environment. Background: My company is, for all practical purposes, a dot com. We have a single production website used by all…

3

Branching for Agile Development

I was recently asked a question based on the following presentation from Google: How Google Speeds Up The Chrome Release Cycle (Slideshow) The main part of the article that interests me is the following: "Anthony LaForge, the technical program manager at Google overseeing Chrome development, created this presentation to explain how Chrome’s development cycles work….

2

New article on Ranger’s Branching in upcoming MSDN Magazine.

After a few years hiatus, i am returning to the world of *published author*. My next article will be published in the February 2011 issue of MSDN Magazine (http://msdn.microsoft.com/en-us/magazine/default.aspx ) The topic will be *Visual Studio ALM Rangers Branching Guidance for Team Foundation Server (TFS) Team Projects*. My co-author is Willy-Peter Schaub, also on the…

1

Basic Branch Plan–Where to fix a bug in my release?

Question from Customer: In the single team branch, once a release is done and if a bug is reported are we supposed to fix the bug in the Main branch and forward integrate back to the DEV branch Response: Separating Development from Release, bug fixing a shipped release is a Release question, not a question…