| *** bauzas4 is now known as bauzas | 05:26 | |
| *** bauzas4 is now known as bauzas | 08:03 | |
| opendevreview | Merged openstack/releases master: [ironic] Cut stable/2026.2 branch for plugins and tools https://review.opendev.org/c/openstack/releases/+/1005566 | 08:44 |
|---|---|---|
| opendevreview | Merged openstack/releases master: Add Freezer cycle highlights (Hibiscus) https://review.opendev.org/c/openstack/releases/+/1005770 | 08:50 |
| opendevreview | Merged openstack/releases master: Release heat-tempest-plugin for 2026.2 Hibiscus https://review.opendev.org/c/openstack/releases/+/1005548 | 08:56 |
| opendevreview | Merged openstack/releases master: Release mistral-tempest-plugin for 2026.2 Hibiscus https://review.opendev.org/c/openstack/releases/+/1005553 | 09:03 |
| opendevreview | Merged openstack/releases master: [horizon] 2026.2 Hibiscus cycle highlights https://review.opendev.org/c/openstack/releases/+/1005812 | 09:03 |
| opendevreview | Omer Schwartz proposed openstack/releases master: [Designate] Add 2026.2 cycle highlights https://review.opendev.org/c/openstack/releases/+/1005854 | 10:16 |
| opendevreview | Merged openstack/releases master: [Designate] Add 2026.2 cycle highlights https://review.opendev.org/c/openstack/releases/+/1005854 | 11:35 |
| opendevreview | Elod Illes proposed openstack/releases master: Add release note links for 2026.2 Hibiscus https://review.opendev.org/c/openstack/releases/+/1005865 | 11:50 |
| *** bauzas5 is now known as bauzas | 12:32 | |
| opendevreview | Stephen Finucane proposed openstack/releases master: openstacksdk 4.21.0 https://review.opendev.org/c/openstack/releases/+/1005909 | 15:07 |
| opendevreview | Stephen Finucane proposed openstack/releases master: keystoneauth 5.18.0 https://review.opendev.org/c/openstack/releases/+/1005910 | 15:07 |
| opendevreview | Stephen Finucane proposed openstack/releases master: python-openstackclient 10.4.0 https://review.opendev.org/c/openstack/releases/+/1005911 | 15:07 |
| opendevreview | Cyril Roelandt proposed openstack/releases master: Add Glance cycle highlights (Hibiscus) https://review.opendev.org/c/openstack/releases/+/1005912 | 15:12 |
| opendevreview | Elod Illes proposed openstack/releases master: Release watcher-tempest-plugin for 2026.2 Hibiscus https://review.opendev.org/c/openstack/releases/+/1005558 | 15:41 |
| frickler | stephenfin: IMHO it is a bad idea to make new releases now which cannot be tested properly while we have a requirements freeze. also both sdk and most of oslo do use stable branches, so I cannot follow the "aren't really tied to releases" argument | 15:55 |
| stephenfin | Hmm, why can't we test them properly? | 15:56 |
| frickler | because all other projects consume what is in upper-constraints.txt | 15:56 |
| stephenfin | can't we branch that? | 15:57 |
| frickler | not until everything else has branched | 15:57 |
| stephenfin | but we've branched everything except for trailing releases, which aren't tracked in u-c afaik? | 15:59 |
| stephenfin | neither are services, for the matter | 15:59 |
| stephenfin | I'm wondering if we can branch u-c at the same time we branch client-libraries, which I believe are the last thing we freeze before the services and the trailing release stuff | 16:00 |
| stephenfin | and btw I'm asking these questions to help me understand. I likely have missed stuff here | 16:00 |
| frickler | there is some interaction between devstack branching, reqs branching, and all services branches. I don't remember all the details, but I think we have learned from various issues that QA+reqs need to be last. maybe elodilles or gmaan can share more details | 16:02 |
| stephenfin | Ack. I'm going to post about this to openstack-discuss also | 16:03 |
| stephenfin | Looking at e.g. the hibiscus release schedule, milestone 3 feels like a natural point to branch requirements | 16:05 |
| stephenfin | We already institute a requirements freeze at this point and expect a requirements freeze exception for any changes, so asking that people explicitly backport to e.g. stable/2026.2 feels sane | 16:05 |
| * stephenfin writes said email | 16:05 | |
| gmaan | yeah, once all projects are done with branching then QA and requirement are the last to do. | 16:18 |
| gmaan | requirement is before QA maybe? but QA is later than services branching | 16:19 |
| stephenfin | okay, email sent | 16:44 |
| gmaan | replied in ML, i do not know why requriement branching is doine late but if we solve it then we can sovle QA branching things also and fix the tetsing gap | 19:34 |
| gmaan | i know, someone or many members complained about testing gap on newly created stble branches and we did not have any right solution for that due to order of requirements branching | 19:35 |
Generated by irclog2html.py 4.1.0 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!