Another purely technical post on TFS...
The scenario
We wish to migrate code between branches that do not have a
branch/merge relationship, in order to expedite urgent changes being made by a
project team, without disrupting on-going BAU development work.
Sample branch hierachy/strategy
Imagine the following branching strategy in TFS (visible by connecting to TFS via Visual Studio 2010 or 2012):
Essentially you have a "DEV" branch, which has a "QA" branch, which in turn has a "PROD" branch. DEV is the branch that you would be using for BAU development. As a piece of development matures, you move it into QA, where it is tested by your internal QA team. There may be further changes made in DEV that are moved into the QA branch as the QA team pick up issues. Once the QA team are happy with a packaged of changes, they will move them into PROD, which is essentially the hand-over to the customer. The PROD branch represents the software that the customer has.
Mo…
Comments
Post a Comment