yasufum | Hi tacker team. | 08:00 |
---|---|---|
ueha | Hi | 08:00 |
manpreetk | hi | 08:01 |
k_fukaya | hi | 08:01 |
yasufum | #startmeeting tacker | 08:01 |
opendevmeet | Meeting started Tue Nov 29 08:01:46 2022 UTC and is due to finish in 60 minutes. The chair is yasufum. Information about MeetBot at http://wiki.debian.org/MeetBot. | 08:01 |
opendevmeet | Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. | 08:01 |
opendevmeet | The meeting name has been set to 'tacker' | 08:01 |
yasufum | #link https://etherpad.opendev.org/p/tacker-meeting | 08:02 |
yasufum | There are five items on the etherpad today. | 08:02 |
yasufum | ueha: can you start from your update? | 08:02 |
ueha | Okay, I will start | 08:03 |
ueha | I have just information sharing about Legacy API deprecation. | 08:03 |
ueha | I have emailed to Discuss-ML on Nov 25, and no one replied to this thread as for now. | 08:03 |
ueha | https://lists.openstack.org/pipermail/openstack-discuss/2022-November/031307.html | 08:03 |
ueha | That's all from my side. | 08:04 |
ueha | any comment? | 08:04 |
yasufum | No reply on the thread? | 08:04 |
ueha | Yes | 08:04 |
yasufum | ok | 08:05 |
yasufum | go on to the next | 08:05 |
yasufum | Next two items are mine, but same topic actually | 08:05 |
yasufum | Although I've asked mapreetk to change unmaintained bugs status, I also started to the task. | 08:06 |
yasufum | Because it's better to do in parallel. | 08:07 |
yasufum | Basically, I'm changing the status to "Won't fix" for old items. | 08:08 |
yasufum | Around 2020 or before ones. | 08:08 |
yasufum | However, there are some items the current status is not clear, for me at least. | 08:09 |
yasufum | So, I'd appreciate if you help me to clarify them. | 08:10 |
yasufum | I've just listed up the bugs on the etherpad. | 08:10 |
yasufum | Let me know by leaving some comment on each report if you know something about. | 08:11 |
yasufum | That's all for the second item. | 08:11 |
yasufum | Any comment? | 08:11 |
ueha | Thanks for your work! I will check with my colleague. | 08:12 |
yasufum | thx | 08:12 |
yasufum | good | 08:12 |
yasufum | The third item of mine is also the chaning the status. | 08:13 |
ueha | Which one should we update, launchpad or etherpad or both? | 08:13 |
yasufum | On launchpad is enough. | 08:14 |
ueha | Okay, I got, thank you! | 08:14 |
yasufum | ok | 08:14 |
yasufum | There three items for which I can change to "Won't fix" but not so sure. | 08:15 |
yasufum | s/I can/I think we can/ | 08:16 |
yasufum | Please tell me if there is a bug we shouldn't change the status. | 08:17 |
yasufum | on launchpad | 08:17 |
yasufum | If no comment until next week, I'll change the status. | 08:18 |
yasufum | That's all. | 08:18 |
yasufum | If no one has comment, go to the next item. | 08:19 |
yasufum | good | 08:20 |
yasufum | manpreetk: can you share about your update for bug triage activity? | 08:20 |
manpreetk | Yes!! Thanks | 08:20 |
manpreetk | First of all would like to thanks yasufum for helping hand. | 08:21 |
yasufum | you're welcome. | 08:21 |
manpreetk | This update is regarding bug triage activity reporting process. | 08:21 |
manpreetk | Added a bug triage roaster etherpad [1] and submit report of bug triage done last week [2]. | 08:22 |
manpreetk | [1] https://etherpad.opendev.org/p/tacker-bug-triage-roaster | 08:22 |
manpreetk | [2] https://etherpad.opendev.org/p/tacker-bug-triage-20221128 | 08:22 |
manpreetk | The bug triage reporting or recording in etherpad can be optional. IMO, it will be helpful if we need discussion or keep track of bugs (open/in-progress) status. But would like to here team's opinion. | 08:22 |
manpreetk | Thats all for this topic. | 08:23 |
yasufum | Is there any rules for changing the status to "Invalid"? | 08:24 |
yasufum | Because we agreed to change it to "Won't fix" at once. | 08:25 |
manpreetk | There isn't any specific rule, i changed those bugs which were irreproducible in master branch to "Invalid". | 08:26 |
manpreetk | Umm if you suggest i ll change them to "Wont fix". | 08:27 |
yasufum | I don't mean so actually. | 08:28 |
yasufum | I've just though it's better to have some more correct rules if possible. | 08:29 |
manpreetk | Guess that will be helpful, we can update the same in https://etherpad.opendev.org/p/tacker-bugtriage | 08:29 |
yasufum | But I've also understood that it depends on each cases and difficult to. | 08:30 |
yasufum | Anyway, we don't need to so serious about which category is the most appropriate for too old bugs actually. | 08:32 |
manpreetk | Yes agree!! | 08:32 |
yasufum | Any other comment, guys? | 08:33 |
yasufum | Or we can go to the next item? | 08:33 |
yasufum | good | 08:34 |
yasufum | manpreetk: let's move on to the next one. | 08:34 |
manpreetk | Yes please. | 08:34 |
manpreetk | This is regarding migration of tacker CI/CD jobs to Ubuntu Jammy (22.04). | 08:35 |
manpreetk | As per OpenStack TC discussion, we need to run at least one job on Focal which can be removed in next cycle. | 08:35 |
manpreetk | Would like to seek Tacker team's opinion whether we should run sol or sol-v2 gate jobs in focal? | 08:35 |
manpreetk | Additionally once we select between above shared choices, do we need to run sol-kubernetes or sol-v2-kubernetes? | 08:35 |
yasufum | ueha: do you have any comment? | 08:36 |
yasufum | Or anyone? | 08:37 |
ueha | IMO, both sol-v2 and sol-kubernetes-v2 are appropriate. What do you think others? | 08:38 |
manpreetk | +1 | 08:38 |
yasufum | I basically agree, but not for both. | 08:39 |
manpreetk | yeah maybe we can skip kubernetes one? | 08:39 |
yasufum | It just a short term support for focal. | 08:39 |
yasufum | and don't need to have several tests for that. | 08:40 |
yasufum | In other word, simple is better for maintenance. | 08:41 |
yasufum | What do you think? | 08:41 |
ueha | Does this mean that we don't need to check the operation of VIM type supported by Tacker on an old OS? | 08:42 |
manpreetk | yasufum: You mean to run few test cases in the focal gate job?? | 08:42 |
yasufum | I think so. | 08:42 |
yasufum | I think focal is not a mainstream anymore. | 08:43 |
ueha | If so, I agree that the sol-v2 test is enough for maintenances. | 08:45 |
yasufum | Any other comment? | 08:47 |
yasufum | good | 08:48 |
manpreetk | Thanks for discussion will update the conclusion in etherpad, as well push separate patch for focal jobs. | 08:48 |
yasufum | manpreetk: Many thanks for your work for migrating to jammy! | 08:49 |
manpreetk | Your welcome!! | 08:49 |
yasufum | All items done for today | 08:50 |
yasufum | But do you have any other topic? | 08:50 |
yasufum | for asking review or so? | 08:50 |
manpreetk | Thanks and Bye! | 08:52 |
yasufum | good | 08:53 |
yasufum | So, let's close this meeting. | 08:53 |
yasufum | bye! | 08:53 |
ueha | Thanks, bye! | 08:53 |
manpreetk | Bye!!! | 08:53 |
takahashi-tsc | Thanks | 08:53 |
yuta-kazato | bye | 08:53 |
yasufum | #endmeeting | 08:53 |
opendevmeet | Meeting ended Tue Nov 29 08:53:51 2022 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | 08:53 |
opendevmeet | Minutes: https://meetings.opendev.org/meetings/tacker/2022/tacker.2022-11-29-08.01.html | 08:53 |
opendevmeet | Minutes (text): https://meetings.opendev.org/meetings/tacker/2022/tacker.2022-11-29-08.01.txt | 08:53 |
opendevmeet | Log: https://meetings.opendev.org/meetings/tacker/2022/tacker.2022-11-29-08.01.log.html | 08:53 |
*** dasm|off is now known as dasm | 13:05 | |
*** dasm is now known as dasm|off | 21:39 |
Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!