-
Notifications
You must be signed in to change notification settings - Fork 184
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
[CMSSW_14_0] Update UTM to 13.0 #9223
[CMSSW_14_0] Update UTM to 13.0 #9223
Conversation
A new Pull Request was created by @aloeliger for branch IB/CMSSW_14_0_X/master. @smuzaffar, @iarspider, @cmsbuild, @aandvalenzuela can you please review it and eventually sign? Thanks.
|
cms-bot internal usage |
please test |
+1 Summary: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-db3d68/39673/summary.html Comparison SummarySummary:
|
+externals @cms-sw/orp-l2 feel free to merge it for next 14.0.X IB/release |
This pull request is fully signed and it will be integrated in one of the next IB/CMSSW_14_0_X/master IBs (tests are also fine). This pull request will now be reviewed by the release team before it's merged. @sextonkennedy, @rappoccio, @antoniovilela (and backports should be raised in the release meeting by the corresponding L2) |
@cms-sw/orp-l2 L1T-DPG would like to make this available for the next CMSSW_14_0 release for O2O updating at P5. Would it be possible to merge this in time for 14_0_9? |
Which we would like to use online after the TS, so potentially at the end of next week. Assuming the usual 1-2 days for testing the release before deployment, we would need it to be built and installed by Wednesday morning. |
I think the plan is now to have 14_0_9 cut by Monday or Tuesday (as discussed in Marino's email thread with ORM). It would be great if this PR can be merged to be available for that release. |
+1 |
Backport of #9214
This backport has been requested by the L1T DPG to support it's use in the CMSSW_14_0 emulator.