18:00:11 <macsz> #startmeeting nova-bugs-team
18:00:15 <openstack> Meeting started Tue Apr  4 18:00:11 2017 UTC and is due to finish in 60 minutes.  The chair is macsz. Information about MeetBot at http://wiki.debian.org/MeetBot.
18:00:16 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
18:00:19 <openstack> The meeting name has been set to 'nova_bugs_team'
18:01:08 <macsz> let's wait a bit
18:01:57 <macsz> anyone here? :)
18:02:37 <macsz> yes or no, let me go quickly through standard agenda
18:02:51 <macsz> #topic Current Nova Bug Stats
18:02:52 <macsz> #info 78 new bugs which need to be skimmed: https://bugs.launchpad.net/nova/+bugs?search=Search&field.status=New
18:02:52 <macsz> #info 284 confirmed and triaged bugs: https://bugs.launchpad.net/nova/+bugs?search=Search&field.status=Triaged&field.status=Confirmed
18:02:52 <macsz> #info 786 open bugs overall: https://bugs.launchpad.net/nova/
18:03:10 <macsz> #topic Reminders
18:03:17 <macsz> #info looking for volunteers for the bug-skimming duty: https://wiki.openstack.org/wiki/Nova/BugTriage#Weekly_bug_skimming_duty
18:03:24 <macsz> the bug dashboard to help you with that
18:03:30 <macsz> #link http://45.55.105.55:8082/bugs-dashboard.html
18:03:37 <macsz> #topic Open Discussion
18:04:21 <mriedem> nova bug meeting?!
18:04:30 <mriedem> i didn't think this still happened
18:04:43 <macsz> it does biweekly :)
18:04:55 <macsz> the one in EU though
18:05:00 <macsz> i dont know about that
18:06:00 <macsz> but frankly, there is rarely anything to say, I mainly maintain it so I can pay more attention to the number of bugs
18:06:08 <mriedem> ok
18:06:19 <mriedem> i think markus_z did the same
18:06:22 <macsz> which by the way is becoming ridiculous
18:06:40 <mriedem> it's under 1000 right?
18:06:49 <macsz> it is, but it is steadily increasing
18:06:56 <mriedem> yeah, i know
18:06:59 <macsz> i am partly to blame lately
18:07:06 <macsz> I went through the stale bugs list and either closed them as invalid or tagged them as New for evaluation
18:07:27 <mriedem> we are also just not in the mode of fixing bugs right now very well
18:07:31 <mriedem> because of new feature development
18:07:41 <macsz> and specs freeze
18:07:43 <macsz> yeah
18:07:50 <macsz> But i was thinking that maybe starting next week I will be posting a weekly bugs report to the ML
18:07:57 <macsz> So this may get more wide attention.
18:08:14 <macsz> and maybe someone will go and grab sth from the list
18:08:47 <macsz> we are not that far from 1000, it is 786 currently
18:09:15 <macsz> it is nearly 1 year high
18:09:59 <mriedem> attempts to get people to care more have never really taken hold over the years
18:10:01 <mriedem> it's just one of those things
18:10:14 <mriedem> unless you do a bug scrub sprint day or something
18:10:40 <macsz> so, if you, mriedem, do have nothing against, i can at least spam some stats weekly on ML
18:10:53 <mriedem> i'm fine with that if you want
18:11:09 <mriedem> i think at one point in newton we went through some of markus' dashboards on a specific day
18:11:14 <mriedem> and scrubbed some of the outstanding older bugs
18:11:30 <mriedem> yeah http://lists.openstack.org/pipermail/openstack-dev/2016-April/091456.html
18:11:45 <mriedem> maybe we should do ^ after the spec freeze
18:11:51 <mriedem> the timing is nearly identical
18:11:54 <macsz> we are close to the anniversary :)
18:12:41 <macsz> yeah, I will make a note of it and include it in bugs update on Monday
18:12:45 <macsz> good point
18:12:51 <mriedem> there is also going to be the openstack bug smash in china in may
18:12:55 <mriedem> the week after the forum
18:13:10 <mriedem> that's more about reviewing patches for bugs though
18:14:05 <macsz> noted
18:14:26 <macsz> so, i think that we can wrap it up and go back to daily duties
18:14:52 <mriedem> yup
18:15:41 <macsz> thanks for your comming, mriedem
18:15:48 <mriedem> yw
18:15:49 <macsz> you made a crowd here today :)
18:15:55 <mriedem> \o/
18:16:03 <macsz> #endmeeting