Friday, 2025-08-22

opendevreviewTakashi Kajinami proposed openstack/releases master: Release final oslo.privsep for 2025.2 Flamingo  https://review.opendev.org/c/openstack/releases/+/95772301:06
opendevreviewTakashi Kajinami proposed openstack/releases master: Release oslo.cache for stable/2024.1  https://review.opendev.org/c/openstack/releases/+/95448101:20
opendevreviewTakashi Kajinami proposed openstack/releases master: Release oslo.config for stable/2024.1  https://review.opendev.org/c/openstack/releases/+/95448201:20
opendevreviewTakashi Kajinami proposed openstack/releases master: Release oslo.config for stable/2024.1  https://review.opendev.org/c/openstack/releases/+/95448201:21
opendevreviewTakashi Kajinami proposed openstack/releases master: Release oslo.cache for stable/2024.1  https://review.opendev.org/c/openstack/releases/+/95448101:21
*** clarkb is now known as Guest2471807:46
opendevreviewElod Illes proposed openstack/releases master: Release final neutron-lib for 2025.2 Flamingo  https://review.opendev.org/c/openstack/releases/+/95770409:00
*** jbernard_ is now known as jbernard11:15
opendevreviewTakashi Kajinami proposed openstack/releases master: Release final oslo.cache for 2025.2 Flamingo  https://review.opendev.org/c/openstack/releases/+/95771411:51
opendevreviewBrian Haley proposed openstack/releases master: Release neutron for stable/2024.1  https://review.opendev.org/c/openstack/releases/+/95447213:09
*** Guest24718 is now known as clarkb13:47
ttxo/14:01
ttx#startmeeting releaseteam14:01
opendevmeetMeeting started Fri Aug 22 14:01:33 2025 UTC and is due to finish in 60 minutes.  The chair is ttx. Information about MeetBot at http://wiki.debian.org/MeetBot.14:01
opendevmeetUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.14:01
opendevmeetThe meeting name has been set to 'releaseteam'14:01
ttxOur agenda is down at:14:01
ttx#link https://etherpad.opendev.org/p/flamingo-relmgt-tracking#L29614:02
ttxPing list: release-team elod14:02
ttxAnyone here for the release team meeting?14:03
elodilleso/14:03
ttxAh!14:03
elodilleshi, sorry, i'm here :]14:04
ttxAlright let's get started14:04
ttx#topic Review task completion14:04
ttx- Propose autoreleases for cycle-with-intermediary libraries (excluding client libraries) which had commits that have not been included in a release. (elod)14:04
ttx#link https://review.opendev.org/q/topic:flamingo-final-non-client-libs14:04
elodillesi went through the open patches (without response from team :'(14:05
elodillestoday morning, and reviewed them14:06
ttxHmm, do you think I should approve them today, or wait next week?14:06
elodillesadded procedural PTL-Approved+1 for them14:06
ttxit is a bit of a Friday14:06
elodillesttx: both works for me14:06
elodilleswon't you be traveling next week? :-o14:06
ttxOK I'll do a pass on them on Monday14:06
ttxI'm traveling with a laptop14:07
ttx- Send weekly email (ttx)14:07
ttxwill do in a minute14:07
fricklerlate o/14:07
ttx#topic Assign R-5 week tasks14:08
ttxok all assigned I think14:09
ttx#topic Review weekly countdown email14:09
ttx#link https://etherpad.opendev.org/p/relmgmt-weekly-emails14:09
fricklerlgtm14:10
ttxalright will send shortly after meet14:10
ttx#topic Open Discussion14:11
ttxWanted to discuss a bunch of old patches that sit in our review dashboard14:11
ttxhttps://review.opendev.org/c/openstack/releases/+/952525 14:12
ttxhttps://review.opendev.org/c/openstack/releases/+/952528 and https://review.opendev.org/c/openstack/releases/+/95252914:13
ttxThose three are old 2023.2-last patches14:13
elodillesyepp14:13
elodillesi think these should have been merged already ages ago :/14:13
elodilleshttps://review.opendev.org/q/topic:2023-2-last+is:open14:14
elodillesbut never got response from teams that they are OK with this14:14
elodillesthere's no deadline in the patches though14:14
ttxOK how about we reply setting a deadline14:15
ttx(and recheck the -1 one)14:15
elodillessounds OK to me14:15
ttxI'll do that after meet14:15
ttxunless someone beats me to it14:15
ttxthen: https://review.opendev.org/c/openstack/releases/+/95220114:16
fricklerwhat would happen if we just abandon them? who would care?14:16
ttxthe 2023.2 ones?14:16
ttxI think we need the tag in for some reason14:16
ttx(to prep for branch removal ?_14:16
ttxThe Mistral release one is missing PTL+114:17
elodillesfrickler: as far as i understand those patches are needed (explained by gmaan in the past)14:17
fricklerfor mistral can try to mail the ptl or ping amorin (not here but maybe in opendev or so)14:18
ttxamorin approved them but has no ptl+1 right14:18
fricklerbut he is in the same company afaict14:18
ttxright14:18
ttxhttps://review.opendev.org/c/openstack/releases/+/94129014:19
frickleroh, wait amorin will be PTL next cycle, too14:19
ttxStill waiting on https://review.opendev.org/c/openstack/project-config/+/94113814:19
fricklerso maybe we can just accept his +114:19
ttxyeah... I would do that and unblock them14:20
ttxwill add14:20
elodilles+114:20
ttxthen one of you can +2a14:20
fricklerfor freezer need to remind noonedeadpunk of it14:20
frickler(which is hereby done ;)14:20
frickler(just for reference https://opendev.org/openstack/election/src/branch/master/candidates/2026.1/Mistral/arnaud.morin@gmail.com)14:22
ttxthanks14:22
ttxthen we have a bunch of https://review.opendev.org/q/topic:%22caracal-stable%22+status:open patches stuck since mid-July14:22
elodillesthese are convenience patches ^^^14:22
ttxyeah I would drop them14:22
elodillesto prepare for caracal to move Unmaintained14:22
elodillesyes, probably we have waited enough14:23
elodilleslet me abandon them14:23
ttxI'd rather have a clean deck before we enter final release period14:23
elodillesfor the recored, there are a couple that just got PTL-Approved+114:23
elodillesso those can be merged14:23
frickler+1 to abandoning if no feedback14:24
ttxonly 2 left:14:24
ttxhttps://review.opendev.org/c/openstack/releases/+/94397514:24
ttxbeen some time since we last heard of Kacper14:24
ttxWe can abandon it, he can un-abandon it if he wants to work on it again14:24
fricklerack, hberaud also doesn't seem to be online14:25
frickleriirc it was a colleague of his?14:25
ttxyes14:25
ttxthat leaves https://review.opendev.org/c/openstack/releases/+/94879014:25
fricklers/it was/they were/14:26
ttxfor which nobody has a strong opinion, I guess14:26
elodilleswell, i have the opinion documented there and frickler too o:)14:26
fricklerah, that one, yeah ... :-/14:27
ttxHey don;t look at me, I voted14:27
elodillesi don't think i will start the process right after the release, to be clear14:27
ttxelodilles: we established that release-core people can vote on their patches, given that there is only 3 active of us14:28
fricklerlet's make a compromise of two weeks instead of 4? ;)14:28
fricklernot sure how that would overlap with the ptg though14:29
elodillessorry, let me correct myself: i won't be start the transition process before 2025.2 Flamingo release <- this would be needed to be able to EOL at the time of release date14:29
elodillesso i'll start the process right after the Flamingo release anyway14:30
elodillesi just wanted to have the deadline more reasonable14:30
frickleroh, and we have a 4 week waiting period, right?14:30
elodillesfrickler: well, 2-4 week, and usually teams realize at that time that they need a final release :S14:31
elodillesi agree that we should be more strict with the deadline though14:32
ttxelodilles: I think it makes sense14:32
fricklerptg is 27-31. so maybe if the set the deadline to the friday before, 2025-10-24?14:33
elodillesfrickler: sounds a bit better than Flamingo date14:33
elodilleslet me update the patch14:34
* ttx waits14:35
opendevreviewElod Illes proposed openstack/releases master: Update 2024.1 Caracal's transition date  https://review.opendev.org/c/openstack/releases/+/94879014:36
elodillessorry, had to add signature to be able to edit :S14:36
elodilles(old patch)14:36
elodilles* signed-off-by14:36
fricklercommit message doesn't match completely any more, do you want to amend that, too?14:36
elodillesbut there it is ^^^14:36
frickler3 instead of 4 weeks14:37
opendevreviewElod Illes proposed openstack/releases master: Update 2024.1 Caracal's transition date  https://review.opendev.org/c/openstack/releases/+/94879014:37
elodillesthere ^^^14:37
frickler+2.5, thx14:38
elodillesthanks too14:38
fricklerfreezer p-c patch just got updated, too :)14:39
ttxalright we have a winner14:40
ttxThat is all I had!14:40
ttxanything else before we end the meeting?14:40
elodillesjust a reminder: these are also ready for a 2nd core review -> https://review.opendev.org/q/topic:caracal-stable+is:open14:41
elodillesrest are abandoned14:41
elodillesso the dashboard is a bit less messy now :)14:42
elodillesthanks ttx o/14:42
elodillesnothing else from me14:42
ttxyeah I thought I would not approve stable/* patches on a Friday14:42
fungispeaking of travel, i'm on vacation all next week through wednesday the following week, so reach out in #opendev or #openstack-infra if you need something since i may be slow to respond directly until i get home14:42
ttxthanks fungi! enjoy the time off14:42
fungiwill do my best14:42
ttx#endmeeting14:42
opendevmeetMeeting ended Fri Aug 22 14:42:54 2025 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)14:42
opendevmeetMinutes:        https://meetings.opendev.org/meetings/releaseteam/2025/releaseteam.2025-08-22-14.01.html14:42
opendevmeetMinutes (text): https://meetings.opendev.org/meetings/releaseteam/2025/releaseteam.2025-08-22-14.01.txt14:42
opendevmeetLog:            https://meetings.opendev.org/meetings/releaseteam/2025/releaseteam.2025-08-22-14.01.log.html14:42
ttxThanks everyone!14:43
elodillesfungi: thanks for the heads up and have a nice vacation! you deserve it! :)14:43
fungithanks14:43
fungi!14:43
opendevreviewMerged openstack/releases master: Update 2024.1 Caracal's transition date  https://review.opendev.org/c/openstack/releases/+/94879015:09
opendevreviewMerged openstack/releases master: Switch Freezer to use launchpad  https://review.opendev.org/c/openstack/releases/+/94129015:34
fricklerelodilles: ttx: forgot to mention https://review.opendev.org/c/openstack/releases/+/958221 needed for elections to proceed15:57
frickleralso https://review.opendev.org/c/openstack/releases/+/958225 is a bit late, but maybe still useful15:59
opendevreviewMerged openstack/releases master: Tag governance 0.19.0 for Aug 2025 elections  https://review.opendev.org/c/openstack/releases/+/95822116:21
elodillesrelease-team: just a heads up, that ironic team is about to retire 'metalsmith', but we still have it listed among Flamingo deliverables :S so probably next week we have to deal with that as soon as possible17:40
gmaanhumm oslo.policy is released and as usual i missed the train to add something but never mind will do it  nova and can move to oslo.policy in next release18:27
JayFelodilles: Do I need anything beyond this? I'm happy to do the legwork that's needed. Jay Faulkner proposed openstack/governance master: Retire metalsmith project from bare metal program  https://review.opendev.org/c/openstack/governance/+/95829718:33
JayFsorta thing that probably wouldn't be done last minute if I hadn't been out six weeks18:34
JayFugh, we cut a release of it in this cycle :( I wish we hadn't done that. If possible we should unpublish that release; I'd be stunned if it was functional.18:41
JayFI was going to remove the empty deliverables file... but it wasn't empty, so I'm unsure how to continue. I'm really, really surprised our release liasons didn't -1 that patch.18:41
opendevreviewGhanshyam proposed openstack/releases master: [manila-tempest-plugin] Tag 2023.2-last  https://review.opendev.org/c/openstack/releases/+/95252519:09
clarkbunreleasing things on pypi should be done with care. Particularly if it works at all19:10
clarkb(if it doesn't work at all or is a security concern the math changes)19:10
JayFThis is also intersecting with "nobody has used this to our knowledge since tripleo died" 19:28
JayFso the question of how much it matters applies, too19:28
JayFI'm not even familiar enough with metalsmith to know how to trivially hello-world it.19:28
JayFI'm sure I could figure it out, but every hour I spend trying to see if that works is an hour I could be spending on projects that people /do/ care about19:29
clarkbin that case it probably doesn't hurt to just leave it and stop producing new releases20:01
clarkbI wouldn't go out of our eway to delete anything if we think no one is using it anyway20:01
elodillesJayF: i think the governance patch will do. that should be approved as soon as possible. i don't have a strong opinion about keeping or deleting metalsmith from Flamingo deliverables. (i don't know which is more confusing: whether we keep it in the list or delete it now that it was released)20:19
JayFlike I said above, I think I'm overthinking it. I doubt anyone cares, and if they do, I suspect they git-care not pypi-care :D 20:20
elodillesbut based on what you say, probably it's not a big deal anyway20:20
elodillesand of course, it's better this came up now and not at release day o:)20:26
JayFyeah, I got back from my sabbat, saw the CI was failing, and suggested the retirement20:27
elodillesjust in time then :)20:28

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