Stephen's corner of the Web

So at AECL we use MKS Source Integrity for source control of our projects. At least in the branch I am in we do. It is a system that uses the RCS format as a backend data store, similar to CVS and Perforce among others. I just started to use it today and as of yet do not have write access to the repository. However, I already know I will not like it. MKS has a concept where you can check out a sandbox of the project. Ther are several types of sandboxes, a Normal Sandbox which is a copy of the Head of the repository. Then there is a Variant Sandbox which is a copy that creates a branch. Finally there is a final kind of sandbox which is used to generate a build environment, but only from a tagged project revision. So, after you create this sandbox to work in, you have a copy of the files, but you have not actually checked them out yet. Instead, you have to check out individual files to actually work on, which places a repository lock on that file. So while you have a file checked out, no one else can work on it. What a pile of crap source control system...