14:02:35 <ttx> #startmeeting releaseteam 14:02:35 <opendevmeet> Meeting started Fri Sep 5 14:02:35 2025 UTC and is due to finish in 60 minutes. The chair is ttx. Information about MeetBot at http://wiki.debian.org/MeetBot. 14:02:35 <opendevmeet> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 14:02:35 <opendevmeet> The meeting name has been set to 'releaseteam' 14:02:47 <ttx> Ping list: release-team elod 14:02:54 <elodilles> o/ 14:03:12 <ttx> Agenda at: 14:03:15 <ttx> #link https://etherpad.opendev.org/p/flamingo-relmgt-tracking#L341 14:03:34 <ttx> #topic Review task completion 14:03:54 <ttx> - Process any remaining client library freeze exception (all) 14:04:06 <ttx> #link https://review.opendev.org/q/topic:flamingo-milestone-3 14:04:17 <elodilles> all merged \o/ 14:04:19 <ttx> All set! 14:04:33 <ttx> - heat-translator release patch - broken gate (elod) 14:04:50 <ttx> #link https://review.opendev.org/q/topic:flamingo-final-non-client-libs+is:open 14:05:02 <elodilles> so the patch is still open :/ 14:05:11 <elodilles> https://review.opendev.org/c/openstack/releases/+/957695 14:05:32 <elodilles> Yasufumi commented on it that he still needs some time 14:06:06 <ttx> OK hopefully he will make progress very soon 14:06:24 <ttx> We have one more week before it becomes very inconvenient 14:06:32 <elodilles> exactly 14:06:46 <ttx> Maybe copy the task to next week for tracking purposes? 14:06:55 <elodilles> so maybe next week we have to release and do the branch cut anyway :/ 14:07:07 <elodilles> ttx: yes, let's copy it 14:07:13 <ttx> - Ensure that all new-release patches in requirements repository for the client library releases are merged. (all) This should be an empty list: 14:07:19 <ttx> #link https://review.opendev.org/q/project:openstack/requirements+branch:master+is:open+topic:new-release 14:07:28 <elodilles> empty \o/ 14:07:33 <ttx> It is an empy list! 14:07:53 <ttx> - Early in the week, email openstack-discuss list to remind PTLs that cycle-highlights are due this week so that they can be included in release marketing preparations. (elod) 14:08:23 <elodilles> the mail was sent 14:08:27 <elodilles> #link https://lists.openstack.org/archives/list/openstack-discuss@lists.openstack.org/thread/P27DVI7OLWIPAB37FDIIOZK7C6YT5QAW/ 14:08:40 <ttx> - Freeze all cycle-based library releases except for release-critical bugs. Independently-released libraries may still be released, but constraint or requirement changes will be held until after the freeze period.(all) 14:08:46 <ttx> I think we covered that 14:09:02 <elodilles> a couple of teams proposed the cycle highlights, but not that many as expected :/ 14:09:13 <ttx> - Propose stable/2025.2 branch creation for all client and non-client libraries that had not requested it at freeze time. (elod) 14:09:23 <ttx> #link https://review.opendev.org/q/topic:flamingo-stable-branches 14:09:49 <ttx> All set except https://review.opendev.org/c/openstack/releases/+/959165 14:09:56 <ttx> which we should track together with the above task 14:10:07 <elodilles> and that is because the same heat-translator gate issue 14:10:15 <elodilles> so yepp 14:10:35 <ttx> - List cycle-with-intermediary deliverables that have not been refreshed in the last 2 months. For this, use the following command, with YYYY-MM-DD being the day two months ago and send email to them (see process for template) (ttx) 14:11:09 <ttx> That uncovered the following not-so-fresh deliverables: 14:11:20 <ttx> horizon 25.4.0 2025-05-27 14:11:20 <ttx> ironic-python-agent-builder 6.1.0 2025-06-10 14:11:20 <ttx> networking-baremetal 6.6.0 2025-06-10 14:11:28 <ttx> The teams were notified 14:12:10 <ttx> Last task was: 14:12:11 <ttx> - investigate https://bugs.launchpad.net/octavia/+bug/2121578 (elod) 14:12:59 <elodilles> i did some investigation, but to tell the truth i did not see broken things beyond the linked things from the bug report 14:13:30 <elodilles> so this needs to be continued 14:14:06 <ttx> ok maybe push back to next week 14:14:11 <elodilles> +1 14:14:23 <ttx> Last task is to send the email, which I'll do today after meeting 14:14:37 <ttx> #topic Assign R-3 week tasks 14:14:48 <ttx> I took over the meeting since I won;t be able to do the one in two weeks 14:15:06 <ttx> Loks like all tasks are assigned 14:15:40 <elodilles> ttx: ACK, thanks. i added my name to the meeting after then 14:15:55 <ttx> #topic Review weekly countdown email 14:16:00 <ttx> #link https://etherpad.opendev.org/p/relmgmt-weekly-emails 14:18:11 <elodilles> LGTM 14:18:19 <ttx> ok will send after meeting 14:18:25 <elodilles> ++ 14:18:33 <ttx> #topic Open Discussion 14:18:39 <ttx> Anything else to discuss? 14:19:16 <elodilles> hmmm, maybe one thing 14:19:22 <elodilles> that comes into my mind 14:19:30 <elodilles> #link https://review.opendev.org/c/openstack/governance/+/958297 14:19:46 <elodilles> metalsmith retirement ^^^ 14:19:59 <elodilles> the governance patch is still not merged 14:20:08 <ttx> hm 14:20:19 <elodilles> and i think we cut stable/2025.2 branch as well today (sorry, i forgot it...) 14:20:31 <fungi> it sounded like the plan floated by JayF on the mailing list was to proceed with releasing it for flamingo and then retire it at the start of the gazpacho cycle? 14:20:48 <ttx> "it will not be included in the Flamingo release" says the patch 14:21:06 <fungi> i'd have to go digging in ml threads, that was a couple weeks ago before i went on vacation 14:21:06 <elodilles> fungi: oh, i missed that, but if that is the case, then we are according to plans at least... :S 14:21:18 <fungi> lemme see if i can dig it up 14:22:20 <ttx> If not we could just kill the branch manually, and remove the deliverable file 14:22:31 <ttx> that would "remove it from the coordinated release" 14:23:27 <elodilles> https://lists.openstack.org/archives/list/openstack-discuss@lists.openstack.org/thread/WFCMET4UJDW56YJKWGA5DSIB37LZUR4B/#WFCMET4UJDW56YJKWGA5DSIB37LZUR4B 14:23:31 <elodilles> fungi: ^^^ 14:23:39 <fungi> yeah, just found it 14:23:52 <fungi> in the thread for the message linked from the governance change 14:24:41 <fungi> "After talking with the Release team on Friday/Monday, we already did a Flamingo-versioned release of Metalsmith, meaning that completely excluding it from the Flamingo release is a nontrivial undertaking. I propose we allow this release to be the final one ever of Metalsmith, and retire the master branch and any unsupported releases after the integrated release is 14:24:43 <fungi> complete." 14:25:06 <elodilles> +1 14:25:12 <fungi> glad my memory wasn't completely off-base this time ;) 14:25:17 <elodilles> :] 14:25:49 <fungi> granted, that was merely a proposal on JayF's part, there seem to be no responses in support or against 14:26:12 <fungi> but i would interpret the deafening silence as enthusiastic tacit approval 14:26:17 <ttx> we should mention it in the governance patch for completeness 14:26:29 <elodilles> +1 14:26:33 <ttx> I'll do that 14:26:43 <elodilles> thanks! 14:27:25 <elodilles> we just have to remember not to copy over metalsmith.yaml to deliverables/gazpacho 14:27:53 <elodilles> (if the governance commit goes through) 14:28:02 <ttx> right 14:28:17 <elodilles> okay, then nothing else from me 14:28:29 <ttx> maybe write it down at the bottom of the tracking doc in the "things to change" section 14:28:42 <elodilles> +1 14:28:43 <ttx> so that we don;t forget 14:28:51 <ttx> alright, if nothing else... 14:28:53 * elodilles adds it now 14:28:57 <ttx> #endmeeting