Your organization should create a common source code repository that both your developers and TMA Resources’ developers can use for development work.
TMA Resources recommends using Subversion as your source control software, however, TMA Resources has no service agreements or commitments with Subversion. Any unknown or upcoming issues with Subversion, or any other source control software, is a potential risk. The source control software must be installed on all developer’s machines (both your organization’s developers and TMA Resources’).
If a programmer needs to work on a file, the file should be checked out and locked prior to beginning any work. If a file is already checked out, the programmer must wait until after the file has been checked back in prior to beginning work (optionally, the programmer can merge changes to the file at a later time).
Coordination should be established to ensure there is not too much waiting for programmers on either side to check in their changes.
If either TMA Resources’ developers or one of your organization’s developers are going to work on a base file or code (xml file, stored procedure, function, etc.) and the file has not been customized before, the developer should check the code into your repository, then check out the file prior to making any customizations.