Inter-operability with current development tools used in the project. Code only needs to be checked against the project compiler, however, as noted above. A designated group will be responsible for ensuring a clean build on each secondary system, and are expected to resolve the overwhelming majority of any compiler or syntax support issues on these systems. Other developers may however be consulted for assistance or advice if changes need to be made to their code, particularly if these changes are subtle. Compiler defects need to be recorded for reference by other developers, and submitted to the vendor for correction.
All code is under revision control on each master.
Files should be locked for the minimum period of time consistent with completing the work required. This includes making changes in all other parts of the system which depend on the code which has been modified, for all except contributed code. In rare circumstances, check-in's which require multiple days and may break the system will be scheduled after consultation with the project. Code which breaks the daily build inconveniences other developers and delays applications delivery. Descriptive, complete and readable.