VSTS Source Code Control Services (Hatteras)
Hatteras is the source code control services component of Team Foundation.
These blogs discuss features of the new product
Branching and Merging
Merging covers both consolidating single files and propagating changes between branches. Because Hatteras uses non-locking concurrent checkout by default, the quality of the merge experience becomes very important.
A changeset is a snapshot of the database at a point in time, that allows you to restore exactly the workspace state you had last wednesday after you checked in what you thought was the final final fix of that bug...
Checkin and Checkout
Checkout has become 'Edit' which lines up with Visual Studio doing automatic checkouts when you click on a file to edit it.
Adding a file if a project folder doesn't exist causes the folder to be automatically added which is an improvement over SourceSafe which required a lot of hand labor to keep the folder structure aligned with your workspace.
SourceSafe employs the Exclusive checkout model which leads to predictable problems with breaking locks. Hatteras defaults to the non-locking Concurrent checkout model. The tradeoff for this is that merging must be done later.
The new source control system will have several client interfaces : A command line interface; integration with Visual Studio; and an API, written in .NET, for writing applications to perform source control operations.
Shelving allows you to park your work-in-progress on the server, safe from accidental deletion or a crash of your hard disc.
Working Folder Mapping and Cloaking
Working folders, more or less...
BurtonWiki is a community discussion of Visual Studio Team System. This is the SourceCodeControlSystem page authored by Stuart Celarier.