What do you like and dislike with the latest Version Control guidance?

We are investigating the next phase of the Version Control (ex Branching and Merging) Guidance, potential integration with MSDN, using other delivery channels and accepting contributions from the ALM community.

current portfolio

• v3.2 - Version Control Guidance 
  • Guidance: Branching strategies, TFVC Gems, Dependency Management with NuGet, and Git for TFVC Users.
  • Quick Reference Posters: TFVC and Git, Git Workflows, and VS consideration aid for TFVC and Git.
    
• Research & Feedback posts
  • Git for the TFVC User – Workflow Investigations Part 1: Making Changes
  • Git for the TFVC User – Workflow Investigations Part 2: Reviewing Changes (No Conflicts)
  • Git for the TFVC User – Workflow Investigations Part 3: Reviewing Changes (With Conflicts)
  • Git for the TFVC User – Workflow Investigations Part 4: Converting a TFVC repository
• MSDN Magazine Articles
  • Team Foundation Server: Visual Studio Team Foundation Server Branching and Merging Guidance
  • Version Control in the TFS Client Object Model
  • Using Feature Toggles as an Alternative to Development or Feature Branches

We would appreciate if you could review the latest guidance and give us candid feedback on content and delivery format.

If you could pin    three (3) features on our backlog, what would they be?

please share candid feedback

We can’t wait to hear from you. Here are some ways to connect with us:

• Add a comment below.
• Contact us on our blog.