rename "2026" workflows

[fwyzard]

Can we rename the "2026" workflows and relvals to something more realistic, like "2030" or "Run4" ?

[fwyzard]

assign pdmv

[cmsbuild]

New categories assigned: pdmv

@AdrianoDee,@sunilUIET,@miquork,@kskovpen you have been requested to review this Pull request/Issue and eventually sign? Thanks

[cmsbuild]

cms-bot internal usage

[cmsbuild]

A new Issue was created by @fwyzard.

@Dr15Jones, @antoniovilela, @makortel, @mandrenguyen, @rappoccio, @sextonkennedy, @smuzaffar can you please review it and eventually sign/assign? Thanks.

cms-bot commands are listed here

[AdrianoDee]

Definetely

[makortel]

assign upgrade

[cmsbuild]

New categories assigned: upgrade

@srimanob,@subirsarkar you have been requested to review this Pull request/Issue and eventually sign? Thanks

[srimanob]

Note, thanks for suggestion. I would propose we go with 2030 to keep consistent with remaining, i.e. 2017.

[davidlange6]

a vote for run4... we've changed the year for these workflows once before :(..

[AdrianoDee]

I would go for Run4, too. Or phase2, to be more inclusive. Also because relval_2017 is kind of misleading too, given now it has wfs from 2017 to 2024. It would deserve a change in name too (maybe phase1?).

And since we are here [sorry (-: ] even relval_upgrade.py includes a huge variety of wfs really not only upgrade related. They are more ... "customized RelVals" from my point of view (e.g. we use the "upgrade" matrix for standard Run3 RelVals productions).

[AdrianoDee]

+pdmv
(solved by #46582 )