Friday, 2025-08-29

opendevreviewBalazs Gibizer proposed openstack/releases master: Release futurist 3.2.1  https://review.opendev.org/c/openstack/releases/+/95883708:11
opendevreviewMerged openstack/releases master: Release final python-cyborgclient for 2025.2 Flamingo  https://review.opendev.org/c/openstack/releases/+/95840310:47
fricklerelodilles: ttx: sorry, can't make it to the meeting, will followup later today11:04
opendevreviewMerged openstack/releases master: Release final python-venusclient for 2025.2 Flamingo  https://review.opendev.org/c/openstack/releases/+/95841911:07
elodillesfrickler: ACK, no problem, thanks for telling it in advance11:31
elodillesactually afaik, there won't be there anyone else11:34
elodillesbut i'll hold the meeting anyway, to have it logged11:35
opendevreviewMerged openstack/releases master: Swift: create feature/threaded branch  https://review.opendev.org/c/openstack/releases/+/95880711:49
ttxelodilles: I'll try to join if I can get network coverage on the train11:53
elodillesthanks o:)12:10
elodilles(on the other hand, feel free to skip it if it would not be comfortable for you, we can discuss things later / next week if needed)12:11
elodilles#startmeeting releaseteam14:00
opendevmeetMeeting 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
opendevmeetUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.14:00
opendevmeetThe meeting name has been set to 'releaseteam'14:00
elodillesPing list: release-team elod14:01
ttxo/14:01
elodilleshi ttx o/14:01
elodilles#link https://etherpad.opendev.org/p/flamingo-relmgt-tracking14:01
ttxSomewhere between Brussels and Paris14:01
elodillesnice :]14:01
elodilleswhat is the current speed of the train? is that TGV? :]14:02
elodillesmeanwhile, we are @ L31214:02
elodillesand let's not wait as i think it will be just the two of us on this meeting14:03
elodilles#topic Review task completion14:04
ttxcurrently goin 4 km/h depressingly14:04
elodilles:S sorry to hear that :S at least there won't be cellphone handover issues o:)14:04
elodillesfingers crossed :D14:05
elodilles1st task was:     Process any remaining library freeze exception. (all)14:05
elodilles#link https://review.opendev.org/q/topic:flamingo-final-non-client-libs+is:open14:05
elodillesthe last remaining patch is14:06
elodilles#link https://review.opendev.org/c/openstack/releases/+/95769514:06
elodillesheat-translator has a broken gate :/14:06
elodilleswe have to follow up this next week14:06
ttxhmm14:07
ttxdo we need the gate fixed before making the tag?14:07
elodillesit would be better i think14:08
elodillesotherwise a fix needs to be cherry picked14:08
ttxObviously would be better14:08
elodillesand there is a workaround patch already afaik14:08
elodillesi will try to track this next week14:08
ttxok14:09
ttxlet's keep an eye on it, I'll add a followup task14:09
elodillesand if we won't be able to do that, then probably need to tag the current patch14:09
elodillesi've added a task to next week with my name on it14:09
elodillesttx: ^^^14:09
elodilles2nd task was:     Ensure that all new-release patches in requirements repository for the library releases are merged. (all)14:09
elodilles#link https://review.opendev.org/q/project:openstack/requirements+branch:master+is:open+topic:new-release14:10
ttxok14:10
elodilleswe are mostly covered with this,14:10
elodilleshad an issue with oslo.service, that broke heat's gate14:10
elodillesbut thanks to tkajinam it's fixed in heat so oslo.service's upper constraint version bump is on the gate right now14:11
ttxok we seem all set on that second task14:12
elodillesthough we have to keep an eye on this in case there will be further new releases14:13
elodillesotherwise yes, we seem to be good with this so far14:13
elodilles3rd task:     Propose autoreleases for cycle-with-intermediary client libraries. (elod)14:13
elodilles#link https://review.opendev.org/q/topic:flamingo-milestone-314:13
elodillesi've gone through the open patches (without response from team)14:14
elodillesand added procedural PTL-Approved+1's14:15
elodillesso these are waiting for 2nd core reviews14:15
ttxOK I can push them through on Monday14:15
elodillesttx: sounds perfect o/14:15
elodillesthanks in advance14:15
elodillesnote: there is only one where the team commented they are waiting for some patch to merge14:16
elodillesbut that is good14:16
ttxok14:16
elodilles4th 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
elodilles"    No good candidate"14:16
elodilles^^^ that's your comment, right?14:17
ttxyes14:17
elodilles+114:18
ttxThere were a couple client libraries but those are not good candidates14:18
elodillesyepp14:18
elodilles5th 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
ttxThe usual stragglers have been notified14:18
elodilles#link https://lists.openstack.org/archives/list/openstack-discuss@lists.openstack.org/thread/PIT2XSTKXGCKCECYFNHT424T4JIOAD2R/14:19
elodillesthe mail you sent ^^^14:19
elodillesI think we have to track this next week, too14:21
ttxyeah next week is the "check if those were updated any recently" task14:21
elodillesah, yepp, there is a task for that14:22
elodillesthanks14:22
elodillesor is there?14:22
elodilleswell, there is the task that somewhat overlaps: 'list cycle-with-intermediery deliverables that have not been refreshed in the last 2 months [..]'14:24
ttxright14:25
ttxtat's the one14:25
elodillesokay14:25
elodilles6th 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:25
elodilleswell, let's do it now: prometheanfire tonyb ^^^ fyi, we are at THAT phase of the cycle ^^^ (Requirements Freeze)14:26
elodillesotherwise we still have a lot of non-client libraries to merge on Monday14:27
ttxyes14:27
elodillesso those will have 'new-release' patches that should be merged14:28
elodillesand we will see whether we will have RFEs coming from teams14:29
elodillesok, let's move on to the last task14:29
elodilles7th task:     check if 2026.1 Gazpacho supported runtime patch / zuul job templates are ready (task from week R-7) (elod)14:30
elodilles#info supported runtimes: https://review.opendev.org/c/openstack/governance/+/95719914:30
elodillesthis has merged ^^^14:30
elodillesso we have supported runtimes carved in stone :)14:30
elodilles#info zuul job templates: https://review.opendev.org/c/openstack/openstack-zuul-jobs/+/958616 && https://review.opendev.org/c/openstack/openstack-zuul-jobs/+/95819014:31
elodillesand these have been prepared accordingly ^^^14:31
elodillesthese are not yet merged, but hopefully they will be, as stable/2025.2 branching will start next week14:31
elodillesi'd appreciate if cores on openstack-zuul-jobs repo reviewed it soon, probably frickler has +2+W rights there o:)14:33
elodilles(when he comes back next week)14:33
elodillesokay, so that's all about tasks for this week14:33
elodilles#topic 'Assign R-4 week tasks'14:34
elodillesall taken, actually14:34
elodilles\o/14:34
ttxwooohoo!14:34
elodilles#topic Review weekly countdown email14:34
ttxmy train moves fast at last14:34
elodilles#link https://etherpad.opendev.org/p/relmgmt-weekly-emails14:35
elodillesplease review ^^^14:35
ttxtrouble loading it... working on it14:36
ttxok lgtm14:39
elodillescool thanks, just wanted to say to postpone this, but then it's not needed o:)14:39
elodillesi'll send later on today14:39
elodilles#topic Open Discussion14:39
elodillesi have two topics14:40
elodillesmaybe start with this one:14:40
elodilles#info (elod) futurist (independent) release: https://review.opendev.org/c/openstack/releases/+/95883714:40
elodillesfuturist is a library14:40
elodillesso should have been released last week at latest14:41
elodillesbut it seems Herve and Takashi are OK to release it now14:41
elodillesit's a bug fix release14:41
ttxIt's an independent release, so they release when they want really14:42
elodillesyes, but if we release now, then it will be part of 2025.2 Flamingo o:)14:42
ttxLike any other Python independent dependency14:42
ttxright14:42
ttxReviewing14:42
elodillesas we are just at the time of freezing requirements o:)14:42
elodillesi tend to accept to release it, given that Herve and Takashi supporting it14:43
ttxstill loading...14:44
elodillesit's a threading (eventlet removal) related bug fix14:45
elodillesthis is the content: https://review.opendev.org/c/openstack/futurist/+/95868914:45
ttxOK reviewed14:45
elodillesgood. +2+W'd14:47
elodillesi'll keep an eye on it's generated new-release requirements patch14:47
elodillesand +2+W it ASAP if Zuul likes it14:47
elodillesand the next/last topic14:48
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/212157814:48
elodillesoctavia team reported it yesterday ^^^14:48
elodillesso as i wrote above, it's the same we encountered on stable branches with oslo.utils14:49
elodillesi'm still investigating what else could we do14:49
elodillesas linked in the bug report Stephen already opened a github issue against setuptools:14:50
elodilles#link https://github.com/pypa/setuptools/issues/505114:50
elodillesand i don't see yet how else we could make things work14:51
ttxslow progress on that issue14:51
elodillesyepp14:51
elodillesi don't think we can do anything with it here on the meeting,14:52
elodillesso it's just a heads up14:52
ttxyeah... we could use fungi's eyes on it when he returns from PTO14:52
elodillesit might affect multiple repositories we just haven't realized it yet 14:54
fungihaving followed the problem, i don't know of any good solutions, but maybe we can come up with an ugly workaround14:54
elodilles:S14:55
elodillesanyway, i'm adding a task to next week with my name on it, to not forget about this14:55
ttxok14:56
fungiit will probably affect a lot of libs over time, but only with older python14:56
elodillesanything else to discuss?14:56
elodillesfungi: grenade jobs seem to be the places where this probably will come up mostly :S14:57
fungiyes14:57
fungiwe could posibly pin back setuptools there14:57
fungican't remember if it will help14:58
fungior rewrite/stream edit the metadata files for packages post-installl14:58
elodillesi'm not sure, because there will be two kinds of names anyway (oslo_utils & oslo.utils)14:58
opendevreviewMerged openstack/releases master: Release futurist 3.2.1  https://review.opendev.org/c/openstack/releases/+/95883714:59
fungiin theory grenade/devstack could adjust the metadata on disk14:59
elodillesthe latter sounds "better" (though uglier :S) workaround14:59
elodilleslet's discuss this next week as we are running out of time15:00
elodillesthanks ttx and fungi o/15:00
ttx++15:00
fungisounds good15:00
elodilles#endmeeting15:00
opendevmeetMeeting ended Fri Aug 29 15:00:28 2025 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:00
opendevmeetMinutes:        https://meetings.opendev.org/meetings/releaseteam/2025/releaseteam.2025-08-29-14.00.html15:00
opendevmeetMinutes (text): https://meetings.opendev.org/meetings/releaseteam/2025/releaseteam.2025-08-29-14.00.txt15:00
opendevmeetLog:            https://meetings.opendev.org/meetings/releaseteam/2025/releaseteam.2025-08-29-14.00.log.html15:00
ttxThanks elodilles !15:00
elodillesthanks too o/15:00
elodillesand save travels ttx o/15:01
elodilles+ nice further vacation fungi o/15:01
fungithanks!15:01
clarkbit would be nice if pypi either automatically started serving files with normalized filenames or allowed package maintainers to change hte name of existing packages as long as they produced an equivalent name and content doesn't change16:19
*** gmaan is now known as gmaan_afk19:30
tonybelodilles: thanks for the prod.  21:43
*** gmaan_afk is now known as gmaan23:20

Generated by irclog2html.py 4.0.0 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!