Laserfiche WebLink
Each revision of a source code routine should be a working routine (at least to the understanding of <br />the developer). This will prevent future confusion by ensuring that all revisions of a routine can be <br />extracted, compiled, and executed. <br />Revision Control Procedure for the CRDSS <br />rcson <br />Files should be placed under revision control using standard RCS or CVS commands or the <br />program developed for the CRDSS (a version of a script developed for SCCS by RTi). This is a <br />script that places a file under RCS control using appropriate options. After a file is under revision <br />rcsedit <br />control, it should be edited using the program (again, developed for the CRDSS from an RTi <br />SCCS script), RCS or CVS commands. As discussed previously, a new revision of a routine should <br />not be stored unless the routine is working as expected. <br />make <br />Rules for extracting RCS files for compiling using will be implemented by RTi. <br />3.0 CONCLUSIONS AND RECOMMENDATIONS <br />Revision control is an important tool that will help developers track software changes throughout the <br />life of the project. This allows file histories to be studied and therefore provides a way to validate <br />files with original sources. The storage of code changes involves storing only the differences <br />between files and not an entire copy of each file revision and therefore does not require extensive <br />additional disk space for software. The following recommendations are made related to using <br />revision control for the CRDSS: <br />The RCS method of revision control will be used for the CRDSS, but SCCS will continue <br />? <br />to be available to support data and software sources that may use SCCS. <br />All types of text files can be stored under revision control, including program source code, <br />? <br />configuration files, shell scripts, and documentation. <br />Existing code will be placed under revision control by storing the original source version as <br />? <br />the first version and then applying the current (modified) version as the first revision. The <br />procedure is described in the discussion section of this task memorandum. <br />A new file will be placed under revision control when the file contents are no longer being <br />? <br />expanded as part of the first version. Source code routines should be stored as a new <br />revision only after verifying that the routine functions as expected. <br />rcsedit <br />Files under revision control will be edited with the script or standard RCS and CVS <br />? <br />commands. <br />make make <br />Default rules for the program will be written to allow to automatically extract <br />? <br />a file from RCS during compiling. <br />8 <br />A275 01.08.95 1.05-20 Malers <br />