07:00:04 #startmeeting masakari 07:00:05 Meeting started Tue Sep 29 07:00:04 2020 UTC and is due to finish in 60 minutes. The chair is yoctozepto. Information about MeetBot at http://wiki.debian.org/MeetBot. 07:00:06 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 07:00:09 The meeting name has been set to 'masakari' 07:00:09 #topic Roll-call 07:00:17 o/ 07:00:50 o/ 07:01:08 o/ 07:01:32 Short question, why you folks still didn't apply for PTL elections?:) 07:01:40 Today is the last day to apply 07:02:00 noonedeadpunk: I'm a professional procrastinator 8-) 07:02:20 I see:)) 07:02:21 tbh, I was too busy to handle this 07:02:33 You have the whole day on your hands :p 07:02:46 noonedeadpunk: another busy day yeah! 07:03:56 I guess there won't be crowds today 07:04:01 #topic Agenda 07:04:09 * Roll-call 07:04:09 * Agenda 07:04:09 * Announcements 07:04:09 ** Masakari Victoria RC1 released 07:04:09 ** Launchpad moderated - series, releases, milestones etc. available now (and for all subprojects): https://launchpad.net/masakari 07:04:10 ** Masakari whiteboard ready (and wiki got improvements too): https://etherpad.opendev.org/p/masakari-whiteboard 07:04:10 ** Masakari Wallaby vPTG planned: https://etherpad.opendev.org/p/masakari-wallaby-vptg 07:04:11 * Review action items from the last meeting 07:04:11 * CI status 07:04:12 * Backports pending reviews 07:04:12 * Critical Bugs and Patches 07:04:13 * Release planning 07:04:26 #topic Announcements 07:04:34 #info Masakari Victoria RC1 released 07:04:44 < champagne showers > 07:05:24 it means that the non-client software repos now have stable/victoria branch as well 07:05:47 and the RC1 is downloadable by the public 07:06:19 thankfully we merged everything I planned for that 07:06:27 nice job 07:06:44 so it might as well end up the final release with no modifications if we don't find anything breaking 07:06:55 suzhengwei: thanks to you as well :-) 07:07:47 RC1 also means the release bot proposed a bunch of changes for both the new stable branch as well as the current master branch 07:08:00 in fact 2 changes per branch and repository: 07:08:08 #info https://review.opendev.org/#/q/(project:openstack/masakari+OR+project:openstack/masakari-monitors+OR+project:openstack/python-masakariclient+OR+project:openstack/masakari-dashboard)+status:open+owner:%22OpenStack+Release+Bot%22 07:08:40 these must not stay unmerged for too long 07:08:42 please review 07:08:50 they are usually just fine 07:09:15 but sometimes the bot can do unexpected things so it uses us hoomans to undo its wrongs 07:09:20 :-) 07:09:58 #info Launchpad moderated - series, releases, milestones etc. available now (and for all subprojects): https://launchpad.net/masakari 07:10:35 so I took some free time of mine and moderated Masakari's launchpad 07:10:44 (and now bragging about it) 07:11:10 for all seriousness, it's at least more useful now to target bugs and blueprints 07:11:41 #info Masakari whiteboard ready (and wiki got improvements too): https://etherpad.opendev.org/p/masakari-whiteboard 07:11:53 another of these keeping-me-busy changes 07:12:13 this is in part a goal of the last meeting's action I assigned to myself 07:12:45 to get better understanding of repos under control and how well they gate (or not) 07:13:25 similarly, pending reviews gives you handy links to observe what to review next 07:14:01 please use and share the love by reviewing! 07:14:12 #info Masakari Wallaby vPTG planned: https://etherpad.opendev.org/p/masakari-wallaby-vptg 07:14:29 I got us some time slots to run vPTG 07:14:36 PTG stands for Project Team Gathering 07:14:59 more details in the linked etherpad 07:15:14 please follow especially 'how to get involved' 07:15:26 suzhengwei: thanks for signing up 07:15:46 #topic Review action items from the last meeting 07:16:01 #info yoctozepto to bring some visibility to Masakari CI status 07:16:13 #info he did (see announcements) 07:16:26 #topic CI status 07:16:47 CI is green all around 07:19:17 it does not have the most up-to-date data because of no periodic jobs but we are a pretty simple project so masakari usually follows only the global failures 07:19:18 (as it is a subset of other major projects in terms of libs usage and such) 07:19:18 #topic Backports pending reviews 07:19:18 #info https://review.opendev.org/#/q/(project:openstack/masakari+OR+project:openstack/masakari-monitors+OR+project:openstack/python-masakariclient+OR+project:openstack/masakari-dashboard)+status:open+-branch:master 07:19:18 ^ using the link from the whiteboard 07:19:35 #info https://review.opendev.org/#/q/(project:openstack/masakari+OR+project:openstack/masakari-monitors+OR+project:openstack/python-masakariclient+OR+project:openstack/masakari-dashboard)+status:open+-branch:master 07:19:41 (did not notice bot being slow) 07:20:02 please notice, some are not backports, as I said they are bot-generated custom changes 07:20:07 others are backports I proposed 07:20:24 please review them and possibly approve, these ones are pretty straightforward imho 07:21:13 #topic Critical Bugs and Patches 07:21:30 none I am aware of 07:21:34 anyone? 07:22:11 I have none. 07:23:09 #topic Release planning 07:23:22 #info RC1 behind us 07:23:45 nothing to do at the moment except for reviewing the bot patches 07:23:52 but please have the future in mind 07:24:20 #topic Open discussion 07:24:41 I've got one topic for it 07:24:43 #info https://review.opendev.org/726761 - should backport or not? 07:24:58 noonedeadpunk's change kinda depends on the above 07:25:05 I think both deserve a backport 07:25:34 but the one linked above can be a bit disruptive if someone relied on the bug 07:25:41 (which is wrong but we know how life goes) 07:26:03 I count on suzhengwei's understanding of code to decide 07:26:17 we can also merge noonedeadpunk's patch by adapting it 07:26:18 I really would be pretty cutious backporting so big changes... 07:26:19 it won't be hard 07:26:36 *cautios 07:26:55 noonedeadpunk: I reviewed it quite thoroughly; it's not bad per itself but I can easily imagine someone relying on giving a fake segment id :-) 07:27:11 suzhengwei: what do you think 07:27:40 I don't really think that such things should be really reliad and we should take such usecases into big consideration. 07:28:12 s/reliad/relied 07:28:34 noonedeadpunk: yeah, one should not have relied on this quirk but could 07:28:46 that's why I'm hesitant to backport 07:29:08 I care for your opinion too, noonedeadpunk, so it looks like a no-go to me 07:29:10 we can talk about this in vPTG. 07:29:12 but we can backport nothing as well, which also an option :p 07:29:33 suzhengwei: sure thing 07:30:02 noonedeadpunk: yours is a pretty much a sanity fix 07:30:09 noonedeadpunk: the other one not 07:30:29 as it seem too much effort and risk for backporting fix without which everyone except me are fine 07:31:06 and honestly, I have already patched mine deployment and can live nicely until V 07:31:15 noonedeadpunk: true that, as well 07:31:20 well, that sets it 07:31:23 #info not backporting 07:31:35 +1 07:31:40 it's an open discussion, folks 07:31:48 anything you want to discuss? 07:32:07 I have create wallaby spec repository, please move unmerged specs from old releases to W. 07:32:19 ^ ++ 07:32:19 https://review.opendev.org/#/c/754579/ 07:32:32 indeed, it's more of a topic for the vPTG itself 07:32:50 but we've got unimplemented specs from past cycles 07:33:11 the thing is - anyone who wants to work on them can now repropose them in wallaby 07:33:19 if you need help with that, don't hesitate to ask 07:34:03 (help with reproposing that is, I'm really not volunteering to help in implementation :-) ) 07:36:51 well, if that's all, I'll be closing the meeting 07:37:05 you can always ping me here, or drop me a mail if need be 07:37:21 thank you for participating 07:37:42 #endmeeting