Visual Studio Team Foundation Server Branching and Merging Guide - v2 - For Visual Studio 11
"Welcome to the BETA of the Branching and Merging Guide preview
As this is a BETA release and the quality bar for the final Release has not been achieved, we value your candid feedback and recommend that you do not use or deploy these BETA artifacts in a production environment.
Quality-Bar Details
Known Issues / Bugs
- Documentation has been reviewed by Visual Studio ALM Rangers
- Documentation has not been through an independent technical review
- Documentation has been reviewed by the quality and recording team
- All critical bugs have been resolved
- Chance for grammar and typos.
- Chance for some redundancy in the guidance, guidance may be pruned for efficiency
- Chance for diagrams to mismatch with guidance topics
- Missing Features
- We are adding more cheatsheets for plans such as feature and code promotion
- We are adding additional Sharing scenarios and topics such as File linking, NUGET, Project and File References
- We are adding the FAQ section
- We are adding “How do I” Video(s)
- We are adding a HOL around Sharing Resources
- Each main area of the guidance will likely be streamlined, various new scenarios addressed
..."
Here's a snap of the one current HOL, "Branching & Merging, Local Workspaces, Diff and Merge"
And a snap of the Guide and cheatsheets;
Related Past Post XRef:
Visual Studio TFS Branching Guide 2010, aka Team Foundation Server Branching Guide III, released (by guess who? Yep,the ALM Rangers…)
Team Foundation Server Branching Guidance v2 Released
Branching Guidance on CodePlex
No comments:
Post a Comment
NOTE: Anonymous Commenting has been turned off for a while... The comment spammers are just killing me...
ALL comments are moderated. I will review every comment before it will appear on the blog.
Your comment WILL NOT APPEAR UNTIL I approve it. This may take some hours...
I reserve, and will use, the right to not approve ANY comment for ANY reason. I will not usually, but if it's off topic, spam (or even close to spam-like), inflammatory, mean, etc, etc, well... then...
Please see my comment policy for more information if you are interested.
Thanks,
Greg
PS. I am proactively moderating comments. Your comment WILL NOT APPEAR UNTIL I approve it. This may take some hours...