Laserfiche WebLink
CRDSS <br />TASK MEMORANDUM 1.05-20 <br />Study of System Integration Issues <br />Revision Control - Use of in CRDSS <br />1.0 ISSUE <br />Files that are implemented for the CRDSS must be maintained under revision control. This allows <br />changes to the code to be tracked and prevents multiple developers from corrupting a file by working <br />on it at the same time. Placing code under revision control also allows a version of the system to be <br />retrieved for any date during the life of the project. The original version of existing software can be <br />retrieved, which is important when trying to maintain a link to the original author of the code (e.g., <br />the USBR and its CRSM). The use of revision control in the CRDSS requires that the following <br />issues be addressed: <br />What method of revision control will be used? <br />? <br />What types of files can be stored under revision control? <br />? <br />What procedure will be used to place existing code under revision control? <br />? <br />What procedure will be used to place new code under revision control? <br />? <br />What procedure will be used to edit a file that is under revision control? <br />? <br />What procedure will be used to compile a program that is under revision control? <br />? <br />2.0 DISCUSSION/ANALYSIS <br />A revision is an identifier (e.g., 1.1.2) associated with a file. Each revision consists of changes from <br />the previous file version. Revision control therefore concentrates on managing the changes to <br />different versions of files. <br />A version number is generally associated with a product that is bigger than a single file (e.g., CRDSS <br />version 1.0). The files that comprise a product typically have different revision numbers for the <br />same product version. For example, ?program? version 2.3 may be composed of ?file1? revision 1.2, <br />?file2? revision 4.5, etc. This occurs because it is convenient to know which files are static from one <br />product version to another. Revision control software allows the developer to set the revision <br />number for a file to any number; however, setting all files for a product version to have the same <br />revision numbers would indicate that all of the files have recently been changed as part of that <br />product version, but this may not be true. <br />Revision control software may also allow a revision to be tagged with a ?label? and with comments. <br />This mechanism can more effectively be used to identify a program's version as it applies to the <br />individual files within a program. For example, at the time when ?CRDSS pr ototype version 1.0? is <br />1 <br />A275 01.08.95 1.05-20 Malers <br />