12:01:30 #startmeeting barbican 12:01:30 Meeting started Tue Aug 8 12:01:30 2023 UTC and is due to finish in 60 minutes. The chair is xek. Information about MeetBot at http://wiki.debian.org/MeetBot. 12:01:30 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 12:01:30 The meeting name has been set to 'barbican' 12:01:39 #topic Roll Call 12:02:03 Courtesy ping for dmendiza[m] ade_lee d34dh0r53 Luzi tosky tobias-urdin jjung mharley 12:02:21 o/ 12:02:25 o/ 12:02:39 shouldn't lpiwowar be added to that list? :) 12:02:45 🙋 12:03:33 tosky, good point:), I will ad myself to the etherpad 12:04:31 morning :) 12:05:22 As usual our agenda can be found here: 12:05:29 #link https://etherpad.openstack.org/p/barbican-weekly-meeting 12:05:49 Just the usual agenda items today 12:05:56 #topic Review Past Meeting Action Items 12:06:44 #link https://meetings.opendev.org/meetings/barbican/2023/barbican.2023-08-01-12.02.html 12:07:13 I have a question for dmendiza[m]. Do we need running master barbican-tempest-plugin in the older jobs (e.g., in stable/victoria)? Can 12:07:35 Can ... ? 12:07:37 :)' 12:07:47 IIUC, Tempest has no branches, therefore we have to run master on all 12:08:15 :D ... Can we pin it to victoria-last? => https://review.opendev.org/c/openstack/barbican-tempest-plugin/+/890784 12:09:46 I don't see why not. I'm not sure I understand what the purpose of the tags are, but this seems like a good use. 12:09:47 It is branch-less but upper-constraints limit what is the newest version of tempest that can run in a job. I was discussing the possibility of bumping up the tempest for stable/victoria in requirements here but I was told that it might break some things so if it is possible we should try to avoid it. 12:09:54 what do you think Grzegorz Grasza ? 12:10:16 that pinning is what other projects do 12:10:39 The only disadvantage it will have that you will not run tests from master. I do not know whether it is something relevant for barbican and stable/victoria branch. 12:10:49 Cool. If all my project friends are jumping off the bridge, then I'm jumping too! 😜 12:10:58 I'm ok with pinning 12:11:11 lpiwowar: but do you need to add barbican and python-barbicanclient to the reuqired projects? I thought they were inherited 12:11:18 and they don't change the version 12:12:54 and for the record, the same override rules should apply to train and ussuri too 12:13:04 and wallaby, which is EM too 12:13:17 tosky: Yes, they are inherited. But I need to specify the override-checkout for the barbican-tempest-plugin. 12:13:18 at some point I guess the older branches will move to EOL 12:13:50 lpiwowar: yes, but then you can just add barbican-tempest-plugin, with its version override, to the required-projects key 12:14:16 tosky: Ok, I will fix that. 12:15:17 tosky: I agree with changing it for train and ussuri too. 12:15:48 and wallaby, there is wallaby-last 12:16:37 +1 12:16:51 +1 12:17:00 thanks! 12:18:27 @dmendiza so 12:18:37 @dmendiza are you jumping with us? ;) 12:18:49 I'm in! :) 12:18:57 \o/ 12:19:34 allright, let's go to the next topic 12:19:37 #topic Liaison Updates 12:19:59 I guess we are covered on QA front 12:20:37 xek: +1 ... We have just this patch for barbican-tempest-plugin which to me seems like good to go => https://review.opendev.org/c/openstack/barbican-tempest-plugin/+/890598 12:22:25 @lpiwowar ack 12:24:13 #topic Open Discussion 12:24:42 The SQLAlchemy 2.0 patches need reviews 12:24:44 #link https://review.opendev.org/q/topic:sqlalchemy-20+project:openstack/barbican 12:27:34 Ok, let's continue to the last topic 12:27:44 #topic Bug Review 12:28:16 There were no new bugs since our last meeting :) 12:29:04 This is it for today 12:29:39 See y'all next week! 12:29:47 #endmeeting