elodilles | reminder: meeting in 30 mins | 13:30 |
---|---|---|
ttx | Made it to the airport lounge, so I should be able to attend! | 13:48 |
elodilles | :-o | 13:58 |
elodilles | thanks ttx :) | 13:59 |
elodilles | let's start then! | 14:00 |
elodilles | #startmeeting releaseteam | 14:00 |
opendevmeet | Meeting 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 |
opendevmeet | Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. | 14:00 |
opendevmeet | The meeting name has been set to 'releaseteam' | 14:00 |
elodilles | Ping list: release-team elod | 14:00 |
elodilles | #link https://etherpad.opendev.org/p/flamingo-relmgt-tracking | 14:00 |
elodilles | we are at line 103 | 14:00 |
elodilles | o/ | 14:00 |
ttx | o/ | 14:01 |
elodilles | wanted 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 completion | 14:04 |
elodilles | 1st 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 |
elodilles | let me check quickly if the tags are present | 14:04 |
frickler | o/ | 14:05 |
elodilles | hi frickler o/ | 14:05 |
frickler | I didn't get to that yet, sorry | 14:05 |
elodilles | frickler: ACK, no worries, you said that in advance that you might not get there | 14:06 |
elodilles | and we are not in a hurry | 14:06 |
elodilles | should i add to next week's task just to not forget it? | 14:06 |
frickler | yes, please | 14:06 |
elodilles | well, i added it to R-17 week, not next week, as next week is an "empty" week without any tasks and meeting | 14:08 |
frickler | ack | 14:08 |
elodilles | 2nd task: 'Review any remaining milestone-1 exceptions (all)' | 14:08 |
elodilles | https://review.opendev.org/q/topic:flamingo-milestone-1+is:open | 14:08 |
elodilles | yepp, we have still oslo.limit waiting for the release :/ | 14:08 |
elodilles | i forgot to ping oslo team earlier this week and AFAIK today is the day when RH folks are out of office | 14:09 |
elodilles | so this will remain to next weeks as well | 14:09 |
ttx | Yeah that one is not making a lot of progress. Maybe we should ask Takashi-san if it's ok to release without | 14:10 |
ttx | (without that extra commit) | 14:10 |
elodilles | yeah that's also possible. i don't remember how important / big changes the release would contain | 14:11 |
elodilles | anyways, we have to double check with oslo team | 14:11 |
elodilles | i've copied this over to R-17 week as well | 14:11 |
elodilles | and assigned it to me to track this with Oslo team | 14:11 |
elodilles | 3rd task: 'Ensure that all new-release patches in requirements repository for the milestone-1 releases are merged (all)' | 14:12 |
elodilles | https://review.opendev.org/q/project:openstack/requirements+branch:master+is:open+topic:new-release | 14:12 |
elodilles | and that is an empty list \o/ | 14:12 |
elodilles | so all the releases are added to upper constraints and teams are testing with them! | 14:13 |
ttx | yay | 14:13 |
elodilles | and that was all about tasks | 14:13 |
elodilles | #topic Assign R-17 week tasks | 14:13 |
elodilles | as far as i see all tasks taken | 14:13 |
elodilles | thanks all o/ | 14:13 |
elodilles | #topic Open Discussion | 14:14 |
elodilles | and here we are ^^^ | 14:14 |
elodilles | anything to discuss? | 14:14 |
fungi | the cla->dco switch in a month is going to affect some patch generation scripts, just as a heads up | 14:15 |
ttx | no email this week? Sweet | 14:15 |
elodilles | fungi: you mean we have to have 'signed-off' tags in generated patches, right? | 14:16 |
elodilles | ttx: yepp, no mail this time :] | 14:16 |
fungi | yes, 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 scripts | 14:16 |
fungi | (so that we also start complying with the foundation's ai contribution policy) | 14:17 |
elodilles | oh, good to know | 14:17 |
fungi | just noting there will be some patches to those jobs/scripts in the coming weeks | 14:18 |
elodilles | release tooling usually add already the 'signed-off' tags, but i forgot about the constraints update job | 14:18 |
fungi | good to know that's already in there | 14:18 |
elodilles | fungi: are you or the infra team planning to propose those patches? | 14:18 |
fungi | not sure yet who will propose them, might be me | 14:18 |
fungi | still waiting for the dust to settle on the tc resolution before doing too much prep | 14:19 |
elodilles | ACK, thanks, i was just unsure if we have to prepare the patches o:) | 14:19 |
elodilles | fungi: makes sense | 14:19 |
fungi | we've got hopefully a month to sort it all out after the resolution gets approved | 14:20 |
elodilles | fungi: 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 |
elodilles | fungi: ++ | 14:20 |
fungi | will do, i expect we'll use a consistent review hashtag for all of the changes too | 14:20 |
elodilles | that's a good idea | 14:21 |
elodilles | i'll double check if any of our scripts in release repository needs an update, too | 14:22 |
elodilles | Okay, thanks for the info fungi o/ | 14:23 |
fungi | yeah, finding anything that calls `git commit` would help | 14:23 |
elodilles | anything else before we close the meeting? | 14:23 |
elodilles | fungi: yepp | 14:23 |
ttx | nothing from me | 14:24 |
elodilles | looks not, so let's end the meeting | 14:26 |
elodilles | thanks everyone for participating o/ | 14:26 |
elodilles | #endmeeting | 14:26 |
opendevmeet | Meeting ended Fri May 23 14:26:32 2025 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | 14:26 |
opendevmeet | Minutes: https://meetings.opendev.org/meetings/releaseteam/2025/releaseteam.2025-05-23-14.00.html | 14:26 |
opendevmeet | Minutes (text): https://meetings.opendev.org/meetings/releaseteam/2025/releaseteam.2025-05-23-14.00.txt | 14:26 |
opendevmeet | Log: https://meetings.opendev.org/meetings/releaseteam/2025/releaseteam.2025-05-23-14.00.log.html | 14:26 |
elodilles | safe travels && bon voyage ttx :) | 14:26 |
ttx | thanks elodilles ! | 14:28 |
elodilles | fungi: 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 |
fungi | elodilles: that won't be necessary. existing changes don't need signed-off-by as they were contributed under the (also entirely valid) cla | 14:30 |
fungi | only new contributions after the switch (completely new changes or revisions to an existing change) will need signed-off-by when pushed to gerrit | 14:31 |
elodilles | i meant for newly created patches | 14:31 |
fungi | gerrit will block them at push if the signed-off-by is missing or incorrect, so they'll never make it into the system | 14:31 |
elodilles | ah, i see, thanks | 14:32 |
fungi | same as it does for cla enforcement today, you can't push a change or revision to gerrit if you haven't agreed to the cla | 14:32 |
elodilles | +1 | 14:32 |
opendevreview | Elod Illes proposed openstack/releases master: Add 'signed off by' tag to bulk_review.sh https://review.opendev.org/c/openstack/releases/+/950760 | 14:40 |
elodilles | fungi: found one ^^^ | 14:40 |
fungi | good catch! | 14:41 |
elodilles | tools/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 that | 14:42 |
fungi | yeah, we'll need to track those down and check them | 14:43 |
opendevreview | Elod Illes proposed openstack/releases master: [tools] Add 'signed off by' tag to scripts https://review.opendev.org/c/openstack/releases/+/950760 | 14:43 |
elodilles | ahh, maybe it's easier to have -s there as well anyway, even if that is not used, so i've added ^^^ | 14:44 |
opendevreview | Jeremy Stanley proposed openstack/releases master: Comply with Policy for AI Generated Content https://review.opendev.org/c/openstack/releases/+/950763 | 15:07 |
fungi | elodilles: ^ a follow-up | 15:07 |
Clark[m] | Should there be a space between the footer key and it's value? | 15:10 |
fungi | Clark[m]: see the git-commit manpage, it's a colon-delimited key:value pair | 15:10 |
fungi | the line that ends up in the commit message footer paragraph looks like: | 15:10 |
fungi | Generated-By: openstack/releases:tools/bulk_review.sh | 15:10 |
Clark[m] | Aha | 15:11 |
fungi | so it's not a raw string, confusingly | 15:11 |
fungi | but still, xceptionally convenient that git added that cli option | 15:12 |
fungi | er, exceptionally | 15:12 |
elodilles | fungi: +2'd, thanks! | 15:12 |
fungi | i 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 |
fungi | the foundation's ai policy gives us a nice consistent format for doing so | 15:16 |
fungi | and might also provide increased visibility so that human contributors remember they should add something similar to their commit messages when appropriate | 15:16 |
elodilles | yepp, this is a great way for both as an example as for identification of the source of the patch. good idea! | 15:26 |
opendevreview | Jeremy Stanley proposed openstack/releases master: Comply with Policy for AI Generated Content https://review.opendev.org/c/openstack/releases/+/950763 | 15:34 |
fungi | spotted another place `git commit` was being called, but which wasn't touched by the parent commit because it already used -s | 15:34 |
Generated by irclog2html.py 4.0.0 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!