| opendevreview | Merged openstack/releases master: Move whereto to oslo team https://review.opendev.org/c/openstack/releases/+/981822 | 08:31 |
|---|---|---|
| *** ralonsoh_ is now known as ralonsoh | 11:36 | |
| *** ykarel_ is now known as ykarel | 14:02 | |
| *** ykarel is now known as ykarel_ | 14:14 | |
| *** ykarel_ is now known as ykarel | 14:15 | |
| opendevreview | Merged openstack/releases master: Add PTG to 2026.2 Hibiscus cycle schedule https://review.opendev.org/c/openstack/releases/+/982233 | 16:20 |
| opendevreview | Dmitriy Rabotyagov proposed openstack/releases master: Tag RC3 for Freezer API https://review.opendev.org/c/openstack/releases/+/982689 | 16:39 |
| elodilles | noonedeadpunk: hi, i see that you proposed RC3 for Freezer API ^^^ | 17:01 |
| elodilles | noonedeadpunk: note that final RC deadline was last week | 17:02 |
| elodilles | noonedeadpunk: we only release now RC3 if it is *very* release critical o:) | 17:02 |
| elodilles | release-team: fyi ^^^ | 17:02 |
| noonedeadpunk | ah, ok, I will abandon it then | 17:04 |
| elodilles | ACK, thanks noonedeadpunk | 17:05 |
| noonedeadpunk | thanks for the update! | 17:05 |
| sean-k-mooney | are we waitign for the actual release to happen this week before proceeding with https://review.opendev.org/c/openstack/project-config/+/951395? | 17:40 |
| gouthamr | o/ release team.. carloss and i were chatting on #openstack-manila.. we have a teeny API regression in Manila. We have decided to patch it: https://review.opendev.org/c/openstack/manila/+/982308 ; but, we're realizing the 2026.1 branch's CI needs some work. We're debating what's the best course of action here.. | 18:19 |
| gouthamr | it isn't a big enough bug to stall the release in my opinion.. so we might turn around and do a minor release next week.. is that fine? | 18:20 |
| gouthamr | i would hate to upset https://review.opendev.org/c/openstack/releases/+/982438 for this issue | 18:21 |
| gouthamr | ah crap, /me reads the conversation between elodilles and noonedeadpunk above | 18:22 |
| gouthamr | sounds like a similar situation | 18:22 |
| clarkb | you can still fix 2026.1 CI and get the change landed there right? The only thing affected by the release schedule is when and what you make a tag from | 18:23 |
| gouthamr | yes, that's the plan clarkb.. i'm just asking if we don't spin up an RC3 for this problem that we discovered this late in the testing phase | 18:23 |
| gouthamr | i mean, i didn't want to do an RC3 and upset the coordinated release.. but, it looks like the final RC deadline was last thursday, so my confusion is moot | 18:25 |
| noonedeadpunk | octavia has a really bad one though, basically octavia+amphora are broken on py3.13 | 18:30 |
| noonedeadpunk | the patch is ready, but it's not even merged on master... | 18:31 |
| noonedeadpunk | but it should be backported to 2025.2 at least anyway, so... | 18:32 |
| gouthamr | noonedeadpunk: ah ack, so that's not a "release critical" issue given it exists in a past release | 19:07 |
| elodilles | gouthamr: i just confirm what you figured out o:) let's postpone the rc3 and make it a stable release some time after the coordinated release. but as Clark says, you can still fix stable/2026.1 gate and land the bug fix in advance | 19:14 |
| gouthamr | ++ ty elodilles | 19:15 |
| elodilles | np | 19:16 |
Generated by irclog2html.py 4.1.0 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!