Friday, 2026-10-09

opendevreviewMerged openstack/releases master: Release placement for stable/2025.1  https://review.opendev.org/c/openstack/releases/+/99757506:51
opendevreviewMerged openstack/releases master: Release os-vif 5.3.0 version  https://review.opendev.org/c/openstack/releases/+/100844506:54
opendevreviewMerged openstack/releases master: Release os-vif 5.2.2 for stable/2026.2  https://review.opendev.org/c/openstack/releases/+/100874906:55
opendevreviewMerged openstack/releases master: Release os-vif 4.3.1 for stable/2026.1  https://review.opendev.org/c/openstack/releases/+/100874807:04
opendevreviewMerged openstack/releases master: python-openstackclient 10.4.0  https://review.opendev.org/c/openstack/releases/+/100591107:18
gthiemongeHi Folks, do you know if we're allowed to backport patches that update translatable strings (like https://review.opendev.org/c/openstack/octavia-dashboard/+/1004179) ? technically it would introduce a regression for i18n users until someone updates the translations09:08
elodillesgthiemonge: i *think* translation tools are running against all stable branches, but I'm not 100% sure. it's a valid concern. to be honest when we backport patches it sometimes happens that log messages are updated (even to unmaintained branches, where we probably don't have active translations running)... but you made me think now... this might be a valid concern... O.o11:23
gthiemongeelodilles: yeah and my main concern here is that the patch is not even a bugfix, it just updates some strings12:43
elodillesgthiemonge: to be clear, in the past we didn't accept doc / string update patches on stable branches, but that rule is long gone now and we tend to like up-to-date or better docs on stable branches as well o:)13:00
*** ykarel__ is now known as ykarel13:08
elodillesreminder: weekly meeting in 30 mins13:30
elodilles#startmeeting releaseteam14:00
opendevmeetMeeting started Fri Oct  9 14:00:37 2026 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-team14:00
elodilles#link https://etherpad.opendev.org/p/indri-relmgt-tracking14:00
elodilleso/14:00
elodillesokay, it seems that it's only me :) let's just hold the meeting to ship's log then. :]14:04
elodilles#topic Review task completion14:04
funginot only you, sorry14:04
elodillesoh, hello fungi \o/14:04
elodilles- Process any late or blocked release requests for deliverables for any branch (treating the new series branch as stable). (all)14:05
* fungi is here, just juggling multiple simultaneous discussions14:05
elodillesfungi: i feel you... :S14:05
elodillesso, we had a couple of releases already for Indri, and stable releases too14:06
elodillesi don't see any blocked release anymore14:06
fungiyeah, security advisory publication has resumed post-release and that's driving more release requests too14:06
elodillesfungi: +114:06
elodillesfungi: should we prepare more releases during next week?14:07
fungiwe held them off during release week, so there were more queued up14:07
elodillesbut those all are released already, right?14:07
fungii'll try to keep an eye out at least for security-related release requests during the ptg, but the vmt is trying really hard not to publish any advisories next week14:07
elodillesfungi: ACK14:08
elodillesokay, next task then14:08
fricklerlate o/14:08
elodilles- Coordinate with the Infrastructure team to swap out the previous cycle signing key and establish the new one for the starting cycle.(fungi)14:08
fungielodilles: i don't think all the changes for the mistral advisory yesterday have merged yet, though i'm still catching up14:08
elodilleshi frickler o/14:08
elodillesfungi: true, i saw stable/2025.1 patches still for mistral in gate queue14:09
fungii did merge the key rotation and then we exercised it, everything looked good14:09
fricklernew key was tested successfully, ack14:09
elodilles+114:09
elodillescool14:09
elodilles- Create the $series-relmgt-tracking etherpad. (elod)14:09
elodilles#link https://etherpad.opendev.org/p/indri-relmgt-tracking14:09
elodilleswe are already using it ^^^14:09
elodillesit's ready, please review when you have some time14:10
elodillesi've filled it based on the Relese Process Guide14:10
elodilles- Email PTLs directly one time to explain the use of the “[release][ptl]” email tag on the openstack-discuss list. (elod)14:11
elodilles(elod) i've sent the mail to all PTLs and release liaisons on Monday14:11
elodillesand the weekly mail task will come later, after the review14:11
elodillesso that's all about task completion review14:12
elodilles#topic Assign R-23 week tasks14:12
elodillesit's mostly releated to 2025.1 Epoxy transition to Unmaintained14:12
elodillesso i've added my name14:12
elodilless/mostly/completely/ o:)14:13
fungithanks! if you need help with any of that let me know, though i expect we'll all be pulled in a lot of directions next week14:13
elodillesactually added my name to similar task to R-21 week14:13
elodillesfungi: help will be appreciated in the coming 2-3 weeks when teams start to approve the transition patches and we'll need to review them o:)14:14
fungiyep, i don't have any more time off planned so should be more useful post-ptg14:15
elodillesthanks in advance o/14:15
elodillesokay, let's move on for now to next topic14:15
elodilles#topic Review weekly email14:15
elodilles#link https://etherpad.opendev.org/p/relmgmt-weekly-emails14:15
elodillesplease review ^^^14:15
fricklerthe last line has a lot of spaces in it, otherwise lgtm14:18
fungiah, yeah the milestone line14:18
elodillesokay, i'll not align the dates then o:)14:18
fungibut yes lgtm too14:18
elodillesACK, will send it later today14:18
elodilles#topic Open Discussion14:19
fungiyou could always move "next week" to a parenthetical at the end of the first entry14:19
fungi2027.1 "Indri" virtual PTG: 12-16 October, 2026 (next week)14:19
elodillesfungi: right, that looks better14:19
fungithen the dates would be a little closer vertically14:19
elodilleswill do that14:20
elodillesso, i've 1 question only:14:20
elodilles(elod) when should we hold the next release meeting, Nov 13 is okay?14:20
fungii'll be around and available14:21
elodillesso everyone is okay with skipping all the weekly meetings until then, right?14:21
fungii'm okay with it, but could also meet if we have a reason to do so14:22
fricklerfine for me14:22
fungimainly i think skipping next week is in order, at the very least, due to the ptg14:22
elodillesnot so many tasks, i think it's enough to ping release-team here if needed until R-19 / Nov 13 meeting14:23
fricklerone other question: iiuc we still need to cleanup some 2024.1 branches, maybe fungi wants to get some practice on that?14:23
fungiyeah, in the lead-up to milestone 1 i suppose work and reminders will pick up?14:23
elodilles#agreed Skip the coming weekly meetings and meet on 13 November14:24
elodilles^^^14:24
elodillesfrickler: which 2024.1 branches you mean?14:24
fungifrickler: i could, is there a list of the ones that opted out of unmaintained? or do you mean stable?14:24
fricklerah, no, 2024.2 https://review.opendev.org/c/openstack/releases/+/100647214:26
fungioh, that makes more sens14:26
fungie14:26
elodillesah, the cylce-trailing projects EOL for 2024.2 Dalmation14:26
elodillesright14:26
fungii guess there's a script to close remaining changes for those branches before tagging and deleting?14:27
elodillesi probably forgot to run the script against it14:27
elodillesfungi: tools/list_eol_stale_branches.sh should be the one14:28
frickleralso tools/abandon_patches_on_unmaintained_branch.sh if needed14:29
elodillesright14:29
elodillesor tools/abandon_patches_on_branch.sh actually... i think...14:30
fricklerah, right, 2024.2 didn't go to unmaintained14:31
elodillesas 2024.2 is EOL not unmaintained14:31
fungiah yeah, because this is stable14:31
elodillesyepp14:31
fungii can run those in a bit, i assume they're fairly self-explanatory with a cursory skimming14:31
elodillesyes, should be14:32
opendevreviewStephen Finucane proposed openstack/reno master: Add support for uid_overrides config option  https://review.opendev.org/c/openstack/reno/+/100786214:33
opendevreviewStephen Finucane proposed openstack/reno master: Add support for loading config from pyproject.toml  https://review.opendev.org/c/openstack/reno/+/100786314:33
opendevreviewStephen Finucane proposed openstack/reno master: docs: Replace reference to Travis CI  https://review.opendev.org/c/openstack/reno/+/100977914:33
elodillesokay, anything else?14:33
fungii didn't have anything14:34
* frickler neither14:34
elodillesthanks. then let's end the meeting14:34
fungithanks elodilles!14:34
elodillesthanks fungi frickler for joining o/14:34
elodilles#endmeeting14:34
opendevmeetMeeting ended Fri Oct  9 14:34:54 2026 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)14:34
opendevmeetMinutes:        https://meetings.opendev.org/meetings/releaseteam/2026/releaseteam.2026-10-09-14.00.html14:34
opendevmeetMinutes (text): https://meetings.opendev.org/meetings/releaseteam/2026/releaseteam.2026-10-09-14.00.txt14:34
opendevmeetLog:            https://meetings.opendev.org/meetings/releaseteam/2026/releaseteam.2026-10-09-14.00.log.html14:34
opendevreviewMerged openstack/reno master: pre-commit: Bump versions  https://review.opendev.org/c/openstack/reno/+/100785914:36
opendevreviewMerged openstack/reno master: Move typing deps to dependency-group  https://review.opendev.org/c/openstack/reno/+/100786014:36
opendevreviewMerged openstack/reno master: docs: Update guidance on changing committed notes  https://review.opendev.org/c/openstack/reno/+/100786114:36
opendevreviewMerged openstack/reno master: docs: Replace reference to Travis CI  https://review.opendev.org/c/openstack/reno/+/100977914:50
opendevreviewElod Illes proposed openstack/releases master: Add list-inbetween-eol-series command  https://review.opendev.org/c/openstack/releases/+/100979215:43
opendevreviewElod Illes proposed openstack/releases master: Reverse list-eom-series sorting  https://review.opendev.org/c/openstack/releases/+/100979315:43
opendevreviewElod Illes proposed openstack/releases master: Extend list_eol_stale_branches.sh with non-SLURP EOL  https://review.opendev.org/c/openstack/releases/+/100979415:43
opendevreviewStephen Finucane proposed openstack/reno master: Add missing zuul jobs  https://review.opendev.org/c/openstack/reno/+/100979515:44
elodillesfungi: you'll need those 3 small patches ^^^ to be able to clean up OSA dalmatian branch15:44
fungioh, thanks!15:45
elodillesi forgot that i had to tweak a bit the script last time to cleanup dalmatian branches... so now i prepared the patch(es) for it.15:48
opendevreviewMerged openstack/reno master: Add support for uid_overrides config option  https://review.opendev.org/c/openstack/reno/+/100786215:55
opendevreviewMerged openstack/reno master: Add support for loading config from pyproject.toml  https://review.opendev.org/c/openstack/reno/+/100786315:58
opendevreviewJeremy Stanley proposed openstack/releases master: Add list-inbetween-eol-series command  https://review.opendev.org/c/openstack/releases/+/100979217:15
opendevreviewJeremy Stanley proposed openstack/releases master: Reverse list-eom-series sorting  https://review.opendev.org/c/openstack/releases/+/100979317:15
opendevreviewJeremy Stanley proposed openstack/releases master: Extend list_eol_stale_branches.sh with non-SLURP EOL  https://review.opendev.org/c/openstack/releases/+/100979417:15
fungielodilles: i made a trivial pep8 fix at the bottom of that stack ^17:15
fungihow do folks generally invoke these shell scripts? at least `tools/list_eol_stale_branches.sh` expects to find `list-inbetween-eol-series` in the executable path, which implies running under an activated venv with `openstack_releases` installed, but e.g. the `[testenv:venv]` section in `tox.ini` needs them in its allowlist to wrap that way17:30
fungidoing a `. .tox/venv/bin/activate` seems to suffice, but curious if there's a preferred workflow17:31
fungihrm...17:41
fungi`> Do you want to delete the branch stable/2023.2 from openstack/openstack-ansible repository? [y/N]: ./tools/list_eol_stale_branches.sh: line 146: read: 0: read error: Resource temporarily unavailable`17:41
fungiseeing those scroll by17:41
funginot sure why it thinks it can't prompt me17:42
elodillesfungi: "tox -e venv -- tools/list_eol_stale_branches.sh" should do the trick. but it should be the same as with "activate"17:54
fungi`venv: failed with tools/list_eol_stale_branches.sh (resolves to tools/list_eol_stale_branches.sh) is not allowed, use allowlist_externals to allow it`17:55
fungihow do you normally get around adding the names of all the scripts to your tox.ini locally?17:55
fungi(because that's what i tried first)17:56
opendevreviewStephen Finucane proposed openstack/reno master: Add missing zuul jobs  https://review.opendev.org/c/openstack/reno/+/100979517:59
opendevreviewStephen Finucane proposed openstack/reno master: Add releasenotes build  https://review.opendev.org/c/openstack/reno/+/100983117:59
fungibut yes, i expect that is unrelated to whatever is breaking the read builtin's ability to wait for input18:00
elodillesfungi: oh, actually you don't need the "tox -e venv" as there is "enable_tox_venv" called in the script. so it should run without any fancy trick18:02
fungiseems like my shell may have stdin winding up in non-blocking mode18:02
elodillesand that is why we don't need the allowlist18:03
fungiweird, it definitely wasn't finding the entrypoint before18:04
elodillesi remember once seen that read error, but dunno how and why :/ for me it was always working18:04
fungithough that seems to probably be from having not run `tox -e venv ...` after the last `git clean`18:04
elodillesi'm mostly using bash as shell18:05
fungiyes, also have bash as my shell here18:06
elodillesneed to be AFK for some time, but this is not urgent so feel free to do other things if you have more important tasks and we can get back to this next week18:07
fungiyeah, i'll keep poking at it, seems like at this point i just need to figure out if bash on my platform is defaulting to non-blocking stdin, or if it's something getting inherited from e.g. tmux18:08
fungithanks for the help!18:08
elodillesno problem :S especially as i could not really help :/18:08
fungiit may just be something left weird in my session, i'll test under a completely fresh terminal in a bit18:19
funginow i'm running it inside a vanilla xterm with no tmux or anything18:20
funginope, exact same behavior in a fresh plain xterm with bash. maybe debian starts bash in nonblocking mode?18:43
fungiokay, hackishly adding "<`tty`" to the end of the read commands seems to have worked around the problem, so i think the problem is that the shell by default thinks my tty is elsewhere? at least for stdin anyway. trying a few other things to narrow it down19:11
opendevreviewStephen Finucane proposed openstack/reno master: Add releasenotes build  https://review.opendev.org/c/openstack/reno/+/100983119:20
fungiokay, another experiment was to run `python3 -c 'import os;os.set_blocking(0, True)'` first which didn't help, so i don't think the problem i'm hitting is the common "stdin left in non-blocking mode" problem that often leads to that same symptom19:32
opendevreviewThomas Bechtold proposed openstack/releases master: stevedore 5.9.2  https://review.opendev.org/c/openstack/releases/+/100984119:46
fungiredirecting stdin for the script itself doesn't seem to work, fwiw19:58
fungiattempting to create a simple reproducer, i get normal expected behavior instead: https://paste.opendev.org/show/bqcRIYVKSoFS9A6otsgj/20:14
fungileading me to suspect something else running earlier in list_eol_stale_branches.sh is leaving stdin in a broken state20:14
fungiyeah, injecting read calls early in the script i can see they're working, so worst case i should be able to brute-force bisect bits of the script until i find where it starts to break20:21
opendevreviewStephen Finucane proposed openstack/releases master: keystoneauth 5.18.1  https://review.opendev.org/c/openstack/releases/+/100986020:34
opendevreviewMerged openstack/reno master: Add missing zuul jobs  https://review.opendev.org/c/openstack/reno/+/100979520:38
opendevreviewMerged openstack/reno master: Add releasenotes build  https://review.opendev.org/c/openstack/reno/+/100983120:38
fungigetting closer... if i put it on the line before the conditional at https://opendev.org/openstack/releases/src/commit/3479e78/tools/list_eol_stale_branches.sh#L145 it works, immediately after that line it breaks, so it's some side effect of either `no_stable_open_patches` or `eol_tag_matches_stable_head`21:18
fungiit's curl!!!22:03
fungiand it actually is non-blocking mode getting left on stdin, curl is what's doing it22:03
fungisimple reproducer with comments: https://paste.opendev.org/show/bavKUuRnCafF9l4uQAfL/22:10
fungithis is with the curl 8.23.0~rc2-1 package on debian sid. i'll go bug-hunting for curl upstream tomorrow, though a trivial local patch would probably be to swap `curl -s` out for `wget -qO-`22:16
fricklerhmm, I was just about to ask for the version info ;) with 8.14.1 from trixie I get "curl: option --output=/dev/null: is unknown" and if I s/=/ / for that option, I get no issue, all three reads work22:17
fungioh, well it's also not needed to reproduce, i was just using it in lieu of `>/dev/null` or similar to hide the noise from curl stdout22:24
fungibut i previously reproduced the issue without any options (--silent or --output)22:25
fungibasically curl anything in a script and then stdin is left in non-blocking mode for all further commands in that script unless i undo it22:27

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