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…

0

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

Renaming a branch with shelvesets

Caution: Renaming branches in TFS 2010 is a very bad idea unless you follow a very specific set of steps: http://blogs.msdn.com/b/chandrur/archive/2010/06/09/renaming-branches-in-tfs-2010.aspx. In TFS 2010, Unshelve will follow pending renames but it will not follow renames committed between when the shelveset was created and the current workspace version.  Here are two cases. Case 1: In some…

0

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…

0

How do I create bug fixes for EVERY version of a product EVER released

A customer asks the following question: “We are building factory machine. New machines are usually delivered with the current stable software version. We don’t do regular updates because our customers prefer stability over new features. After reading the Rangers Branching Guide I have some questions. I understand the need for the main and the development…

0

How TFS stores files and calculated deltas on versioned files

  Recently I got a request from a customer to help them estimate the expected size of a proposed TFS 2010 environment, and to help them estimate a ten-year growth prediction. This customer was focusing narrowly on the overhead required to create a new branch. This customer was asking "how much database space is needed…

5

Where do I fix a production defect?

Question from a customer of the Rangers Branching Guidance (http://tfsbranchingguideiii.codeplex.com ) “My company has a major release every 3 months.  In between major releases we have monthly maintenance releases. (Similar to the "Advanced Branching Plan") Our monthly release usually is limited to high priority bugs based on customer complaints and business needs. Scenario: Lets say…

1

Project Dependencies will break with branching if not done properly

In the February 2011 issue of MSDN Magazine, I wrote an article on Shared Code (or code dependencies as some call it). Often I see a common problem with relative references to dependent assemblies or projects. If relative references are not created properly for a solution that is branched, the relative references may break. Since…

1

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…

0