14:00:05 #startmeeting releaseteam 14:00:05 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:05 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 14:00:05 The meeting name has been set to 'releaseteam' 14:00:14 Ping list: release-team elod 14:00:23 #link https://etherpad.opendev.org/p/flamingo-relmgt-tracking 14:00:49 we are at line 103 14:00:59 o/ 14:01:13 o/ 14:03:52 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:04:06 #topic Review task completion 14:04:22 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:35 let me check quickly if the tags are present 14:05:23 o/ 14:05:30 hi frickler o/ 14:05:44 I didn't get to that yet, sorry 14:06:10 frickler: ACK, no worries, you said that in advance that you might not get there 14:06:20 and we are not in a hurry 14:06:39 should i add to next week's task just to not forget it? 14:06:49 yes, please 14:08:01 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:16 ack 14:08:25 2nd task: 'Review any remaining milestone-1 exceptions (all)' 14:08:35 https://review.opendev.org/q/topic:flamingo-milestone-1+is:open 14:08:54 yepp, we have still oslo.limit waiting for the release :/ 14:09:29 i forgot to ping oslo team earlier this week and AFAIK today is the day when RH folks are out of office 14:09:46 so this will remain to next weeks as well 14:10:24 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:44 (without that extra commit) 14:11:12 yeah that's also possible. i don't remember how important / big changes the release would contain 14:11:23 anyways, we have to double check with oslo team 14:11:27 i've copied this over to R-17 week as well 14:11:50 and assigned it to me to track this with Oslo team 14:12:25 3rd task: 'Ensure that all new-release patches in requirements repository for the milestone-1 releases are merged (all)' 14:12:32 https://review.opendev.org/q/project:openstack/requirements+branch:master+is:open+topic:new-release 14:12:44 and that is an empty list \o/ 14:13:12 so all the releases are added to upper constraints and teams are testing with them! 14:13:13 yay 14:13:31 and that was all about tasks 14:13:42 #topic Assign R-17 week tasks 14:13:50 as far as i see all tasks taken 14:13:58 thanks all o/ 14:14:32 #topic Open Discussion 14:14:36 and here we are ^^^ 14:14:41 anything to discuss? 14:15:19 the cla->dco switch in a month is going to affect some patch generation scripts, just as a heads up 14:15:22 no email this week? Sweet 14:16:14 fungi: you mean we have to have 'signed-off' tags in generated patches, right? 14:16:29 ttx: yepp, no mail this time :] 14:16:40 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:17:12 (so that we also start complying with the foundation's ai contribution policy) 14:17:26 oh, good to know 14:18:05 just noting there will be some patches to those jobs/scripts in the coming weeks 14:18:06 release tooling usually add already the 'signed-off' tags, but i forgot about the constraints update job 14:18:43 good to know that's already in there 14:18:44 fungi: are you or the infra team planning to propose those patches? 14:18:57 not sure yet who will propose them, might be me 14:19:26 still waiting for the dust to settle on the tc resolution before doing too much prep 14:19:37 ACK, thanks, i was just unsure if we have to prepare the patches o:) 14:19:49 fungi: makes sense 14:20:31 we've got hopefully a month to sort it all out after the resolution gets approved 14:20:34 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:49 fungi: ++ 14:20:54 will do, i expect we'll use a consistent review hashtag for all of the changes too 14:21:29 that's a good idea 14:22:16 i'll double check if any of our scripts in release repository needs an update, too 14:23:01 Okay, thanks for the info fungi o/ 14:23:05 yeah, finding anything that calls `git commit` would help 14:23:10 anything else before we close the meeting? 14:23:20 fungi: yepp 14:24:44 nothing from me 14:26:19 looks not, so let's end the meeting 14:26:28 thanks everyone for participating o/ 14:26:32 #endmeeting