Minutes

Release Manager Backend

Everything is running except Windows.  Also, all builds are currently debug - Navid reports it would take about 50 - 100 new entries in MySQL to enable optimized builds.

Windows builds were working at one time by submitting jobs by hand to the windows LSF queue, but there was a problem with automation.  Perhaps a LSF submitter bug, but Navid needs to do some additional investigation.

64 bit builds:  Navid has started to receive feedback from those giving it a try.  Seems to have gone well and easily for those who try it out.

Concerning RHEL5 and Babar's plans, it is Richard's understanding that they will go to RHEL4 first.  He was be talking them again soon.  But that does bring up our need to close the loop on RHEL4 to make sure we can consistently run GR in RHEL4.  Final issue was associated with the G4 libraries requiring a rebuild on RHEL4, Heather will refresh her memory.  In addition, Richard later mentioned that FSW is planning to drop RHEL3 in a couple of months.

Installer

 User releases are now being automatically generated for the soon to come installer.  Zips (tgz) of the externals are available for all OSes except Mac.  Navid was looking into a little bug at the time of this meeting (which I believe has since been sorted out).  He's planning to make the user releases available via the RMviewer.  So ultimately there will be three methods for obtaining releases:  RMviewer, Tony's Java interface, and via the command line.  The command line option is Navid's lowest priority, as that mechanism is used primarily by those interested in automated installations, but he will get to it.

Release Manager Front End

Karen has updated RM2 on glast-ground is asking for additional comments.  Heather suggests sending around a note to corelist/softlist to trigger more interest (ditto for RMviewer).

RMViewer

The current version is 0.4.  Navid hopes to release a version 0.5 in the next few days.  This would include the updates for user releases, including providing a path to the files on u30.  Next up would be completion of the tag collector which is written but in need of debugging.

SCons

There is a more recent production release of SCons but there are no features or bug fixes that affect us.  Navid can install this newer version on AFS and we can migrate at will.

GoGui

Current release is 0.9.2   Not much to report, the recent cooling water outage hurt!

Windows on the to do list.  see next item

Windows Support

Joanne has been busy trying to learn about windows builds.  VS2008 is now installed.  She has been studying the schema used to describe the project files.   Extra attributes can be included and parsed (I think I missed the rest of this statement!)  Joanne is also considering the work done by Toby and Tracy for VS2005.  Joanne plans to start with the Microsoft builder which comes with SCons and then determine how to modify the builder for our purposes.  Then Joanne also needs to understand how this fits into our particular implementation of SCons usage. The solution files are ASCII, but they are a problem for another day.

stag

Minor updates coming, new release will then become available.  In the meantime, the current version is available on u05 for testing.

CHS

Jim Panetta tested and provided some tweaks that have been committed.  Heather asked when we could activate CHS builds in RM2?  Joanne pointed out that the version of FSW that is being used does not yet have a tag.  This includes new code from Owen.  Bryson offered to manufacture a version of FSW from a nightly build or from an upcoming candidate release.  There is a FSW meeting today where Bryson will inquire further.  Once that's in - Joanne has some changes to externals.scons for a group of libs that MOOT needs.

Maintenance annoyance soon to be fixed:  The various container packages (GR, ST, CHS) have their own copies of the SCons-specific files.  The plan is to have a symbolic link so we have only one copy in CVS
so we don't have to maintain those files separately.  Navid tried to do that last night and ran into a problem.  Those directories are out of synch right now - CHS has mod from Bryson concerning registering objects.  Navid needs to port that into the other copies of the SCons files in the other containers and then create the symlink.  In fact, the SConstruct files could possibly be common across containers.  There is a single line that defines the name of the container which would need to be handled elsewhere.

Bry asked about the timeline to move to SCons-only builds.  Heather did some hand-waving and all agreed it would be on the scale of months before we could completely ditch CMT.  The point of Bryson's question was the need to modify the scripts to setup the environment and perform installation.  That structure currently assumes CMT builds.

ST

g2c versus f2c  - according to Jim C and Eric Winter, the optimizers package has several dependencies with no C++ replacement available.  Possible to distribute f2c as a library ( or source ?? ), Eric had made such a suggestion at this week's software meeting.  See the GR section for further f2c discussion.

GR

Concerning f2c, Joanne did contact Jim C.  Joanne updated some code, and Jim also made some patches.  There was only one routine in GR that used f2c and there is a C++ replacement available.  There is tag that should do the right thing.  FluxSvc requirements file has some mention of f2c which we don't need any longer.  Navid asked if anyone seriously considered moving to g2c instead?  Joanne believes that was not an option.  g2c may lack a precise replacement for some of the routines we use, and on windows there may have been a requirement to have a fortran compiler available.

Emmanuel asked a general tagging question concerning moving tags.  For example in the tip package, a tag already exists.  Currently only the glast or glastrm accounts can move tags if necessary.  In this case, we agreed that only tags on SCons-specific files may be moved.  Tags on source code, may not.

Heather started to test the GlastRelease-v15r49 tag of GlastRelease-scons to try it out.  The updates to the SCons-specific files such as the SConscript files are at the head (as they should be), but also need to be tagged along the GlastRelease-v15r49 branch so that users will get those changes when doing a checkout on GlastRelease-v15r49.  Emmanuel is aware of the situation, and Navid has a script that can apply the branch tag to those files.  Heather's testing is pending that update to the GlastReleasev15r49 branch.

Navid and Joanne have further discussed creating a centralized lib directory, where there is a need to handle identical file names.  Joanne has posted details here:  https://confluence.slac.stanford.edu/display/SAS/Proposal+for+obf+extlib+Organization  Tracy is aware of the proposal and thus far has no complaints.

FRED v0r100 upgrade:  Emmanuel has been pursuing this and has run into a problem in testing.  He has built a newer version of FOX.  When testing by starting up FRED using ruby, he receives a segmentation fault.  Emmanuel has sent around details and will get back to this.

Agenda

  • Release Manager Status
    • Backend
      • Windows
      • RHEL5 running
        • Any news about Babar's plans for RHEL5?
      • Mac boxes back up and runnning
      • Any news on developers updating their code in accordance with 64 bit fixes?
  • Installer
    • user release status
    • developer release status
  • Front End - Karen
  • No labels