14:01:22 <mnasiadka> #startmeeting kolla
14:01:22 <opendevmeet> Meeting started Wed Jan 10 14:01:22 2024 UTC and is due to finish in 60 minutes.  The chair is mnasiadka. Information about MeetBot at http://wiki.debian.org/MeetBot.
14:01:22 <opendevmeet> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
14:01:22 <opendevmeet> The meeting name has been set to 'kolla'
14:01:26 <mnasiadka> #topic rollcall
14:01:27 <mnasiadka> o/
14:01:29 <SvenKieske> o/
14:01:30 <SvenKieske> :D
14:02:00 <mmalchuk> o/
14:02:22 <mhiner> o/
14:02:43 <bbezak> o/
14:03:06 <jangutter> o/
14:03:38 <mnasiadka> #topic agenda
14:03:38 <mnasiadka> * Review action items from the last meeting
14:03:38 <mnasiadka> * CI status
14:03:38 <mnasiadka> * Release tasks
14:03:38 <mnasiadka> * Regular stable releases (first meeting in a month)
14:03:40 <mnasiadka> * Current cycle planning
14:03:40 <mnasiadka> * Additional agenda (from whiteboard)
14:03:42 <mnasiadka> * Open discussion
14:03:45 <mnasiadka> #topic CI status
14:03:57 <mnasiadka> I think the CI is overall green, with some amber here and there
14:04:01 <mnasiadka> but haven't seen any total breakage
14:04:11 <mnasiadka> #topic Release tasks
14:04:43 <mnasiadka> We've reverted the branch changes - so we're building from master now and running master in kolla-ansible
14:04:57 <mnasiadka> What we omitted, is that we use master a-c-k on stable/2023.2 branch
14:05:03 <mnasiadka> any volunteers to fix this?
14:06:19 <mmalchuk> I can try
14:06:49 <mnasiadka> ok then
14:07:00 <mnasiadka> #topic Regular stable releases (first meeting in a month)
14:07:20 <mnasiadka> Anybody happy to follow the regular stable releases procedure after mmalchuk fixes a-c-k in 2023.2?
14:07:58 <bbezak> sure
14:08:00 <bbezak> can do
14:10:01 <mnasiadka> fantastic
14:10:01 <mnasiadka> #topic Current cycle planning
14:10:26 <mnasiadka> Let me check if we have Caracal priorities populated on the whiteboard
14:10:50 <mnasiadka> https://etherpad.opendev.org/p/KollaWhiteBoard#L207
14:10:54 <mnasiadka> nope, only Kayobe it seems
14:11:13 <SvenKieske> afaik there should be some stuff there, I fuzzily remember I wanted to pester the infra team with stuff to mirror?
14:12:07 <SvenKieske> should we add stuff from https://etherpad.opendev.org/p/kolla-caracal-ptg#L111 ? not sure about the process here
14:12:19 <mnasiadka> Yes, I'll populate it
14:12:27 <mnasiadka> But not now, for the sake of the meeting
14:12:31 <mnasiadka> Anything anybody is working on?
14:12:40 <SvenKieske> okay, I see it. awesome :)
14:12:42 <mnasiadka> Maybe the quorum queues backports?
14:13:06 <SvenKieske> yeah I hope I get to that in the next weeks, I also have read your suggestions on changing things a bit
14:13:27 <SvenKieske> just currently swamped with back-from-vacation and other stuff
14:13:32 <mnasiadka> Sure :)
14:15:53 <mnasiadka> Ok, I see nothing fancy
14:15:59 <mnasiadka> let's go forward then
14:16:08 <mnasiadka> #topic Additional agenda (from whiteboard)
14:16:36 <mnasiadka> frickler is not around, but some topics from him
14:16:44 <mnasiadka> I guess we'll talk about them next week
14:17:24 <mnasiadka> seems nothing else on the whiteboard topics
14:17:30 <mnasiadka> #topic Open discussion
14:17:36 <mnasiadka> Anybody anything?
14:18:15 <SvenKieske> I worked on shellcheck end of last year, if someone is also interested
14:18:17 <mmalchuk> simple question
14:18:51 <mmalchuk> can we create backports along with master change
14:19:06 <mmalchuk> why cores show bad practice?
14:19:49 <mmalchuk> kevko what do you think?
14:20:08 <mnasiadka> you can create backports when you want, but to merge them we need the commit id from master
14:20:50 <mmalchuk> so creating bunch of reviews is fine?
14:21:31 <mmalchuk> ok then, thats all from me
14:24:26 <mnasiadka> mmalchuk: what do you mean by creating bunch of reviews?
14:24:35 <mnasiadka> creating backports when master is not merged yet?
14:24:58 <mnasiadka> I agree it's an antipattern, and you need to refresh those backports after master gets merged
14:25:29 <mnasiadka> And probably it creates some mess, but core's should always check if change is merged in master already
14:26:10 <mnasiadka> seems we're done with the meeting
14:26:12 <mmalchuk> mnasiadka too many reviews in gerrit without WIP
14:26:32 <kevko> Hi
14:26:40 <mnasiadka> Ah, just last but not least - I will be off for the next two weeks - bbezak gladly agreed to manage the meetings
14:26:42 <mnasiadka> so please behave :)
14:26:52 <mmalchuk> after master changes the same count of reviews in stable branches again and again
14:27:29 <mmalchuk> with only source commit hash changed
14:28:27 <mmalchuk> thats all
14:28:49 <mmalchuk> mnasiadka thanks and good weekend
14:29:00 <mnasiadka> kevko: the main ask is to create backports AFTER the master patch is merged
14:29:12 <mnasiadka> I agree sometimes we backport something to check if it passes upgrade jobs or whatever
14:29:13 <mmalchuk> yep
14:29:15 <SvenKieske> yeah, sometimes it would be nice to be able to merge backports faster. well it is what it is.
14:29:18 <mnasiadka> but that should be rather exception
14:29:41 <mmalchuk> SvenKieske not in all cases)
14:29:46 <mnasiadka> yes, a nice reminder to core reviewers to have a look on backports section of the dashboard
14:30:25 <mnasiadka> ok, enough for today
14:30:39 <mnasiadka> Thank you all for coming!
14:30:41 <mnasiadka> #endmeeting