-
Notifications
You must be signed in to change notification settings - Fork 24
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Release 2024-09-20ish #647
Comments
Proposal of packages to be tagged and included for the upcoming release:
Anything else? |
And for completeness:
|
I think we should also start making tags for key4hep-spack again (as we did for some time in the past), to make it easy to reproduce these builds if necessary (spack commits and cherry-picks are then also available from that tag, not just from cvmfs). |
We also need a first tag for the following, I think:
|
Hi, following releases are ready:
ATM I'm trying to finish FCCAnalyses in this PR: HEP-FCC/FCCAnalyses#309 |
Since no one complained when changing the compiler to GCC 14 for the AlmaLinux 9 nightly builds I won't make a build with GCC 11 and in some time I will stop building the nightlies with GCC 11 (now it's possible to choose either GCC 14 or GCC 11 with Alma 9). |
Makes sense to drop gcc11 soon. |
Hi, for the FCCAnalyses the new tag is v0.10.0 |
These ones are still missing, I can only do |
Hi all and @jmcarcell, there is another release of k4RecCalorimeter with fixes from @tmadlener: v0.1.0pre15 |
Release 2024-10-03 (when building started) has been deployed (Alma 9) or is in the process (Ubuntu 22). I'll send an email later today after a few things are checked. |
List of packages (@BrieucF to add)
edit (Thomas): copied all elements to the top level comment to have github pick them up as tasks
edit (Brieuc): add a PR that would be nice to have in k4geo, if possible in time, if not let's proceed
k4GeneratorsConfig
ddfastshowerml
(Add tags for the packages living on the desy gitlab #658)marlinmlflavortagging
(Add tags for the packages living on the desy gitlab #658)The text was updated successfully, but these errors were encountered: