Attendees: Stefan Roiser, Andreas Pfeiffer, Dirk Duellmann, Bertrand Bellmann, Tony Poll,
News
===
+ LCG 53b is released - it contains fixes for ROOT and POOL, Atlas nightlies are working fine with it, CMS will pick it up in one of the next development cycles.
+ We resurrected the nightlies mails, i.e. reports about errors, crashes per platform / slot will be sent to the project responsibles. These are
LCGCMT: Piotr, Stefan
ROOT: Bertrand, Axel
RELAX: Stefan
CORAL: Dirk
COOL: Andrea, Marco Cl.
POOL: Dirk
Gaudi: Hubert, Marco Cl.
+ New packages installed
- 4suite 1.0.2 - a python XSLT processor
- pyxml 0.8.4 - xml tools for python (including validating xml parser)
+ New package requests for FastJet (2.1.0) and KtJet (1.08)
- The Generator project has an installation for ktjet available
- FastJet can be installed aswell
Round Table
===
SPI
---
+ We are aiming for LCG 54, plans are
- move to new CLHEP 1.9.3.1 - this removes dependencies on HepMC and HepPDT
- move to new gccxml 0.6.0_patch4 - for support of the gcc 4.1 compiler
- complete stack for LCG/AA projects on osx/intel
- ROOT is already available for osx/intel
- The other projects will be installed in place if possible
+ The changes in the packages has been tested from yesterday in the nightlies. The clhep version was missing for osx/intel, now installed, otherwise seems to be fine.
Persistency
---
+ Usage problems with the threading capabilities of CORAL, it was proposed to turn off the threading by default and only turn it on on request (to be discussed in the AF)
AoB
===
+ Can we improve the time to delivery for LCG/AA projects from the announcement until the ready LCG release?
The build time of the projects is not so much the issue, than rather the time to get a configuration for a project together and to tag the repository for it. It was discussed to give SPI people the right to tag the repositories of the LCG/AA projects. At the moment in SPI a system is setup to use the same build configuration for the nightly builds and the release of projects. If this is in place a tag of the repository can be applied after the nightlies have been "rubber stamped" having the requested functinoality and subsequently a release can be produced the same way the nightlies were done. Dirk will give access to the Persistency project repositories.
There are minutes attached to this event.
Show them.