VSTS Ranger Branching Guidance – A Question on Separate Branches for each Change Request
Question from TFS Branching Guide 2.0 on Codeplex: “I am creating a new branch for each ‘Change Request’ that comes from the client – I love the idea of isolating the code this way. Do I have to create a new build definition for each, or am I missing something really straight forward? It seems like overkill for the smaller changes, but I want to keep a consistent set of rules – so if one change request gets a branch then so do all of them.” My Response: I think it may be overkill to isolate each customer change request into a separate branch.
Original post:
VSTS Ranger Branching Guidance – A Question on Separate Branches for each Change Request
