Willy's Reflections - Visual Studio ALM Rangers

| Willy-Peter Schaub | Visual Studio ALM Rangers | In search of IT simplicity, quality and tranquility |

TFS Integration Tools – Why does guidance state that TFS supports directory level branching? Is this an error?

TFS Integration Tools – Why does guidance state that TFS supports directory level branching? Is this an error?

  • Comments 2

We received the following question

On the Branching section of the "TFS Integration Platform - Subversion Migration Guidance" document, it is stated "Perforce and Clear case, for example, are based on file level branching, whereas TFS is based on directory level branching". I am able to branch a single file in TFS, so is this an error in the documentation or do they mean something else?

Response

We are busy updating the readiness package and associated documentation to clarify the statement. File branching is supported in Team Foundation Server, but the best practice is to branch at the folder level, or better yet, at the branch level. Clearcase has a different model that results in individual file branching, or what we would call sparse branching. It is critical to understand Team Foundation Server branching (see http://tfsbranchingguideiii.codeplex.com/ for more information) and the guidance in order to formulate the best migration plan.

What to avoid …

Avoid complex branching structures, such as the following:
DSC00288

  • PBI: As a CM I would like to keep the branches to a minimum so that Willy will get his neck red in the sun... :)

  • LOL :)

Page 1 of 1 (2 items)
Leave a Comment
  • Please add 1 and 8 and type the answer here:
  • Post