Menu
I have my TFS 2010 structure as follows:
ProjectCollectionA
..trunk
....Dev (this is a branch)
...Website1(these are folders)
...Website2
....Release(this is a branch)
...Website1(these are folders)
...Website2
For whatever reason, I have dev and release as Branches and Website1, Website2 as Folders. My question is should I be having dev and release as folders and Website1 and Website2 as branches? Does that make more sense? What is the best practice here? Any advantages or disadvantages going one way or other? Thanks for the help
913
With TFS, there are several ways that you can handle releases. You can tag/label each release branch or bug fix. But the relationship between release branches and the release is not always clear. Teams need to create a naming scheme and define a TFS branching strategy to help document the flow of change.
You can prefix the branch you want to create with the folder name or branch type you want. For example you can put a feature branch into a feature folder by making the branch name. This is an example of how the tree will look.
There's a very comprehensive guide here from the ALM Rangers that explains the different branching practices in TFS.
If Website 1 and Website 2 are related applications within the same overall solution (not VS solution) or if there are any dependencies between the two Websites, then this (IMO) is the best approach. If they are two completely unrelated projects with isolated code bases, I would seperate it into two TFS Projects.
It's hard to decide on a correct branching pattern for someone without knowing the full ins and outs of thier business practices. What we do here, might not work for you (Actually, what we do we probably shouldn't).
102
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
