Transcript [email protected] @mariorod1 source control models centralized OR distributed centralized scales to large code bases.

[email protected]
@mariorod1
source control models
centralized OR distributed
centralized scales to large code bases
distributed best in class offline experience
Check-in
Check-out
Strengths
Check-in
Check-out
Best for
•
Scales to very large codebases
•
Large integrated codebases
•
Fine level permission control
•
•
Allows usage monitoring
Control and auditability over
source code down to the file level
Strengths
Check-in
Check-out
Best for
•
Scales to very large codebases
•
Large integrated codebases
•
Fine level permission control
•
•
Allows usage monitoring
Control and auditability over
source code down to the file level
•
Offline editing support
•
Medium-sized integrated
codebases
•
Easy to edit files outside Visual
Studio or Eclipse
•
A balance of fine-grained control
with reduced friction
•
•
Full offline experience
Complete repository with
portable history
Simplified branching model
•
Modular codebases
•
Integrating with open source
•
Highly distributed teams
•
we need to embrace DVCS
Git OR Mercurial
Team Foundation Server / Service
Project 1
3rd Party
Project 2
Local
Repo
3rd Party
Other
Remote
Git Repo
User: …. TFS sucks
Us: We are sorry ... Why do you feel that way?
User: Because [reasons] … is a centralized version control product
Us: We are supporting Git
User: I love TFS!
Us: We love you too
Git
(hosted by TFS)
decision at the project level
 Version control (TFVC or Git)
 Comment on changesets & commits New!
 Work item tracking and tagging
 Team rooms New!
 Agile planning tools
 Feedback Management
 Agile Portfolio Management* New!
 Build*
 Web-based test case management*
 Load testing* New!
* Capability in preview – limits may apply. Authoring load tests requires Visual Studio Ultimate 2013 Preview.