14:00:14 #startmeeting releaseteam 14:00:14 Meeting started Fri Oct 3 14:00:14 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:14 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 14:00:14 The meeting name has been set to 'releaseteam' 14:00:20 Ping list: release-team elod 14:00:30 #link https://etherpad.opendev.org/p/flamingo-relmgt-tracking 14:00:51 we are waaaay down at the bottom, at line 451 14:00:53 o/ 14:00:55 o/ 14:01:20 let's get started as frickler is on PTO 14:01:27 Probably not worth it to go over every task... safe to assume we completed all of them 14:01:38 yepp 14:01:48 maybe just a discussion on how well the process went, maybe 14:02:00 #topic Review task completion / release postmortem 14:02:19 all tasks were finished 14:02:22 There was a glitch around afs publication toward the end, but you semed to have it under control? 14:02:25 seemed* 14:02:45 and it wasn't for a normal step in the process 14:02:49 yes, fortunately that went well on the 3rd try :S 14:03:06 it was holding up a separate docs fix that should have been merged last week 14:03:26 fungi: exactly 14:04:00 it was a wrong link we missed to catch around Epoxy release time 14:04:14 but fortunately frickler found it now 14:04:30 ok, anything we should/can do to avoid similar issues in the future? 14:04:59 though the question is whether this could happen when we push the new web page updates next time 14:05:05 maybe a checklist addition to look for outstanding docs fixes related to the release? i dunno 14:06:05 slightly related, that i got a lot of 403 / 404 responses when running scrappy for the sitemap.xml update task: https://review.opendev.org/c/openstack/openstack-manuals/+/962792 14:06:49 see my comment https://review.opendev.org/c/openstack/openstack-manuals/+/962792/1#message-2ebe61e3f183d40b8f5482924ac4164d113f8973 14:07:00 i have a feeling the docs site http/403 problem was a symptom of increases in llm training crawler traffic just generally overloading the afs client and making it take longer to pull some updated files into its cache 14:07:22 :S 14:07:38 i'm getting super slow response for e.g. releases.openstack.org right now too (same server) 14:08:02 yeah, it's slow for me as well 14:08:08 system load is really low, but i need to check the apache scorecard, there's a good chance it's not got any free worker slots 14:08:47 anyway, it was maybe good to mention, and we should take an eye on it, especially around Gazpacho release 14:08:51 we can increase those if there are free resources (seems like there are plenty) 14:09:50 +1 14:10:17 beyond this issue, i think the rest of the tasks went smoothly 14:10:23 anything else to add? 14:11:00 no 14:11:18 i'll merge the signing key rotation change some time on monday 14:11:44 fungi: ACK, thanks! 14:12:01 i'll remind folks, but a test release immediately after or taking approvals slow at first until we know it's working is a good idea, as usual 14:12:33 fungi: indeed, we can do a test release out of release-test 14:12:53 yeah, if folks have time that'll be the best way 14:13:03 btw, i'll be out on Monday, but we can do that on Tuesday if you won't have time earlier 14:13:31 good. move on then 14:13:34 #topic Assign Gazpacho R-25 tasks 14:13:43 #link https://etherpad.opendev.org/p/gazpacho-relmgt-tracking 14:13:52 line 21 ^^^ 14:14:26 all taken 14:14:40 #topic Open Discussion 14:14:50 anything to discuss? 14:16:16 do we need a meeting next week? 14:16:46 oh, probably yes if we skip the next 3 weeks 14:17:00 we can assign tasks a bit in advance 14:17:23 maybe it's worth to go through the tasks next week. but afterwards i think we could have a couple of "meeting-free" weeks o:) 14:17:49 I guess we should have one during PTG 14:18:11 * ttx fixes the tracker doc 14:18:15 yes, we can have a short discussion during the PTG 14:19:13 probably there won't be many things to discuss related to the weekly tasks, but otherwise we can have a short session 14:19:21 yep 14:20:17 It's on the agenda at 15utc on Friday 14:20:25 not sure why I picked that hour 14:20:32 btw, please review the gazpacho-relmgt-tracking page whether i missed something or if i did any mistake in it 14:20:38 dayling time changes? 14:20:45 er, daylight 14:20:49 yeah, but maybe I was confused 14:21:13 * fungi is perpetually confused 14:21:26 :) 14:22:38 should probably keep it to 14utc 14:22:46 to avoid changing the hour just before 14:22:53 ttx: for consistency, that could help, yes 14:22:55 I'll move it around 14:23:01 thanks! 14:24:36 ok moved 14:24:55 awesome, now i don't need to make a separate reminder ;) 14:24:55 ++ 14:25:05 :] 14:27:00 another note, that if i remember well frickler will be on PTO in the coming 2 weeks, so we should not wait for his reviews in case of release patches 14:27:53 ack 14:27:58 nothing else from me 14:28:21 okay, then let's end the meeting and give back some time to everyone :) 14:28:29 thanks for participating o/ 14:28:33 #endmeeting