April, 2007
CMT or Not CMT
See the WhiteBoard no VS2005 support (and no clear plans to do so by cmt-central), doesn't create useful Intel Mac Makefiles, we're already behind the CMT-times, but ditch CMT at what cost? (in some Jim T. Kirk voice)
When you don't know what to do.. set up a task force!
Associated issues:
Mucho environment variables such as <package>ROOT
Package dependencies - we need to have a careful review of our uses, and consider -no_auto_imports in those cases where the use is required.
Getting a handle on our externals
Should make sure we keep the source around - presently it's stashed on u05.
Automated External Builds for all platforms and at the very least document the method of building all of our externals - this was started in the Developer's Corner some time ago and never finished.
When to upgrade Gaudi again? may be driven by our need to support RHEL4 and Intel Mac..or our interest level in GaudiPython
cppunit should be set up to use the shared library rather than the static lib - if it's not already.
Pointer Skims
See Eric's talk: http://confluence.slac.stanford.edu/download/attachments/20011/Event_Collections.pdf
Go with a fully-ROOT implementation or use MySQL?
Like to have something by end of April.
RHEL4
GSFC set to move soon (actually they seem to be maintaining a machine specifically for GR now)..and Joanne's laptop is now RHEL4. Most of GR's packages now compile - there seems a lingering issue with CLHEP/Gaudi - who will look into this and when? And what of the remaining compilation failures? (Yes we see you CalRecon and TkrRecon!)
Release Manager
It would be best if RM and MrStudio would share as much code as possible for building our packages.
Online Authentication has been bust since Sept, 2006.
See: ~glast/infraBin/ReleaseManager for command-line versions of web-based commands we no longer have access too until the online authentication issue is sorted out.
Unit Testing
Some are broke...many do nothing useful
Should consider the use of sub-packages for unit tests (will help with our dependency problem mentioned above)
Ntuple Documentation
Keeping it up to date - perhaps review every six months?
Doxygen 1.5.1 problem with @page, who will look into this and communicate our troubles to Doxygen-Central?
Do we include CalTuple or SVAC in the workbook - should we?
xxxRootData packages also need to jump over to use Doxygen for its documentation so that it is more easily included in the workbook.
Actually speaking of documentation..when was the last time you checked the mainpages of your packages?
VS2005 and Intel Mac Support
Not clear how soon we need this - but it should be kept in mind.
Shared Libraries for Utility Packages
See the WhiteBoard
Workbook
Exisiting examples should be reviewed to insure their content is still up to date.
The "Advanced" and "Data Access" navbars should be reviewed.
An archiving policy needs to be worked out.
System Tests
New interface
PyRoot
Be nice to look at using this more 