|
|
How to do a JETDSP release
This page is only of interest to developers on the JET site. It details how to make a release and get a full copy of the code onto Unix. Any volunteers to automate this?
Jetdsp can be released as a sav file from PC only. This is inconvenient but since the .sav file grew to be so large, only the PC version of the program writes it out without truncation.
To make a release and transfer the code and binary to Unix:
-
set the minor/major release number in options__harddefs
-
Make sure your JETNET username is in the JET_CATS local group releasersJETDSP (this is the case for the authors on the project at the time of writing).
-
Install WinZip or equivalent
-
Current version of IDL is 5.3, which you need on your PC.
-
Map a drive (Q:, say) to \\catsserver\jetdsp$
-
Open the archive Q:\jetdsp.ZIP
-
Extract the contents to a local directory on your PC. (I guess this could alternatively be on q:)
-
Open Sourcesafe
-
Do a 'get latest' on the Data Analysis subtree into the local directory you just specified. This will overwrite the versions of the files that you just got out of the archive with the latest version from sourcesafe.
-
From WinZip, do a 'Freshen existing files on the whole archive. Make sure you don't just do this to one directory. Also, don't do an 'Update (and Add)': this will add all files into the archive, including a load of redundant ones.
-
Add any extra files that have appeared in the program to the WinZip archive.
-
Close the archive.
You now have the latest files on your PC and an archive of the code body for transfer elsewhere. To transfer this to Unix:
-
Copy Q:\jetdsp.ZIP as a binary to ~jetdsp on JAC.
-
Logon to user jetdsp
-
type 'unzip -a jetdsp.ZIP' at the Unix prompt
-
remove the version of the jetdsp directory under inprogress (after archiving if you want to save it)(but bear in mind that the reference copy is in SourceSafe).
-
move (mv) the jetdsp directory from under "Data Analysis" to inprogress
-
remove the "Data Analysis" directory
-
if this snapshot of the code corresponds to a proper release, then you should put a copy under 'safe' (together with its corresponding sav file, see below) in a date-named directory. We will age off these snapshots when we hit the jetdsp username filestore quota (so long as the JAC admins don't read this first). These are just snapshots for quick backtracking and debugging purposes: I don't want to set up a proper CVS repository until we commit to using that full time, because running two source code stores might lead to divergence.
To make a proper binary release:
-
set up your PC environment so that it holds the latest version of the source code of the PPF and JPF clients. These are on JAC under /usr/local/idl. Make sure the IDL path on your PC picks these up or else the build will not work.
-
Check that JETRDAIDL.dll comes up when you type 'help, /dlm' at the IDL prompt on your PC. If it doesn't, install the RDA client.
-
Start IDL on your PC and type @build_jetdsp at the prompt
-
type "save, /routines, filename='x:\jetdsp.sav'" at the prompt, where X: is a destination of your choosing
-
copy jetdsp.sav to: ~jetdsp/inprogress/jetdsp on JAC, and to a new directory under ~jetdsp/release corresponding to this version
-
make a new 'source' soft link from this new release directory
-
break and re-make the 'next' soft link
-
test and then tell the JAC administrators where the new version is.
-
Solaris release requires the same binary, but is under review, and the next one will probably be by su.
|
