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