Friday, 2025-05-23

elodillesreminder: meeting in 30 mins13:30
ttxMade it to the airport lounge, so I should be able to attend!13:48
elodilles:-o13:58
elodillesthanks ttx :)13:59
elodilleslet's start then!14:00
elodilles#startmeeting releaseteam14:00
opendevmeetMeeting started Fri May 23 14:00:05 2025 UTC and is due to finish in 60 minutes.  The chair is elodilles. Information about MeetBot at http://wiki.debian.org/MeetBot.14:00
opendevmeetUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.14:00
opendevmeetThe meeting name has been set to 'releaseteam'14:00
elodillesPing list: release-team elod14:00
elodilles#link https://etherpad.opendev.org/p/flamingo-relmgt-tracking14:00
elodilleswe are at line 10314:00
elodilleso/14:00
ttxo/14:01
elodilleswanted to wait to frickler as the 1st task was assigned to him, but let's start the topics to get things moving o:)14:03
elodilles#topic Review task completion14:04
elodilles1st task was: 'Manually push 2023.2-eol tags for Kolla after https://review.opendev.org/c/openstack/releases/+/948231 did not result in any tag being created (due to Bobcat being marked EOL already) (frickler)'14:04
elodilleslet me check quickly if the tags are present14:04
fricklero/14:05
elodilleshi frickler o/14:05
fricklerI didn't get to that yet, sorry14:05
elodillesfrickler: ACK, no worries, you said that in advance that you might not get there14:06
elodillesand we are not in a hurry14:06
elodillesshould i add to next week's task just to not forget it?14:06
frickleryes, please14:06
elodilleswell, i added it to R-17 week, not next week, as next week is an "empty" week without any tasks and meeting14:08
fricklerack14:08
elodilles2nd task: 'Review any remaining milestone-1 exceptions (all)'14:08
elodilleshttps://review.opendev.org/q/topic:flamingo-milestone-1+is:open14:08
elodillesyepp, we have still oslo.limit waiting for the release :/14:08
elodillesi forgot to ping oslo team earlier this week and AFAIK today is the day when RH folks are out of office14:09
elodillesso this will remain to next weeks as well14:09
ttxYeah that one is not making a lot of progress. Maybe we should ask Takashi-san if it's ok to release without14:10
ttx(without that extra commit)14:10
elodillesyeah that's also possible. i don't remember how important / big changes the release would contain14:11
elodillesanyways, we have to double check with oslo team14:11
elodillesi've copied this over to R-17 week as well14:11
elodillesand assigned it to me to track this with Oslo team14:11
elodilles3rd task: 'Ensure that all new-release patches in requirements repository for the milestone-1 releases are merged (all)'14:12
elodilleshttps://review.opendev.org/q/project:openstack/requirements+branch:master+is:open+topic:new-release14:12
elodillesand that is an empty list \o/14:12
elodillesso all the releases are added to upper constraints and teams are testing with them!14:13
ttxyay14:13
elodillesand that was all about tasks14:13
elodilles#topic Assign R-17 week tasks14:13
elodillesas far as i see all tasks taken14:13
elodillesthanks all o/14:13
elodilles#topic Open Discussion14:14
elodillesand here we are ^^^14:14
elodillesanything to discuss?14:14
fungithe cla->dco switch in a month is going to affect some patch generation scripts, just as a heads up14:15
ttxno email this week? Sweet14:15
elodillesfungi: you mean we have to have 'signed-off' tags in generated patches, right?14:16
elodillesttx: yepp, no mail this time :]14:16
fungiyes, e.g. the constraints update job will need to start doing git commit -s, and that's probably a good time to also add the generated-by footer to those same scripts14:16
fungi(so that we also start complying with the foundation's ai contribution policy)14:17
elodillesoh, good to know14:17
fungijust noting there will be some patches to those jobs/scripts in the coming weeks14:18
elodillesrelease tooling usually add already the 'signed-off' tags, but i forgot about the constraints update job14:18
fungigood to know that's already in there14:18
elodillesfungi: are you or the infra team planning to propose those patches?14:18
funginot sure yet who will propose them, might be me14:18
fungistill waiting for the dust to settle on the tc resolution before doing too much prep14:19
elodillesACK, thanks, i was just unsure if we have to prepare the patches o:)14:19
elodillesfungi: makes sense14:19
fungiwe've got hopefully a month to sort it all out after the resolution gets approved14:20
elodillesfungi: i'll try to take an eye on it but please add me as reviewer so that i won't miss it to review o:)14:20
elodillesfungi: ++14:20
fungiwill do, i expect we'll use a consistent review hashtag for all of the changes too14:20
elodillesthat's a good idea14:21
elodillesi'll double check if any of our scripts in release repository needs an update, too14:22
elodillesOkay, thanks for the info fungi o/14:23
fungiyeah, finding anything that calls `git commit` would help14:23
elodillesanything else before we close the meeting?14:23
elodillesfungi: yepp14:23
ttxnothing from me14:24
elodilleslooks not, so let's end the meeting14:26
elodillesthanks everyone for participating o/14:26
elodilles#endmeeting14:26
opendevmeetMeeting ended Fri May 23 14:26:32 2025 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)14:26
opendevmeetMinutes:        https://meetings.opendev.org/meetings/releaseteam/2025/releaseteam.2025-05-23-14.00.html14:26
opendevmeetMinutes (text): https://meetings.opendev.org/meetings/releaseteam/2025/releaseteam.2025-05-23-14.00.txt14:26
opendevmeetLog:            https://meetings.opendev.org/meetings/releaseteam/2025/releaseteam.2025-05-23-14.00.log.html14:26
elodillessafe travels && bon voyage ttx :)14:26
ttxthanks elodilles !14:28
elodillesfungi: btw, will there be a gerrit check or something to -W a patch if there's no 'signed-off' tag? or is it too early to ask and this will be all described in the TC resolution? o:)14:30
fungielodilles: that won't be necessary. existing changes don't need signed-off-by as they were contributed under the (also entirely valid) cla14:30
fungionly new contributions after the switch (completely new changes or revisions to an existing change) will need signed-off-by when pushed to gerrit14:31
elodillesi meant for newly created patches14:31
fungigerrit will block them at push if the signed-off-by is missing or incorrect, so they'll never make it into the system14:31
elodillesah, i see, thanks14:32
fungisame as it does for cla enforcement today, you can't push a change or revision to gerrit if you haven't agreed to the cla14:32
elodilles+114:32
opendevreviewElod Illes proposed openstack/releases master: Add 'signed off by' tag to bulk_review.sh  https://review.opendev.org/c/openstack/releases/+/95076014:40
elodillesfungi: found one ^^^14:40
fungigood catch!14:41
elodillestools/functions have the scripts to 'Update .gitreview' patches, but i'm not sure that is used in the jobs as i remember there are some copied scripts in project-config repo or something like that14:42
fungiyeah, we'll need to track those down and check them14:43
opendevreviewElod Illes proposed openstack/releases master: [tools] Add 'signed off by' tag to scripts  https://review.opendev.org/c/openstack/releases/+/95076014:43
elodillesahh, maybe it's easier to have -s there as well anyway, even if that is not used, so i've added ^^^14:44
opendevreviewJeremy Stanley proposed openstack/releases master: Comply with Policy for AI Generated Content  https://review.opendev.org/c/openstack/releases/+/95076315:07
fungielodilles: ^ a follow-up15:07
Clark[m]Should there be a space between the footer key and it's value?15:10
fungiClark[m]: see the git-commit manpage, it's a colon-delimited key:value pair15:10
fungithe line that ends up in the commit message footer paragraph looks like:15:10
fungiGenerated-By: openstack/releases:tools/bulk_review.sh15:10
Clark[m]Aha15:11
fungiso it's not a raw string, confusingly15:11
fungibut still, xceptionally convenient that git added that cli option15:12
fungier, exceptionally15:12
elodillesfungi: +2'd, thanks!15:12
fungii figure that's a good place to start as an example of more widespread implementation, and a great way for our tools to identify their work (e.g. so that people can easily find what to modify and where when it starts to generate incorrect patches)15:15
fungithe foundation's ai policy gives us a nice consistent format for doing so15:16
fungiand might also provide increased visibility so that human contributors remember they should add something similar to their commit messages when appropriate15:16
elodillesyepp, this is a great way for both as an example as for identification of the source of the patch. good idea!15:26
opendevreviewJeremy Stanley proposed openstack/releases master: Comply with Policy for AI Generated Content  https://review.opendev.org/c/openstack/releases/+/95076315:34
fungispotted another place `git commit` was being called, but which wasn't touched by the parent commit because it already used -s15:34

Generated by irclog2html.py 4.0.0 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!