|
|
In order to ease the software update transition for users, we've developed a two-phase process for installing new software versions on Socrates. This is to ensure that users have time to test the new versions and make any modifications to scripts or programs that depend on the software being updated.
In the first phase, software is installed and set up to run as '< product_exec>.new'. This allows users to test the new version and make any modifications necessary to their scripts or programs. It also gives the Socrates Team and users a chance to test programs for bugs.
After approximately two weeks, we move to the second phase. We now move the previous version of the software to '< product_exec>.old' so that the previous version will still be available for users who depend on it. The new version will become the production version and the '< product_exec>' gets moved from '< product_exec>.new'. Finally, the previous old version gets removed and is no longer available.
If you run into any problems with new, production, or old versions of any software package on Socrates, please contact socrates_consult@berkeley.edu . The Socrates software naming convention is summarized in the table below.
| < product_exec>.new | New test version of product. |
| < product_exec> | Stable production version of product. |
| < product_exec>.old | Most recent back version of product. |
Please send comments to: calweb_consult@berkeley.edu.
For additional questions, see Questions.
Last updated 23 July 1998.