Submitting Software

This section outlines the steps involved in submitting updates to the SNOMAN. The term `we' below refers to the coordinating site team.

1. We suggest that the contributor briefly discusses how the new code will interface to the rest of the code BEFORE starting work on it.

2. When the work is complete, we will issue a development release so that the contributor can install his code into the current version of SNOMAN.

3. The contributor must test out the update. At a very minimum they must run the complete suite of run_*.cmd files (the tool: RUN_STANDARD_JOBS, makes this a trivial task to perform) and confirm that the code does not crash and that their contribution is working. If appropriate a new n-tuple should be constructed to demonstrate this.

4. The code and documentation is then sent to us. We reserve the right to refuse it if:-
   • Step 3) has taken too long and that there have been major conflicting updates since the development release had been made.

   • There is a serious breach of the coding rules laid down in the Programmer's Manual.

   • There is inadequate documentation. Normally updates should include contributions to the User Manual and the Companion.