08:02:24 <yasufum> #startmeeting tacker
08:02:24 <opendevmeet> Meeting started Mon Jun 22 08:02:24 2026 UTC and is due to finish in 60 minutes.  The chair is yasufum. Information about MeetBot at http://wiki.debian.org/MeetBot.
08:02:24 <opendevmeet> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
08:02:24 <opendevmeet> The meeting name has been set to 'tacker'
08:02:37 <yasufum> #link https://etherpad.opendev.org/p/tacker-meeting
08:02:54 <yasufum> Let's start today's meeting.
08:03:20 <yasufum> Just one topic on the etherpad today.
08:03:23 <yasufum> #topic Eventlet Removal activity in Tacker - follow-up discussion on Patch Management
08:04:04 <shivam> This topic is a follow-up discussion on the Tacker Eventlet Removal activity, continuing from the previous IRC meeting on 08/06/2026.
08:04:47 <shivam> As some members have already started working on their assigned category changes/migration, we would like to discuss how to manage and review patches for these changes, to avoid merge conflicts and dependency issues between categories.
08:05:47 <shivam> one option/approach could be: Each member raises a DNM patch for their category
08:06:22 <shivam> if required, validates it using 'Depends-On' between dependent categories
08:07:27 <shivam> and once all categories changes are done and DNM patch build is success, everything is combined into a single final patch for review and merge.
08:08:08 <shivam> However, one concern with this approach is that one large, combined patch may be difficult to review and harder to trace if a bug is found later.
08:08:27 <shivam> I would like to hear community's thoughts on proposed suggestion for Patch Management.
08:08:38 <shivam> Are there any other suggestions from community for handling Eventlet removal related patches?
08:08:45 <shivam> Thank you.
08:08:54 <yasufum> thanks
08:09:04 <yasufum> Any comment?
08:10:06 <takahashi-tsc> Is this approach also adopted by Nova or Neutron project?
08:11:00 <shivam> hmm... no.
08:11:44 <shivam> For Nova md Neutron, multiple patches were merged independently. All changes were not merged in single patch.
08:13:07 <takahashi-tsc> Oh, I think if they faced the similar issues, it is very helpful as referece. Anyway, let's discuss it. I'd like to hear community members' opinions.
08:17:53 <yasufum> I have nothing opposite to your approach. I think it might not be a problem if a single large patch is proposed.
08:20:39 <takahashi-tsc> I believe we need to confirm with members who will actually proceed with development, such as koba-san, Bertrand, etc.
08:21:18 <takahashi-tsc> But this week is NFV week and some members are not here today... (To be honest, I'm also joining NFV meeting.)
08:26:34 <yasufum> Is it enough for today?
08:27:47 <shivam> hmm.. I think yes. I will follow up on this topic in next IRC when all members are present.
08:27:53 <shivam> Thanks
08:28:12 <yasufum> OK, thanks.
08:30:15 <takahashi-tsc> I also do not have further commnets.
08:30:38 <yasufum> shivam: And I'd also appreciate that your patch has been merged finally after several unexpected failures. We can merge rest of our critical patches.
08:30:51 <yasufum> https://review.opendev.org/c/openstack/tacker/+/992221
08:31:18 <shivam> Thank you.
08:31:41 <yasufum> So, let's close this meting.
08:31:49 <yasufum> Thank you for joining, bye!
08:32:00 <shivam> Thank you, bye!
08:32:01 <takahashi-tsc> bye
08:32:03 <yasufum> #endmeeting