08:02:06 #startmeeting tacker 08:02:06 Meeting started Tue Sep 6 08:02:06 2022 UTC and is due to finish in 60 minutes. The chair is yasufum. Information about MeetBot at http://wiki.debian.org/MeetBot. 08:02:06 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 08:02:06 The meeting name has been set to 'tacker' 08:03:17 #link https://etherpad.opendev.org/p/tacker-meeting 08:03:47 there are two items on the etherpad today. 08:04:17 The first one is mine. 08:04:40 #topic releasenotes coverage 08:05:18 In the last meeting, I've mentioned to check our releasenotes. 08:06:23 It's because some features or bug fixes were missed to be merged in the latest releases. 08:07:26 So, I'd like to check them before the end of this release. 08:08:40 As described on the etherpad, roughtly 29 changes have no releasenotes 08:08:59 which has "Implement" or "Closes-Bug" tag in its commit message. 08:09:33 It's better to cover such a change in the releasenotes without tiny ones. 08:10:07 The detailed results of the survey is here. 08:10:11 #link https://etherpad.opendev.org/p/tacker-meeting-20220906-list-all-changes-in-zed 08:11:04 So, please check your patches again and upload a releasenotes if it seems better to do so. 08:11:10 that's all 08:11:15 Do you have any comment? 08:12:02 Thanks for your survey and sharing, I will tell my colleagues and post releasenote if necessary. 08:12:16 thanks :) 08:12:26 No comments from my side, we'll confirm the list and make release note if required. 08:12:41 OK, thanks. 08:12:56 So, can we go to the next item? 08:13:11 #topic About posted patch dependencies for RC1 08:13:12 Sorry, I have a question about deadline of post releasenote. 08:13:21 oops 08:13:48 We aim to post by RC1? or Final Release..? 08:14:23 I wonder it's must not be critical changes and no need to have long time for reviewing. 08:14:56 Yes, I think so too. 08:16:02 How about Sep 12? It's the first day of RC1 target week. 08:16:25 I mean the deadline of uploading releasenotes. 08:17:32 OK, I'll share the schedule with my team. 08:17:47 I agree, we should post it by Sep 12 and merge it by RC1. 08:18:12 Thanks. I'd like to add the conclusion on my item on the ehterpad. 08:19:15 OK, go to the second topic from ueha. 08:19:41 sure, I will share about posted patch dependencies for RC1. 08:20:13 Since RC1 (Sep 16) is approaching, we want to prevent a large merge conflict from occurring just before RC1. 08:20:43 It is assumed that merge conflicts will occur with CNF refactoring/enhancement patch, but there will be no major impact. 08:21:00 But, basically, it is related to the changes of the patch below, so I would like you to review it so that it can be merged as soon as possible. 08:21:10 * CNF v2 API enhance and refactor | https://review.opendev.org/c/openstack/tacker/+/855117 08:21:27 * [WIP] Helm chart support for CNF v2 API | https://review.opendev.org/c/openstack/tacker/+/855579 08:21:51 (The last one is WIP. 08:22:05 And it is clear that the some patches posted by FJ and the following UT improvement patch cause conflicts, so we want to merge them earlier. 08:22:16 Improve Unit Test for V2 API | https://review.opendev.org/c/openstack/tacker/+/848565 08:22:34 That's all from my side. 08:23:37 Do you have any comment or question? 08:23:58 thanks 08:25:15 I also do that ASAP. 08:26:12 Is there any concerns about dependency? No? 08:26:47 good 08:27:18 As we are considering the affected point, there is nothing in particular at the moment. 08:27:39 ok, good news for us :) 08:28:16 thank you :) 08:28:29 Sorry please let me clarify the request. We should merge 855117 and 855579 earlier than other related patches such as 848565 08:28:33 Is my understanding correct? 08:30:21 No, I think 848565 is in the same level as 855117 and 855579. 08:31:15 OK, so we should merge 855117, 855579 and 848565bearlier than other patches, right? 08:31:21 related patches I said is other CNF patch posted by FJ. 08:31:28 Yes 08:31:38 Understood, thanks! 08:32:13 :) 08:33:27 takahashi-tsc: Thanks for the comment. 08:34:34 It seems enough for the topic. 08:34:49 ueha: Thnak you for your mention. 08:35:05 So, do you have any other topic than on the etherpad? 08:35:25 sorry, I have a topi. Is it OK? 08:35:40 Sure, please go ahead. 08:35:55 Thanks. We are implementing the tool for DB migration, is FT implementation required? 08:36:03 https://review.opendev.org/c/openstack/tacker-specs/+/848410 08:36:14 We think the migration needs to be tested to ensure that it can be done succesfully, but the tool we are implementing is not tacker's main funtion, we want to confirm that if it is OK to test the tool by FT. 08:38:18 I'm not sure exactly, but no need to have a test, especially a functional test, in CI 08:38:29 as similar to other tools. 08:39:51 ma-ooyama: It will be implemented as a feature of tacker-db-manage, right? 08:40:12 Yes. 08:40:24 We don't have any test for the tool currently. 08:41:19 Understood. So we will implement only unit test. 08:43:16 IMO, it's better to implement some validation feature for your update to ensure it works correctly. 08:43:36 For example, dry-run for checking arguments or so. 08:43:52 Although it depends on your implementation. 08:44:28 Any other comment on the topic? 08:45:31 Thanks. I understood that the test or feature to validate tool is needed, but FT is not needed. 08:47:36 OK, it seems enough for the topic. 08:48:06 So, let's close this meeting if no one has any othere comment topic. 08:49:09 Good 08:49:21 Thanks for joining, bye! 08:49:28 Thanks, bye 08:49:28 thanks, bye 08:49:32 thanks, bye 08:49:38 bye 08:49:41 thanks,bye 08:49:49 #endmeeting