Hello,
is there a technical limitation on how many Code-Branches a TFS Server can handle? I am asking that because someone in our company suggested to create a _seperate branch_ for every (!) bug we find in our product and give that branch the name of the bug, so
that they can be easily related. However, this means we may be creating 10000s of branches during the products lifecycle. I understood that there is probably no problem with the harddisk-space on TFS because it only needs space for the changes.
But i dislike that approach because i think:
- there may be other bottlenecks in VS / TFS dealing with so many branches
- we will spend to much time for foward / backward merging of code
- i expect the VS Source Control explorer to slow down
What is your opinion on that approach ?
Regards,
Holger