Wednesday, 2023-09-13

opendevreviewrenliang proposed openstack/project-team-guide master: Add and remove incorrect links  https://review.opendev.org/c/openstack/project-team-guide/+/89461001:51
ianychoi[m]Thank you for mentioning me, frickler. JayF: Sorry for no replies for a few days - I have just replied. Thank you all!07:49
fricklerianychoi[m]: oh, you weren't visible in this channel earlier, else I'd have made a direct reference. seems this is a recurring issue with the matrix bridge. thanks for responding anyway07:51
ianychoi[m]Yep, now I recognize the recurring issue thanks to you :)07:53
opendevreviewMerged openstack/project-team-guide master: Add and remove incorrect links  https://review.opendev.org/c/openstack/project-team-guide/+/89461011:38
fungiyes, i think the matrix bridge must not put people in the channel from an irc perspective unless they start talking (probably in order to minimize the number of active irc protocol connections)12:10
opendevreviewMatthias Runge proposed openstack/governance master: Add python-observabilityclient  https://review.opendev.org/c/openstack/governance/+/89491512:24
opendevreviewMatthias Runge proposed openstack/governance master: Add python-observabilityclient  https://review.opendev.org/c/openstack/governance/+/89491512:39
opendevreviewAlex Kavanagh proposed openstack/governance master: Add Pure Storage Manila flashblade charm to OpenStack charms  https://review.opendev.org/c/openstack/governance/+/89391113:47
*** blarnath is now known as d34dh0r5315:02
fricklertc-members: so this sounds pretty release-critical to me, no idea whether it is only me having been so ignorant or whether there is a larger gap in communications https://review.opendev.org/c/openstack/requirements/+/887261/comments/9f400e68_c9f028aa cc: zigo stephenfin elodilles 18:41
fricklerrelated, also some lack of either communications or clear responsibilities, there's a situation with castellan https://review.opendev.org/c/openstack/requirements/+/88314118:42
fungiboth of those look like either a lack of sufficient integration testing, or a preference by the lib reviewers for moving forward regardless of whether consumers are ready18:49
fungiand i agree it's the sort of thing worth raising to the tc18:49
fungi(because i also am not sure who's "right" in those scenarios)18:50
fungianother option is reverting those changes on stable/2023.2 and tagging a new stable point releases18:51
fricklerfor oslo.db that seems the only feasible solution indeed, since at least 4 projects are not ready for sqla 2.0, with the work on heat not even having started afaict18:55
elodillesfrickler: thanks for bringing this up. as we discussed this during last relmgt meeting on Friday hberaud added a task to track the issues (oslo.db, castellan; line 428 @ https://etherpad.opendev.org/p/bobcat-relmgt-tracking ) and regarding oslo.db (SQLA 2.0) a mail thread was also started by zigo ( https://lists.openstack.org/pipermail/openstack-discuss/2023-September/035069.html )19:21
elodillesto me this really looks like we need to do again some revert&release action like we did in last cycles (also related to oslo libraries :/) if that solves our problem at all... :S19:23
fricklerelodilles: yes, the point that I was missing before is that oslo.db >= 13 seems to depend on sqla >= 2.0, which doesn't seem to be expressed in its requirements though19:24
elodillesyepp19:28
elodilles(and i have some deja vu o:) (oslo.db 12.1.0 release issues in Zed, with some follow up discussions on PTG afterwards))19:35

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