| frickler | yes, this is why projects should merge those changes asap | 07:08 |
|---|---|---|
| elodilles | yepp. we advertise it a couple of places that those generated patches should be reviewed and approved as soon as possible, especially if teams want to see release notes, but less active projects tend to ignore to do so | 08:36 |
| opendevreview | Merged openstack/releases master: Release ironic-python-agent 11.2.0 and branch for 2025.2 https://review.opendev.org/c/openstack/releases/+/959569 | 08:42 |
| opendevreview | Merged openstack/releases master: Release nova RC1 for 2025.2 Flamingo https://review.opendev.org/c/openstack/releases/+/960103 | 08:42 |
| opendevreview | Merged openstack/releases master: Release ovn-bgp-agent RC1 for 2025.2 Flamingo https://review.opendev.org/c/openstack/releases/+/960106 | 08:42 |
| opendevreview | Merged openstack/releases master: Release zaqar RC1 for 2025.2 Flamingo https://review.opendev.org/c/openstack/releases/+/960125 | 08:43 |
| elodilles | as it is said in the commit message of those generated patch: "Add file to the reno documentation build to show release notes for | 08:43 |
| elodilles | stable/2025.2." | 08:43 |
| opendevreview | Merged openstack/releases master: Release zaqar-ui RC1 for 2025.2 Flamingo https://review.opendev.org/c/openstack/releases/+/960124 | 08:43 |
| opendevreview | Merged openstack/releases master: Release neutron RC1 for 2025.2 Flamingo https://review.opendev.org/c/openstack/releases/+/960102 | 08:58 |
| opendevreview | Merged openstack/releases master: Release manila-ui RC1 for 2025.2 Flamingo https://review.opendev.org/c/openstack/releases/+/960086 | 08:58 |
| elodilles | release-team: can one of you review and approve (if correct) the following 'new-release' patches please? (so that it won't be Self+2 from me o:)) https://review.opendev.org/q/topic:new-release+branch:master+is:open | 08:58 |
| elodilles | (^^^ this is what i mentioned yesterday: https://meetings.opendev.org/irclogs/%23openstack-release/%23openstack-release.2025-09-11.log.html#openstack-release.2025-09-11.log.html#t2025-09-11T16:21:36 ) | 09:00 |
| opendevreview | Merged openstack/releases master: Release magnum-ui RC1 for 2025.2 Flamingo https://review.opendev.org/c/openstack/releases/+/960083 | 09:01 |
| elodilles | +1: i'm about to review the flamingo-rc1-deadline patches that lacks team response | 09:03 |
| opendevreview | Elod Illes proposed openstack/releases master: Release mistral RC1 for 2025.2 Flamingo https://review.opendev.org/c/openstack/releases/+/960092 | 09:08 |
| frickler | elodilles: I would very much prefer to escalate the inactivity of the freshly refreshed requirements DPLs to the TC (hi gouthamr ;). I also haven't seen any action being taken in terms of reqs freeze for example | 09:10 |
| ttx | elodilles: I +2ed the missed constraints updates patches | 09:25 |
| elodilles | frickler: i haven't followed the requirements team's activity, but we got some responses, which reminds me: pyroute2 thread: https://lists.openstack.org/archives/list/openstack-discuss@lists.openstack.org/thread/SQLZ6ZOPUF5EHJ722ZQGPT7PSPV4PCNE/ | 09:30 |
| elodilles | ttx: ACK, thanks o/ | 09:31 |
| elodilles | (i've answered to the pyroute2 thread) | 09:58 |
| opendevreview | Elod Illes proposed openstack/releases master: Release barbican RC1 for 2025.2 Flamingo https://review.opendev.org/c/openstack/releases/+/960062 | 10:05 |
| opendevreview | Yasufumi Ogawa proposed openstack/releases master: Release tacker RC1 for 2025.2 Flamingo https://review.opendev.org/c/openstack/releases/+/960113 | 10:10 |
| opendevreview | Elod Illes proposed openstack/releases master: Release trove-dashboard RC1 for 2025.2 Flamingo https://review.opendev.org/c/openstack/releases/+/960115 | 10:12 |
| opendevreview | Elod Illes proposed openstack/releases master: Release trove RC1 for 2025.2 Flamingo https://review.opendev.org/c/openstack/releases/+/960116 | 10:18 |
| opendevreview | Elod Illes proposed openstack/releases master: Release octavia RC1 for 2025.2 Flamingo https://review.opendev.org/c/openstack/releases/+/960105 | 12:17 |
| opendevreview | Elod Illes proposed openstack/releases master: Release ceilometer RC1 for 2025.2 Flamingo https://review.opendev.org/c/openstack/releases/+/960066 | 12:20 |
| opendevreview | Elod Illes proposed openstack/releases master: Release bifrost for 2025.2 Flamingo https://review.opendev.org/c/openstack/releases/+/960047 | 12:54 |
| opendevreview | Takashi Kajinami proposed openstack/releases master: Create a new etcd3gw release https://review.opendev.org/c/openstack/releases/+/960832 | 14:00 |
| ttx | #startmeeting releaseteam | 14:00 |
| opendevmeet | Meeting started Fri Sep 12 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 |
| opendevmeet | Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. | 14:00 |
| opendevmeet | The meeting name has been set to 'releaseteam' | 14:00 |
| ttx | Ping list: release-team elod | 14:00 |
| ttx | Our agenda for today is: | 14:00 |
| ttx | #link https://etherpad.opendev.org/p/flamingo-relmgt-tracking#L369 | 14:01 |
| elodilles | o/ | 14:01 |
| ttx | #topic Review task completion | 14:01 |
| ttx | - Process any remaining library branching exception. (all) | 14:01 |
| ttx | #link https://review.opendev.org/q/topic:flamingo-stable-branches+is:open | 14:02 |
| ttx | https://review.opendev.org/c/openstack/releases/+/959165 is still open | 14:02 |
| frickler | \m/ | 14:02 |
| elodilles | yes, i've pinged them on the other patch: | 14:03 |
| elodilles | https://review.opendev.org/c/openstack/releases/+/957695 | 14:03 |
| elodilles | as this is the one that blocks the other one ^^^ | 14:03 |
| ttx | At this point we can drop it from release, or give it a bit more time | 14:04 |
| ttx | I'd be fine giving it a bit more time before pulling it out | 14:04 |
| elodilles | i think next week we have to do something :/ | 14:04 |
| ttx | since not much depends on it | 14:04 |
| ttx | yeah, by next week we'll have to pull it | 14:04 |
| elodilles | i think we might need to release it broken, as is | 14:05 |
| ttx | or release broken yes | 14:05 |
| elodilles | if it won't be fixed by then | 14:05 |
| ttx | ok let's push back to next week for final call | 14:05 |
| elodilles | +1 | 14:06 |
| ttx | - generate release requests for all deliverables that do not have a suitable candidate yet: (elod) | 14:06 |
| elodilles | some were proposed already, i've copied them in the list; and i've generated release patches for the rest | 14:07 |
| elodilles | bifrost: https://review.opendev.org/c/openstack/releases/+/960047 | 14:08 |
| elodilles | ironic-inspector: https://review.opendev.org/c/openstack/releases/+/959565 | 14:08 |
| elodilles | ironic-prometheus-exporter: https://review.opendev.org/c/openstack/releases/+/960048 | 14:08 |
| elodilles | ironic-ui: https://review.opendev.org/c/openstack/releases/+/960049 | 14:08 |
| elodilles | networking-generic-switch: https://review.opendev.org/c/openstack/releases/+/959567 | 14:08 |
| elodilles | swift: https://review.opendev.org/c/openstack/releases/+/959567 | 14:08 |
| ttx | Just approved bifrost | 14:08 |
| elodilles | note: there are some further ironic release patch | 14:08 |
| elodilles | i had a couple of -1's there for asking the teams to double check the version bumps | 14:09 |
| elodilles | but no answer yet | 14:09 |
| ttx | hmm | 14:10 |
| ttx | maybe you can +2/PTL+1 them with a note that they will be merged asap unless we get a -1... and I will approve them on Monday if no response | 14:11 |
| ttx | together wit those RC1 | 14:11 |
| elodilles | ACK, I'll do that after the meeting then | 14:11 |
| ttx | I'll add a task for that | 14:12 |
| ttx | good activity for my Monday train ride | 14:12 |
| elodilles | :] | 14:13 |
| ttx | - investigate https://bugs.launchpad.net/octavia/+bug/2121578 (elod) | 14:14 |
| elodilles | yeah, i had other things to investigate so had no time to deal with this :/ | 14:14 |
| ttx | Let's push it forward to next week | 14:14 |
| elodilles | on the other hand i haven't heard complains about this issue | 14:14 |
| elodilles | so i don't know how serious this is | 14:15 |
| ttx | - heat-translator release patch - broken gate (elod) | 14:15 |
| elodilles | (let's hope it won't blow up in our face at release day :S fingers crossed :X) | 14:15 |
| ttx | I think we covered it | 14:15 |
| elodilles | yes | 14:15 |
| ttx | - Send weekly email. (ttx) | 14:16 |
| ttx | will do in a minute | 14:16 |
| ttx | #topic Assign R-2 week tasks | 14:16 |
| ttx | All set! Thanks elodilles | 14:16 |
| elodilles | +1 | 14:17 |
| ttx | #topic Review weekly countdown email | 14:17 |
| ttx | #link https://etherpad.opendev.org/p/relmgmt-weekly-emails | 14:17 |
| * elodilles clicks | 14:18 | |
| opendevreview | Merged openstack/releases master: Release bifrost for 2025.2 Flamingo https://review.opendev.org/c/openstack/releases/+/960047 | 14:19 |
| elodilles | mail LGTM | 14:20 |
| elodilles | ttx: sorry, i think i missed to mention some thing at one task | 14:20 |
| elodilles | i mean two points: | 14:21 |
| elodilles | 1) Branch devstack-plugin-* deliverables: | 14:21 |
| elodilles | #link https://review.opendev.org/q/topic:devstack-plugin-flamingo | 14:21 |
| ttx | ok will send in a few | 14:21 |
| elodilles | ttx: ++ | 14:22 |
| ttx | this one needs attention from gmaan | 14:22 |
| elodilles | so, Ghanshyam is on PTO | 14:22 |
| ttx | (https://review.opendev.org/c/openstack/releases/+/960039) | 14:22 |
| elodilles | he'll be back after 2025.2 Flamingo release :) | 14:22 |
| elodilles | so probably we should review and process this patch without his approve | 14:23 |
| ttx | looks like we'll have to make a call then | 14:23 |
| ttx | will do | 14:23 |
| elodilles | yes, frickler ttx , please do review and approve if it looks OK | 14:23 |
| ttx | done | 14:24 |
| ttx | a bit of a no-brainer | 14:24 |
| elodilles | 2) cycle-with-rc that are not trailing deliverables and that have not done a RC1 yet | 14:24 |
| elodilles | #link https://review.opendev.org/q/topic:flamingo-rc1-deadline | 14:24 |
| elodilles | i've gone through the patches without response from team | 14:24 |
| ttx | yeah for those I will approve them on Monday unless they get -1ed | 14:25 |
| elodilles | and updated the hashes where it was needed | 14:25 |
| elodilles | ttx: thanks o/ | 14:25 |
| elodilles | sounds good o/ | 14:25 |
| ttx | #topic Open Discussion | 14:25 |
| fungi | summarizing the discussion with zigo yesterday: temporary disappearance of notes for the upcoming release between stable branch creation at and merging the auto-proposed change adding it to the index confuses some downstream consumers (e.g. distro package maintainers) | 14:25 |
| elodilles | probably majority were approved and/or updated by teams :) | 14:25 |
| fungi | yesterday it first got raised to the opendev sysadmins as a potential content hosting problem or publication job failure, before we tracked it back to openstack's release process working as designed | 14:25 |
| fungi | i can't help but wonder if there's a way to shorten or eliminate that gap, since even if maintainers are around and approve those changes quickly, there is still some period of time where the upcoming changes have vanished from the site entirely | 14:25 |
| fungi | food for thought (maybe a good ptg topic) | 14:26 |
| ttx | +1 | 14:26 |
| ttx | I'll add it | 14:26 |
| fungi | thanks! | 14:26 |
| fungi | probably needs some brainstorming of solutions | 14:27 |
| elodilles | +1 | 14:27 |
| ttx | elodilles: want to talk pyroute2? | 14:28 |
| elodilles | ttx: ah, yes, | 14:28 |
| elodilles | fortunately it got solved meanwhile :) | 14:28 |
| elodilles | so | 14:28 |
| ttx | ok so maybe no need :) | 14:28 |
| elodilles | pyroute2 had a bug | 14:28 |
| fungi | well, the immediate emergency got solved | 14:28 |
| elodilles | and needed some capping | 14:28 |
| elodilles | (elod) pyroute2 bug: https://meetings.opendev.org/irclogs/%23openstack-release/%23openstack-release.2025-09-08.log.html#openstack-release.2025-09-08.log.html#t2025-09-08T12:52:46 | 14:29 |
| elodilles | requirements capping to pyroute2==0.8.1 was accepted - https://review.opendev.org/c/openstack/requirements/+/960366 / https://lists.openstack.org/archives/list/openstack-discuss@lists.openstack.org/thread/SQLZ6ZOPUF5EHJ722ZQGPT7PSPV4PCNE/ | 14:29 |
| elodilles | (just to have it here, for ship's log o:)) | 14:29 |
| elodilles | fungi: indeed, we might need to bump pyroute2 version on stable/2025.2 later on, if that is possible | 14:30 |
| fungi | also based on discussion, there's not yet a fix upstream in the library | 14:30 |
| elodilles | as far as i understood | 14:30 |
| elodilles | fungi: exactly | 14:30 |
| elodilles | no the current fixes proved to be not enough | 14:31 |
| fungi | increasing constraints for non-openstack-controlled projects in a stable branch is generally something we don't do | 14:31 |
| elodilles | no, the current fixes proved to be not enough | 14:31 |
| elodilles | so yes, teams are waiting for further fixes | 14:31 |
| elodilles | fungi: exactly | 14:31 |
| ttx | ok, anything else? | 14:31 |
| fungi | probably we should stick with pyroute2 0.8.1 in our constraints list for the lifetime of the stable/2025.2 branches | 14:32 |
| elodilles | fungi: so i don't know whether there could be given some exception for pyroute2 later, or we have to stick to the capping | 14:32 |
| elodilles | fungi: i see. i did not remember the requirements team's policy on this | 14:32 |
| fungi | i'm not aware of having previously made exceptions for cases like that | 14:32 |
| elodilles | fungi: i thought some exceptional cases we could bump versions | 14:32 |
| frickler | usually exceptions are made for CVEs | 14:33 |
| frickler | but I'm not sure how strict we need to be on this | 14:33 |
| fungi | we freeze constraints (except for stable point releases of our own software) in order to stabilize testing, and we don't make any security guarantees about versions of software in the frozen constraints list | 14:33 |
| elodilles | fungi: i think some rare cases when CI had issues we did that | 14:33 |
| elodilles | and what frickler says, when there were CVEs | 14:33 |
| fungi | if we have made exceptions for vulnerabilities solely in a dependency, that seems like a poor choice and sets incorrect expectations for users of those files | 14:34 |
| elodilles | but i'm not fully aware of requirments processes, so i was just wondering | 14:34 |
| fungi | we cannot, as a project, be expected to track vulnerabilities for all dependencies in our maintained stable branches, and changing versions of dependencies destabilizes testing | 14:35 |
| elodilles | hmmm. i see | 14:35 |
| elodilles | so probably those things needs to be handled downstream by vendors | 14:35 |
| fungi | and we've repeatedly discouraged downstream consumers from using the frozen stable constraints lists exactly because we don't track vulnerabilities in those dependencies | 14:35 |
| frickler | except for kolla and osa there are many deployments not involving downstream vendors, so they plainly use u-c | 14:36 |
| elodilles | O.o | 14:36 |
| fungi | and it's their responsibility to alter the versions of dependencies or backport patches to them in those cases | 14:36 |
| fungi | i really wish we had a better way to let them know, because i suspect in many cases they don't even realize that's the case | 14:37 |
| frickler | we (kolla) also in vain try to convince people not to use the images we produce in production | 14:38 |
| frickler | (which also are produced using upstream stable u-c) | 14:38 |
| ttx | anything more we can do at this stage? | 14:39 |
| fungi | not that i know of | 14:39 |
| elodilles | thanks for the discussion! good to know this details. | 14:40 |
| ttx | alright, anything else to discuss? | 14:40 |
| opendevreview | sean mooney proposed openstack/releases master: Release watcher RC1 for 2025.2 Flamingo https://review.opendev.org/c/openstack/releases/+/960123 | 14:40 |
| elodilles | ttx: one more thing | 14:40 |
| elodilles | #link https://review.opendev.org/q/topic:fix-release-requirements-update-constraints | 14:40 |
| elodilles | some upper constraints bumps were missed because people started to use python_version>=3.10 in upper-constraints.txt | 14:41 |
| frickler | ah, right, I need to review these, thx for the reminder | 14:41 |
| elodilles | so i've created the above fixes to not miss them in the future ^^^ | 14:41 |
| frickler | though also with 3.9 gone, we could probably drop most of the >=3.10 stanzas | 14:42 |
| ttx | yeah we need project-config core to approve those | 14:42 |
| elodilles | well, one fix is for cases when teams replaces setup.py with pyproject.toml | 14:42 |
| frickler | yes, that one is needed anyway indeed | 14:42 |
| elodilles | frickler: i didn't even know we have py3.9 lines there | 14:43 |
| elodilles | frickler: i was surprised, as flamingo only supports py310+ | 14:43 |
| frickler | they were re-introduced when people still wanted to run centos9 jobs for some special cases | 14:43 |
| elodilles | but centos9 is also not supported runtime, am i right? o:) | 14:44 |
| ttx | I need to run, so I'll close the meeting, but feel free to continue the open discussion in-channel | 14:44 |
| fungi | looking | 14:44 |
| elodilles | https://governance.openstack.org/tc/reference/runtimes/2025.2.html | 14:44 |
| elodilles | ttx: okay, thanks o/ | 14:45 |
| frickler | it is not, but some projects were slow in updating stuff, in particular since centos10 wasn't available for quite some time during this cycle | 14:45 |
| ttx | #endmeeting | 14:45 |
| opendevmeet | Meeting ended Fri Sep 12 14:45:35 2025 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | 14:45 |
| opendevmeet | Minutes: https://meetings.opendev.org/meetings/releaseteam/2025/releaseteam.2025-09-12-14.00.html | 14:45 |
| opendevmeet | Minutes (text): https://meetings.opendev.org/meetings/releaseteam/2025/releaseteam.2025-09-12-14.00.txt | 14:45 |
| opendevmeet | Log: https://meetings.opendev.org/meetings/releaseteam/2025/releaseteam.2025-09-12-14.00.log.html | 14:45 |
| elodilles | frickler: i see | 14:45 |
| elodilles | anyway, my fixes handles now these cases, i've generated the missed new-release patches by using them | 14:46 |
| elodilles | maybe we are too close to the release day to simply drop the py39 and >=py310 lines from upper-constraints.txt now | 14:47 |
| elodilles | and of course, again, i don't know what is requirements team's view on this | 14:48 |
| frickler | yes, likely best to wait until after the release | 14:48 |
| frickler | https://review.opendev.org/c/openstack/requirements/+/948876 has some context | 14:48 |
| fungi | wait until after the release to approve the topic:fix-release-requirements-update-constraints changes? | 14:48 |
| frickler | the "requirements team" was pretty quiet on all that, mainly handled between me and rpittau | 14:49 |
| frickler | fungi: no, wait with removing final 3.9 figments from u-c | 14:49 |
| fungi | ah | 14:49 |
| elodilles | yes, i think those fixes can be merged | 14:50 |
| opendevreview | Cyril Roelandt proposed openstack/releases master: Release glance RC1 for 2025.2 Flamingo https://review.opendev.org/c/openstack/releases/+/960076 | 15:54 |
| fungi | i've proposed https://review.opendev.org/c/openstack/requirements/+/960857 to add a security warning to the readme, global requirements and upper constraints files in the requirements repo | 15:58 |
| fungi | maybe that will help, i don't know | 15:59 |
| opendevreview | Yasufumi Ogawa proposed openstack/releases master: Release tacker RC1 for 2025.2 Flamingo https://review.opendev.org/c/openstack/releases/+/960113 | 16:21 |
| frickler | at least something to point deployment projects and their consumers to, +1 | 19:49 |
| opendevreview | Goutham Pacha Ravi proposed openstack/releases master: Release manila 21.0.0.0rc1 (flamingo) https://review.opendev.org/c/openstack/releases/+/960087 | 21:59 |
| opendevreview | Yasufumi Ogawa proposed openstack/releases master: Release final heat-translator for 2025.2 Flamingo https://review.opendev.org/c/openstack/releases/+/957695 | 22:36 |
Generated by irclog2html.py 4.0.0 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!