Tuesday, 2026-10-13

fricklerdo we have some reference as to how this process is handled? 2025.1 is going eom very soon, not sure whether that would be worth the effort. also as a minimum requirement I think we would need to be able to create a stable branch for every open release, we must not introduce gaps07:15
elodillesyes, we had the problem a couple of cycles ago with some oslo libs :/ and the only thing (i remember) we did was to moved them back to cwi, but we didn't cut stable branches, afair07:32
*** ykarel_ is now known as ykarel08:04
tkajinamit's ok that we do not create branches for older releases, especially older than 2026.2 .10:11
tkajinammaybe we can at least move 2027.1 to cwi model, and revisit older branches when we actually need these10:12
fricklerack10:54
opendevreviewStephen Finucane proposed openstack/releases master: tooz 9.2.0  https://review.opendev.org/c/openstack/releases/+/101014511:23
*** haleyb|out is now known as haleyb12:55
opendevreviewStephen Finucane proposed openstack/releases master: data: Use boolean values for series_status slurp field  https://review.opendev.org/c/openstack/releases/+/100611013:43
opendevreviewStephen Finucane proposed openstack/releases master: data: Encode supported Python versions  https://review.opendev.org/c/openstack/releases/+/99355713:43
opendevreviewTakashi Kajinami proposed openstack/releases master: Move back tooz to the CWI model  https://review.opendev.org/c/openstack/releases/+/101003914:41

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