14:00:57 <elodilles> #startmeeting releaseteam
14:00:57 <opendevmeet> Meeting started Fri Aug 29 14:00:57 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:57 <opendevmeet> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
14:00:57 <opendevmeet> The meeting name has been set to 'releaseteam'
14:01:11 <elodilles> Ping list: release-team elod
14:01:14 <ttx> o/
14:01:26 <elodilles> hi ttx o/
14:01:39 <elodilles> #link https://etherpad.opendev.org/p/flamingo-relmgt-tracking
14:01:48 <ttx> Somewhere between Brussels and Paris
14:01:55 <elodilles> nice :]
14:02:08 <elodilles> what is the current speed of the train? is that TGV? :]
14:02:59 <elodilles> meanwhile, we are @ L312
14:03:42 <elodilles> and let's not wait as i think it will be just the two of us on this meeting
14:04:01 <elodilles> #topic Review task completion
14:04:21 <ttx> currently goin 4 km/h depressingly
14:04:55 <elodilles> :S sorry to hear that :S at least there won't be cellphone handover issues o:)
14:05:07 <elodilles> fingers crossed :D
14:05:27 <elodilles> 1st task was:     Process any remaining library freeze exception. (all)
14:05:39 <elodilles> #link https://review.opendev.org/q/topic:flamingo-final-non-client-libs+is:open
14:06:07 <elodilles> the last remaining patch is
14:06:11 <elodilles> #link https://review.opendev.org/c/openstack/releases/+/957695
14:06:23 <elodilles> heat-translator has a broken gate :/
14:06:57 <elodilles> we have to follow up this next week
14:07:20 <ttx> hmm
14:07:34 <ttx> do we need the gate fixed before making the tag?
14:08:05 <elodilles> it would be better i think
14:08:17 <elodilles> otherwise a fix needs to be cherry picked
14:08:30 <ttx> Obviously would be better
14:08:30 <elodilles> and there is a workaround patch already afaik
14:08:48 <elodilles> i will try to track this next week
14:09:05 <ttx> ok
14:09:06 <ttx> let's keep an eye on it, I'll add a followup task
14:09:08 <elodilles> and if we won't be able to do that, then probably need to tag the current patch
14:09:22 <elodilles> i've added a task to next week with my name on it
14:09:29 <elodilles> ttx: ^^^
14:09:59 <elodilles> 2nd task was:     Ensure that all new-release patches in requirements repository for the library releases are merged. (all)
14:10:09 <elodilles> #link https://review.opendev.org/q/project:openstack/requirements+branch:master+is:open+topic:new-release
14:10:24 <ttx> ok
14:10:31 <elodilles> we are mostly covered with this,
14:10:54 <elodilles> had an issue with oslo.service, that broke heat's gate
14:11:27 <elodilles> but thanks to tkajinam it's fixed in heat so oslo.service's upper constraint version bump is on the gate right now
14:12:53 <ttx> ok we seem all set on that second task
14:13:03 <elodilles> though we have to keep an eye on this in case there will be further new releases
14:13:27 <elodilles> otherwise yes, we seem to be good with this so far
14:13:49 <elodilles> 3rd task:     Propose autoreleases for cycle-with-intermediary client libraries. (elod)
14:13:57 <elodilles> #link https://review.opendev.org/q/topic:flamingo-milestone-3
14:14:42 <elodilles> i've gone through the open patches (without response from team)
14:15:05 <elodilles> and added procedural PTL-Approved+1's
14:15:16 <elodilles> so these are waiting for 2nd core reviews
14:15:17 <ttx> OK I can push them through on Monday
14:15:27 <elodilles> ttx: sounds perfect o/
14:15:30 <elodilles> thanks in advance
14:16:08 <elodilles> note: there is only one where the team commented they are waiting for some patch to merge
14:16:26 <elodilles> but that is good
14:16:35 <ttx> ok
14:16:41 <elodilles> 4th task:     Evaluate any non-client libraries that did not have any change merged over the cycle to see if it is time to transition them to the independent release model if applicable (ttx)
14:16:51 <elodilles> "    No good candidate"
14:17:06 <elodilles> ^^^ that's your comment, right?
14:17:52 <ttx> yes
14:18:06 <elodilles> +1
14:18:09 <ttx> There were a couple client libraries but those are not good candidates
14:18:17 <elodilles> yepp
14:18:41 <elodilles> 5th task:     List cycle-with-intermediary deliverables that have not been released yet and send a separate email targeted to teams with such unreleased deliverables to remind them that they need to release before $rc1-deadline (ttx)
14:18:58 <ttx> The usual stragglers have been notified
14:19:44 <elodilles> #link https://lists.openstack.org/archives/list/openstack-discuss@lists.openstack.org/thread/PIT2XSTKXGCKCECYFNHT424T4JIOAD2R/
14:19:56 <elodilles> the mail you sent ^^^
14:21:17 <elodilles> I think we have to track this next week, too
14:21:52 <ttx> yeah next week is the "check if those were updated any recently" task
14:22:23 <elodilles> ah, yepp, there is a task for that
14:22:27 <elodilles> thanks
14:22:46 <elodilles> or is there?
14:24:28 <elodilles> well, there is the task that somewhat overlaps: 'list cycle-with-intermediery deliverables that have not been refreshed in the last 2 months [..]'
14:25:18 <ttx> right
14:25:23 <ttx> tat's the one
14:25:34 <elodilles> okay
14:25:43 <elodilles> 6th task:     On Friday, remind the requirements team to freeze changes to openstack/requirements by applying -2 to all open patches. Ensure that reviewers do not approve changes created by the proposal bot, but do approve changes for new OpenStack deliverable releases. (elod)
14:26:45 <elodilles> well, let's do it now: prometheanfire tonyb ^^^ fyi, we are at THAT phase of the cycle ^^^ (Requirements Freeze)
14:27:31 <elodilles> otherwise we still have a lot of non-client libraries to merge on Monday
14:27:54 <ttx> yes
14:28:46 <elodilles> so those will have 'new-release' patches that should be merged
14:29:16 <elodilles> and we will see whether we will have RFEs coming from teams
14:29:55 <elodilles> ok, let's move on to the last task
14:30:01 <elodilles> 7th task:     check if 2026.1 Gazpacho supported runtime patch / zuul job templates are ready (task from week R-7) (elod)
14:30:09 <elodilles> #info supported runtimes: https://review.opendev.org/c/openstack/governance/+/957199
14:30:13 <elodilles> this has merged ^^^
14:30:50 <elodilles> so we have supported runtimes carved in stone :)
14:31:16 <elodilles> #info zuul job templates: https://review.opendev.org/c/openstack/openstack-zuul-jobs/+/958616 && https://review.opendev.org/c/openstack/openstack-zuul-jobs/+/958190
14:31:27 <elodilles> and these have been prepared accordingly ^^^
14:31:57 <elodilles> these are not yet merged, but hopefully they will be, as stable/2025.2 branching will start next week
14:33:13 <elodilles> i'd appreciate if cores on openstack-zuul-jobs repo reviewed it soon, probably frickler has +2+W rights there o:)
14:33:35 <elodilles> (when he comes back next week)
14:33:54 <elodilles> okay, so that's all about tasks for this week
14:34:09 <elodilles> #topic 'Assign R-4 week tasks'
14:34:28 <elodilles> all taken, actually
14:34:33 <elodilles> \o/
14:34:43 <ttx> wooohoo!
14:34:44 <elodilles> #topic Review weekly countdown email
14:34:59 <ttx> my train moves fast at last
14:35:00 <elodilles> #link https://etherpad.opendev.org/p/relmgmt-weekly-emails
14:35:04 <elodilles> please review ^^^
14:36:56 <ttx> trouble loading it... working on it
14:39:01 <ttx> ok lgtm
14:39:24 <elodilles> cool thanks, just wanted to say to postpone this, but then it's not needed o:)
14:39:31 <elodilles> i'll send later on today
14:39:51 <elodilles> #topic Open Discussion
14:40:04 <elodilles> i have two topics
14:40:12 <elodilles> maybe start with this one:
14:40:24 <elodilles> #info (elod) futurist (independent) release: https://review.opendev.org/c/openstack/releases/+/958837
14:40:51 <elodilles> futurist is a library
14:41:10 <elodilles> so should have been released last week at latest
14:41:29 <elodilles> but it seems Herve and Takashi are OK to release it now
14:41:36 <elodilles> it's a bug fix release
14:42:03 <ttx> It's an independent release, so they release when they want really
14:42:24 <elodilles> yes, but if we release now, then it will be part of 2025.2 Flamingo o:)
14:42:39 <ttx> Like any other Python independent dependency
14:42:40 <ttx> right
14:42:41 <ttx> Reviewing
14:42:49 <elodilles> as we are just at the time of freezing requirements o:)
14:43:26 <elodilles> i tend to accept to release it, given that Herve and Takashi supporting it
14:44:07 <ttx> still loading...
14:45:06 <elodilles> it's a threading (eventlet removal) related bug fix
14:45:14 <elodilles> this is the content: https://review.opendev.org/c/openstack/futurist/+/958689
14:45:44 <ttx> OK reviewed
14:47:10 <elodilles> good. +2+W'd
14:47:39 <elodilles> i'll keep an eye on it's generated new-release requirements patch
14:47:56 <elodilles> and +2+W it ASAP if Zuul likes it
14:48:09 <elodilles> and the next/last topic
14:48:28 <elodilles> #info (elod) bug -> package name normalization issue (we had with oslo.utils at first, but now we have it with recent oslo.* releases): https://bugs.launchpad.net/octavia/+bug/2121578
14:48:38 <elodilles> octavia team reported it yesterday ^^^
14:49:14 <elodilles> so as i wrote above, it's the same we encountered on stable branches with oslo.utils
14:49:29 <elodilles> i'm still investigating what else could we do
14:50:16 <elodilles> as linked in the bug report Stephen already opened a github issue against setuptools:
14:50:21 <elodilles> #link https://github.com/pypa/setuptools/issues/5051
14:51:03 <elodilles> and i don't see yet how else we could make things work
14:51:14 <ttx> slow progress on that issue
14:51:19 <elodilles> yepp
14:52:05 <elodilles> i don't think we can do anything with it here on the meeting,
14:52:16 <elodilles> so it's just a heads up
14:52:29 <ttx> yeah... we could use fungi's eyes on it when he returns from PTO
14:54:13 <elodilles> it might affect multiple repositories we just haven't realized it yet
14:54:45 <fungi> having followed the problem, i don't know of any good solutions, but maybe we can come up with an ugly workaround
14:55:22 <elodilles> :S
14:55:58 <elodilles> anyway, i'm adding a task to next week with my name on it, to not forget about this
14:56:20 <ttx> ok
14:56:47 <fungi> it will probably affect a lot of libs over time, but only with older python
14:56:47 <elodilles> anything else to discuss?
14:57:27 <elodilles> fungi: grenade jobs seem to be the places where this probably will come up mostly :S
14:57:37 <fungi> yes
14:57:59 <fungi> we could posibly pin back setuptools there
14:58:18 <fungi> can't remember if it will help
14:58:46 <fungi> or rewrite/stream edit the metadata files for packages post-installl
14:58:47 <elodilles> i'm not sure, because there will be two kinds of names anyway (oslo_utils & oslo.utils)
14:59:07 <opendevreview> Merged openstack/releases master: Release futurist 3.2.1  https://review.opendev.org/c/openstack/releases/+/958837
14:59:25 <fungi> in theory grenade/devstack could adjust the metadata on disk
14:59:38 <elodilles> the latter sounds "better" (though uglier :S) workaround
15:00:13 <elodilles> let's discuss this next week as we are running out of time
15:00:23 <elodilles> thanks ttx and fungi o/
15:00:24 <ttx> ++
15:00:26 <fungi> sounds good
15:00:28 <elodilles> #endmeeting