Friday, 2025-07-04

*** ykarel__ is now known as ykarel04:10
ttx#startmeeting releaseteam14:00
opendevmeetMeeting started Fri Jul  4 14:00:32 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
opendevmeetUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.14:00
opendevmeetThe meeting name has been set to 'releaseteam'14:00
ttxPing list: release-team elod14:01
opendevreviewDmitriy Rabotyagov proposed openstack/releases master: Release OpenStack-Ansible 2024.2  https://review.opendev.org/c/openstack/releases/+/95413214:03
ttxAnyone else here for the release team meeting?14:03
frickler\o14:04
ttxo/14:04
ttxOK let's get started14:04
ttx#link https://etherpad.opendev.org/p/flamingo-relmgt-tracking#L18314:04
ttxOur agenda for today ^14:04
ttx#topic Review task completion14:05
ttx- Generate release requests for all cycle-with-intermediary libraries which had changes, but did not release since milestone-1 (elod)14:05
ttxThis was done14:05
ttx#link https://review.opendev.org/q/topic:flamingo-milestone-214:05
ttxA bunch are waiting for a second review, we can clear out the exceptions next week14:06
ttx- Catch if there are acl issues in newly created repositories (ttx)14:06
ttxDone, no issue reported14:07
ttx- Propose convenience releases for 2024.1 Caracal (elod)14:07
ttxNot sure about the status of that one.. checking...14:07
fricklerI don't remember seeing those14:08
ttxme neither14:08
ttxI'll push it back to next week14:08
ttx- Send emails to Cinder, Glance, Telemetry and Barbican teams about deliverables defined in governance but not in deliverable files (ttx)14:09
ttxThis was done.. only the Telemetry team replied.14:09
ttxfor the others it's not their first time on the list, so I assume we can ignore them14:09
ttx- Open up discussion with TC about why is Monasca still being listed with deliverables in governance (elod)14:10
ttxThis was mentioned on https://review.opendev.org/c/openstack/governance/+/95367114:10
ttxOne issue here is that our scripts do not read off the inactive list14:11
ttx(to be fair it's not very machine-readable)14:11
ttxso I guess we'll continue to wait for that inconsistency to be resolved14:12
ttx- Send weekly email (ttx)14:12
ttxI'll do that shortly after this meeting14:12
ttx#topic Assign R-12 week tasks14:12
ttxall assigned14:14
ttx#topic Review weekly countdown email14:14
ttx#link https://etherpad.opendev.org/p/relmgmt-weekly-emails14:14
fricklerthere's a stray word in L9 (applied strikethrough)14:16
ttxnice catch!14:16
ttxWill send in a minute14:17
ttx#topic Open Discussion14:17
ttxAnything else?14:17
fricklerthe issue we had with oslo.utils for 2024.2 now also affects an 2024.1 release (oslo.messaging I think)14:18
frickler#link https://review.opendev.org/c/openstack/requirements/+/95342014:18
fricklerone possible workaround that was mentioned would be to change references from e.g. oslo.utils to oslo_utils in constraints and maybe consuming projects' requirements14:19
fricklerI'm not sure whether that's a valid move for stable branches, but it might be that we have no other choice14:20
ttxthat might be worth a try14:20
ttxI think it's OK on stable branches, as it is a move to keep them working14:20
ttxI would love to have fungi 's eyes on that workaround but he is on holiday today14:23
ttxso probably a discussion to continue next week14:23
ttxanything else?14:23
fricklernot from me I think14:24
ttxalright let's close this then14:24
ttxthanks frickler !14:24
ttx#endmeeting14:24
opendevmeetMeeting ended Fri Jul  4 14:24:52 2025 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)14:24
opendevmeetMinutes:        https://meetings.opendev.org/meetings/releaseteam/2025/releaseteam.2025-07-04-14.00.html14:24
opendevmeetMinutes (text): https://meetings.opendev.org/meetings/releaseteam/2025/releaseteam.2025-07-04-14.00.txt14:24
opendevmeetLog:            https://meetings.opendev.org/meetings/releaseteam/2025/releaseteam.2025-07-04-14.00.log.html14:24
fungii can take a look14:24
fungiadjusting the package names in a stable branch constraints file doesn't seem like it should cause any problems, as long as they normalize to the same string14:25
fungisadly we can't easily pin setuptools in these cases (not until everyone's relying on build-system.requires in pyproject.toml) so have to make adjustments as its behavior changes14:27
fricklerwill an "oslo_utils==7.4.0" entry in upper-constraints.txt take effect if a project has "oslo.utils" in its requirements.txt? or will the latter suddenly be unconstrained? something to test for I guess14:29
fungiyes, they'll be treated the same by pip14:29
fungiso it should work as intended still14:30
fungipip normalizes all package names before performing comparisons14:30
fungithe problem we're running into is that we're querying metadata ourselves in some places and then not performing normalized matches14:30
fungiand tooling has decided to change whether it returns normized forms14:31

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