Attendance: Joanne Bogart, Toby Burnett, Richard Dubois, Marco Frailis, Riccardo Giannitrapani, Heather Kelly, Michael Kuss, Hans Mayer-Hasselwander, Leon Rochester, Tracy Usher, Karl Young
Karl provided a demonstration of the release manager as it now stands. There are 3 routines, all of which reside in $GLASTROOT/ground/scripts/ReleaseManager: testPack.pl - tests a package against an existing checkout package. The test is performed using the package's supplied test routine. The checkout package must already exist in the SLAC release area. One can test the HEAD of a package, by using "head" as the version tag. USAGE: testPack.pl <package> <version tag> <checkout package> <version tag> OUTPUT: an e-mail to the user (SLAC e-mail) denoting success or failure. It was requested that more information be provided in the e-mail message.
testCheckPack.pl - tests a checkout package, using the package's supplied test routine. Currently writes to SLAC AFS space - general users should not use this script until it has been officially released by Karl. This is expected by next week. USAGE: testCheckPack.pl <checkout package> <version tag>
genDoc.pl - generates Doxygen output for a checkout package. This script only handles checkout packages. Karl will modify to handle simple packages. This is the script that is run every night, searching for new tags of checkout packages and running Doxygen on the files. The output HTML files are dumped into SLAC AFS space. Hence, at this time, general users should not attempt to use this script until Karl releases it. USAGE: genDoc.pl <checkout package> <version tag>
General Comments: The .pl extensions will be removed from the script names, per Toby's request.
It was noted that none of the existing packages have a test program that conforms to our stated convention of: test_<package name> Package owners should go back over their packages and renamed their test routines appropriately.
Can we handle multiple tests per package?
Proposal: Release Manger Client Server Model
RM server sets up the environment, using a standard linux configuration. Richard requested that the user could query the release manager to determine what the "standard" configuration consists of. The RM client resides on the user's machine and interacts with the RM server. The executable will be called grm (Glast Release Manager).
**** I think my brain was off for much of Karl's intro to his proposal...so feel free to fix that ****
The client server version of the RM will be made available in 2 weeks.
Windows testing is next on the to do list, once the release manager for linux is setup and running.