Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Minutes

Release Manager

Windows fix for EOL character is in.  Unfortunately due to a bug in external.scons the build on all oses is currently failing, so it has not been tested yet.

Navid will patch externals.scons and getting the builds going again.

Mac - AFS token issue still a problem.  Unix-admins have sent details to Navid.  The long and short of it is that we will continue to generate Mac builds by hand.

ST Builds

New facilities tag updates setting of environment variables to address case of TIMING_DIR.  If user has already set TIMING_DIR, that value is used, rather than setting it at runtime.  Tag has not yet been tested, due to the above mentioned external.scons bug.  Once facilities has been tested, Navid will run it by James Peachey to look over.  Then he'll pursue getting it into ST (and GR).  This should fix a number of failing unit tests.

Swig .in and .i files

Ongoing issue keeping the .in and .i files in synch for our swig builds.  Currently our CMT builds use the .in to generate a .i with hardcoded paths.  The SCons builds can use the parse the .i files in CVS directly.  Jim Chiang suggests we use a script to convert the .in to a .i file SCons, to alleviate the burden on developers to maintain two files.  Heather and Navid would prefer modifying the CMT builds to use the .i directly, and thus still allowing the developers to maintain one file.  Navid is looking into this possibility.  Alternatively we will containue to maintain the two files.  Richard asked why we would prefer not to use Jim's suggestion and convert the .in to .i file - Navid points out this would require modifcation to the SConscript files for all affected packages, and the introduction of a new builder to deal with the .in files.  As it stands, SCons (and obviously swig) recognize the .i files and deals with them appropriately.  Joanne suggests an email alert when an .in is updated in CVS.  Navid will look into that, as well as issuing a warning to the person doing the CVS commit, if the associated .i file is not updated as well.

Dumping RH9

No particular with dumping RH9 and SCons, though Navid points out it brings us closer to rhel5.  We need to consider how to handle f2c.

Heather asks if our source distributions and doxygen generation are only being done for the rh9_gcc32opt builds.  Navid confirms that is the case, though it is easy to change.  We agreed, to go ahead and update the RM, to use the rhel4 builds for source and doxygen.  In fact, as of this writing, Navid has already made the change for Doxygen.  This should have no impact on Chuck and the workbook, as the Doxygen is copied into an O/S indepedent location.

Emmanuel asked if we could discontinue creating rh9 externals when upgrades become necessary.  Heather answers, not quite yet, as we still officially support RH9.  However, test builds, such as python 2.6.2 need not be built for rh9.

Installer

Navid is in email discussion with Tony concerning the new web based installer.
RM front end
Joanne output for test programs
if SCons RM can look at CMT RM and modify its tables to set the appropriate flags
Windows and commonRootData and rootcint
VC9  send the output
set
CHS

N will notify B about upcmong update end of May
rebuilt fxRuby
still has teh same error
heprepcorba package responsible for launching fred, when not passing fred to ior file
if not pass it the ior file, FRED launches
v0r99 and v0r99a
question this summer get rid of rh9 rhel3 machines - if going to be upgrading external libraries

Agenda

  • Release Manager Status
    • Backend
      • Windows
      • Automatically notify package owners of build failures -- done, some suggestions from Toby
      • Any possibility of noting RM2 failures in RM1?
      • Mac -token issue
      •  
      • Other Issues?
  • rh9 need to dump by summer
  • Installer/  RMviewer /Tag Collector - Navid
    • Contact Tony
    • user releases are good to go
    • developer release status
    • Version 0.5 current test release
    • available for testing from ftp://ftp-glast.slac.stanford.edu/glast.u05/RMViewer/
    • status of current RM binary installs?
    • To Do List
      • Installer for Developer Releases
      • Contact Tony concerning web based installer
      • Tag Collecting
  • Front End - Karen

...