Laserfiche WebLink
make <br />The command uses the notation $(...) to indicate the value of a variable that was previously <br />defined. The value of would be blank if the current library is to be used, or would <br />DMILIB_DATE <br />contain a specific date. Note that a different date could potentially be specified for each library. <br />Each library is documented with ?release notes? so that developers know which version to use. <br />These release notes only describe the changes in the library from the previous version. For example: <br />The GetDiversion function now has a return code of <br />ERROR_CANNOT_FIND if the diversion cannot be located in the <br />database. <br />This type of documentation requires developers to track work that is being done, not only using <br />revision control for the source code, but in a development chronology. Release notes are E-mailed to <br />developers and also exist on the system in a public area so that release notes can be printed at any <br />time by developers. Old library versions are removed from the system as the prototypes move <br />forward (but still exist on backup tapes). <br />Initial development will consist of writing new library code (e.g., the low-level DMI library) and <br />implementing existing libraries (e.g., public domain software). The low-level libraries that form the <br />foundation of much of the work in the CRDSS cannot hold up the development of the higher-level <br />applications. Consequently, the scheduling of work on the low-level routines must target the most <br />critical routines to be developed. After these routines are tested in a stand-alone mode, they are <br />released to developers in the form of a library, and can be used in other development efforts. It is <br />anticipated that initial release notes will mainly have comments like: <br />The following routines have been added to the DMI library: <br />GetDiversion <br />GetReservoir <br />See the man pages for these routines. <br />In other words, initial release notes announce new routines as they are developed so that these <br />routines can then be used by other developers. Note that simply adding a new routine to a library <br />does not require that a new dated library be released since none of the previous version's code has <br />been changed. <br />An effort is made to debug all code before it is released as a library. However, it is inevitable that <br />software bugs will creep into code. The release notes address bug fixes. E-mail is used extensively <br />to communicate between developers, so that bugs are corrected as quickly as possible. <br />Code that is part of a main program and that may not be in a library can be used to regenerate a <br />previous version of the application by retrieving the appropriate revision of files from the revision <br />control file. However, it is not anticipated that this will be necessary because continued development <br />of each application moves that application forward while depending on dated libraries. Improvement <br />of an application program affects only the main program and should not affect the development of <br />another application program. <br />5 <br />A275 01.08.95 1.05-22 Malers <br />