14:00:13 <ttx> #startmeeting releaseteam
14:00:13 <opendevmeet> Meeting started Fri Mar 28 14:00:13 2025 UTC and is due to finish in 60 minutes.  The chair is ttx. Information about MeetBot at http://wiki.debian.org/MeetBot.
14:00:13 <opendevmeet> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
14:00:13 <opendevmeet> The meeting name has been set to 'releaseteam'
14:00:19 <ttx> Ping list: release-team armstrong
14:00:27 <ttx> Our agenda at:
14:00:27 <elodilles> o/
14:00:32 <ttx> #link https://etherpad.opendev.org/p/epoxy-relmgt-tracking#L394
14:00:58 <frickler> \o
14:01:27 <ttx> makes me think, we should probably create the Flamingo tracker :)
14:01:31 <ttx> #topic Review task completion
14:01:53 <ttx> - Process any remaining stable branching exception
14:02:19 <kacperrh[m]> \o
14:02:40 <ttx> Looks like https://review.opendev.org/c/openstack/releases/+/945279 was merged
14:02:45 <elodilles> yepp
14:02:48 <ttx> So I think we are done here?
14:02:57 <elodilles> yes, everything has branched
14:03:07 <elodilles> and finally requirements, too
14:03:12 <ttx> - Notify the documentation team (elod)
14:03:23 <ttx> #link https://review.opendev.org/q/topic:www-epoxy-final
14:03:38 <elodilles> i've created the patches
14:03:58 <elodilles> sitemap.xml is not refreshed yet, but as far as i understand it should be after the final release
14:04:06 <ttx> right
14:04:14 <ttx> - On the day before the deadline for final release candidates, propose last-minute RCs where needed
14:04:32 <fungi> when i get back to the house i need to go ahead and push up the temporary semaphore changes for wednesday so i don't forget
14:04:47 <ttx> Looks like we have two left
14:05:01 <ttx> Cinder RC2 https://review.opendev.org/c/openstack/releases/+/945741
14:05:02 <elodilles> fungi: oh, good, yes, that will help us a lot! thanks in advance!
14:05:12 <ttx> Trove RC2 https://review.opendev.org/c/openstack/releases/+/945796
14:05:30 <ttx> I'm ok with approving Trove now
14:05:37 <elodilles> me too
14:05:57 <ttx> yes pushed my +2
14:06:04 <ttx> just pushed*
14:06:32 <elodilles> +2+W'd
14:07:02 <elodilles> so we just need cinder's RC2 :)
14:07:34 <fungi> we should probably add a reminder in the r-1 week checklist for future cycles to prepare the semaphore change, lest i forget one of these times
14:07:36 <ttx> Re: Cinder, are we ok granting them an exception? Since I won't be very available next week, I leave the call to y'all
14:08:06 <elodilles> fungi: ACK, will do a process patch after the meeting for that
14:08:33 <frickler> we should place a deadline on cinder at least. monday 12 utc?
14:08:54 <ttx> trying to track which patches they are waiting on
14:09:25 <elodilles> i have a feeling that they will be ready with RC2 today EOB (US timezone)
14:09:41 <ttx> https://review.opendev.org/q/project:openstack/cinder+branch:stable/2025.1+status:open
14:09:45 <fungi> in the future, gerrit hashtags could be used to identify pending changes for situations like this
14:09:58 <elodilles> but we can hurry the team via their RC2 patch
14:10:28 <ttx> Looks like two are in the pipeline to merge
14:10:38 <fungi> rosmaita was asking me questions about backporting job fixes to stable, which i assume was related
14:10:39 <ttx> the third one might not be one they are waiting for
14:11:14 <ttx> I think that one can land post-release
14:11:20 <elodilles> +1
14:11:32 <ttx> so we might be able to push Cinder RC2 in a few hours
14:11:44 <ttx> which would be great, allowing us to push that final release promotion patch
14:11:46 <elodilles> fingers crossed
14:12:33 <ttx> anything else on this one?
14:12:38 <elodilles> i'll be available today after the meeting for a couple of hours and even can check things at late hours (EU)
14:12:58 <fungi> i'm okay massaging the integrated gate pipeline to prioritize those cinder stable/2025.1 changes if getting them merged sooner would help
14:13:34 <ttx> fungi: if the line is long, i would not mind that
14:13:42 <fungi> at the momen't i'm not in a position to check whether they're approved or what the gate backlog looks like
14:13:54 <fungi> but in about an hour i can look
14:14:03 <ttx> that would be great!
14:14:05 <ttx> - At the end of the week, send weekly email content (ttx)
14:14:11 <ttx> I'll do that in a few
14:14:31 <ttx> - After the email is sent, use propose-final-releases to tag the existing most recent release candidates as the final release for projects using the cycle-with-rc model (elod)
14:14:35 <ttx> That one is pending RC2
14:14:37 <ttx> Cinder RC2
14:14:41 <elodilles> yepp
14:14:57 <ttx> #topic Assign R+0 week tasks
14:15:16 <frickler> https://review.opendev.org/945666 is second position in gate, should be done in ~45mins, so no action needed there currently
14:15:33 <ttx> Most tasks are group tasks... I'll try to be there for the final hours of the release and will check my messages in the evenings in case there is a big blocker
14:16:19 <ttx> But I'll likely not be around before 17:00 CEST (15utc)
14:16:38 <ttx> fungi should be around for any Foundation marketing sync
14:16:49 <fungi> i'll try to be online wednesday by 10:00 utc
14:16:50 <elodilles> i can take care of the tasks that needs action
14:17:01 <fungi> just to keep an eye on stuff
14:17:17 <fungi> and yeah, happy to liaison with foundation marketing folks
14:17:34 <ttx> Sorry again for the miserable timing of my vacation. I just did not have much choice
14:17:38 <elodilles> fungi: cool, thanks!
14:18:08 <ttx> #topic Review weekly countdown email
14:18:16 <ttx> #link https://etherpad.opendev.org/p/relmgmt-weekly-emails
14:18:21 <ttx> Please review ^
14:18:39 <fungi> there is never a convenient time for vacations, sadly
14:19:33 <elodilles> i've read it in advance, LGTM
14:19:46 <ttx> I just added a "soon"
14:19:58 <elodilles> yeah, saw that, still LGTM :)
14:20:07 <ttx> OK will send it after the meeting
14:20:22 <frickler> +1
14:20:24 <ttx> #topic Open Discussion
14:20:31 <ttx> Anything else?
14:20:33 <opendevreview> Merged openstack/releases master: Release trove RC2 for 2025.1 Epoxy  https://review.opendev.org/c/openstack/releases/+/945796
14:21:12 <elodilles> maybe one thing
14:21:44 <elodilles> i did a quick check with the 'missing-releases' command
14:22:06 <elodilles> and did some edit in a WIP patch: https://review.opendev.org/c/openstack/releases/+/945630
14:22:50 <ttx> yeah sounds like a good idea
14:23:01 <elodilles> this will work for future deliverables
14:23:19 <elodilles> i mean, it works mostly already for epoxy deliverables
14:23:42 <elodilles> but this fix still has some false negative warnings
14:24:13 <elodilles> (deliverables released 2024 and early this year)
14:24:29 <elodilles> and does not work at all for old releases
14:24:54 <elodilles> does anyone use this command for checking old releases' deliverables?
14:25:07 <fungi> is this for the - vs _ in tarballs? (not where i can easily look at the patch atm)
14:25:10 <elodilles> should we have a better solution, or is this acceptable?
14:25:21 <elodilles> fungi: mostly that
14:26:13 <elodilles> (_ instead of - or . in tarballs and _ instead of - in wheel names)
14:27:03 <fungi> i'll take a look once i'm back to my workstation in a bit, but it should be generally safe to check for normalized and non-normalized forms and then consider it satisfactory as long as at least one exists
14:27:21 <frickler> I wouldn't object to a more flexible solution, but I'm also fine going forward with the simple approach
14:27:32 <frickler> fungi: it only checks for the new variant afaict
14:27:55 <elodilles> yes, only the new way
14:28:00 <fungi> ah, yeah then that's going to complain about a lot of stuff prior to mid-january
14:29:02 <elodilles> fungi: fortunately in epoxy we don't have many such release (~8-10 or so)
14:29:02 <fungi> i guess it's mostly a question as to what level of tolerance you have for manually filtering out older false-negatives
14:29:17 <elodilles> yes o:)
14:30:28 <frickler> I have another question which I wrote earlier but don't remember seeing an answer: can 2025.2 be switched to development already or does it need to wait for the release last week? we already updated -manuals, so the current state is a bit inconsistent. asking because of https://review.opendev.org/c/openstack/releases/+/945183 primarily
14:30:52 <frickler> eh, s/last/next/
14:31:26 <elodilles> frickler: afaik we usually set <next series> as in 'development' state at release day
14:31:41 <elodilles> though master is now already Flamingo
14:32:12 <elodilles> but it's better if teams focus on Epoxy in the last couple of days o:)
14:32:41 <frickler> well obviously the sdk team has already switched focus a while ago ;)
14:33:03 <elodilles> the possibility is there :)
14:33:21 <ttx> yeah it does not matter that much
14:33:33 <ttx> anything else before we close the meeting?
14:33:39 <elodilles> nothing else from me
14:34:22 <fungi> i got nothin'
14:34:36 * frickler neither
14:35:22 <ttx> #endmeeting