I value tools that help manage the branch for my team. We are working on a commercial product, so the tools should be carefully selected to handle several issues, possible fixes in older versions, etc.
Basically, I want to achieve what git -flow allows .
But since we already use TFS (2012 today, but the 2013 update is in the pipe) with Visual Studio 2012 (but we didn’t use branches before), I would like to stick to the full MS product line.
Then I searched for guidance and I found this software. I saw a short webcast of the V Branch Extension Quick Tour on Channel 9 showing the tool. But it only covers the creation of the original structure. How about everyday work?
Let's say I finished work on a feature or fix. How can I help a developer merge with the correct branch? How can I easily read the idea of work?
The tools say "automate the branch task in the ALM Rangers branch guide" ... but I don't see any menu that can do this. The only thing I see is the Create Initial Structure menu.
Did I miss something? Is there any other resource that can help me?
I like GIT ... I believe in its strong branching features. But I feel that the git experience in VS 2012 is terrible ... so I would like to enable TFS.
Since my team (including myself) is not mature in branch management, I have to keep things as simple as possible, so any advice is welcome.
source
share