ROOT Project Meeting
Shift handover: Lukas -> Stephan
- Notable issues of git cloning, we've seen this on macos, then also on alma, the fix would be to have a github token to authenticate all git clone requests
- Danilo: we currently do up to 4 clones per job, a mitigation could be to reduce the number of clones, maybe to 2
- Staphan: has a PR to try something in this diretion
News
- We're at -20% in our issues backlog, at the upper limit of what was promised to the LHCC
Meeting summaries
- IO: investigating the CMS RNTuple use-cases that uses a lot of memory, ATLAS came with a similar issue but we identified it wasn't related to the same cause, we also concluded that we needed a backport of performance improvements so we will be carrying a patch to LLVM untill we migrate to LLVM 23
- Python bindings: CppJIT is now released on PyPI, next is to sync the ROOT migration branch on the CppJIT released code, the branch is currently green but has a lot of patches that we are currently trying to reduce
Proposals
- Danilo: Having another development release next november supported until June
- Stephan: I have a problem with the motivation being "one additional stop for deprecations", if this makes the jump to ROOT7 then I'm against, otherwise I'm for it
- Danilo: indeed this shouldn't be used as an opportunity to stuff more things
- many people: maybe it could be named root7 rc1 instead?
- JR: maybe not because we can't do bug fixes only for 6 months
- Philippe: we may end up having to do the last 6 release around the same time as 7
- Danilo: let's wrap up, we don't decide today, we still have some days to consult experiments and make a final decision
- Philippe: just to reinforce my POV, I don't see why not release 6.46, I think this would break expectations and make the jump to ROOT7 higher for experiments
- Stephan: but experiments only jump from long term to long term anyway so they won't switch to 6.46 anyway, this would hoever be a good way to keep things flowing
Liaisons
- NTR
Round table
- Serguey: struggling with a functionality i call interactivity in the canvas