Re: [openstack-dev] [Neutron] Bug deputy process

2015-12-05 Thread Gary Kotton
From: "Armando M." mailto:arma...@gmail.com>> Reply-To: OpenStack List mailto:openstack-dev@lists.openstack.org>> Date: Saturday, December 5, 2015 at 1:27 AM To: OpenStack List mailto:openstack-dev@lists.openstack.org>> Subject: Re: [openstack-dev] [Neutron] Bug dep

Re: [openstack-dev] [Neutron] Bug deputy process

2015-12-04 Thread Armando M.
On 4 December 2015 at 15:15, Carl Baldwin wrote: > On Thu, Dec 3, 2015 at 9:29 AM, Kyle Mestery wrote: > > One concern I have is ensuring we rotate people, because it does take > some > > time, and if the same handful of rotate, they will burn out. So I > actively > > encourage more people to vo

Re: [openstack-dev] [Neutron] Bug deputy process

2015-12-04 Thread Carl Baldwin
On Thu, Dec 3, 2015 at 9:29 AM, Kyle Mestery wrote: > One concern I have is ensuring we rotate people, because it does take some > time, and if the same handful of rotate, they will burn out. So I actively > encourage more people to volunteer, you don't even have to be a Neutron core > reviewer to

Re: [openstack-dev] [Neutron] Bug deputy process

2015-12-03 Thread Armando M.
On 3 December 2015 at 14:20, Ryan Moats wrote: > I missed this the first time around, but I concur with the comments of the > other deputies - > the effort only took me about an hour or two a day and I think it's been > rather helpful :) > Btw, have a look at [1,2] to see if that suits your subs

Re: [openstack-dev] [Neutron] Bug deputy process

2015-12-03 Thread Ryan Moats
I missed this the first time around, but I concur with the comments of the other deputies - the effort only took me about an hour or two a day and I think it's been rather helpful :) Ryan Moats (regXboi) __ OpenStack Developme

Re: [openstack-dev] [Neutron] Bug deputy process

2015-12-03 Thread Sean M. Collins
> One concern I have is ensuring we rotate people, because it does take some > time, and if the same handful of rotate, they will burn out. So I actively > encourage more people to volunteer, you don't even have to be a Neutron > core reviewer to do this! I actually didn't realize that it didn't r

Re: [openstack-dev] [Neutron] Bug deputy process

2015-12-03 Thread Armando M.
On 3 December 2015 at 10:48, Johnston, Nate wrote: > I second that - I don’t have the ability to triage a bug. But I would be > happy to take a watch if I could. > Anyone has the ability to triage bugs, but some don't have full privileges (like assigning milestones, owner or severity) as they d

Re: [openstack-dev] [Neutron] Bug deputy process

2015-12-03 Thread Armando M.
On 3 December 2015 at 10:42, Smigiel, Dariusz wrote: > > From: Kyle Mestery [mailto:mest...@mestery.com] > [...] > > One concern I have is ensuring we rotate people, because it does take > some time, and if the same handful of rotate, they will burn out. So I > actively encourage more people to v

Re: [openstack-dev] [Neutron] Bug deputy process

2015-12-03 Thread Sean M. Collins
On Thu, Dec 03, 2015 at 10:58:07AM EST, Ihar Hrachyshka wrote: > The thing I would like us to see enhanced is making sure that tags set to > bugs are actively tracked by corresponding teams. Thanks - you just reminded me to tag two bugs that I had just touched. :) -- Sean M. Collins __

Re: [openstack-dev] [Neutron] Bug deputy process

2015-12-03 Thread Miguel Angel Ajo
I can only agree with the opinions others already expressed. It’s been a very good initiative. Going through the bugs everyday during my week opened my eyes to how the end users face bugs, an the kind of issues we have. I got myself educated into following the incoming bug stream from launchpad

Re: [openstack-dev] [Neutron] Bug deputy process

2015-12-03 Thread Johnston, Nate
I second that - I don’t have the ability to triage a bug. But I would be happy to take a watch if I could. —N. > On Dec 3, 2015, at 1:42 PM, Smigiel, Dariusz > wrote: > >> From: Kyle Mestery [mailto:mest...@mestery.com] > [...] >> One concern I have is ensuring we rotate people, because it

Re: [openstack-dev] [Neutron] Bug deputy process

2015-12-03 Thread Smigiel, Dariusz
> From: Kyle Mestery [mailto:mest...@mestery.com] [...] > One concern I have is ensuring we rotate people, because it does take some > time, and if the same handful of rotate, they will burn out. So I actively > encourage more people to volunteer, you don't even have to be a Neutron core > revi

Re: [openstack-dev] [Neutron] Bug deputy process

2015-12-03 Thread Doug Wiegley
Roughly an hour a day, and super useful. I’d echo that anyone can volunteer, since a lot of the job is reaching out to various folks for input (docs/policies/neutron-teams.rst is the map of truth.) I found a lot of bugs that I care about in the pre-mitaka backlog, that I didn’t know existed. Th

Re: [openstack-dev] [Neutron] Bug deputy process

2015-12-03 Thread Kyle Mestery
On Wed, Dec 2, 2015 at 10:49 AM, Armando M. wrote: > Hi neutrinos, > > It's been a couple of months that the Bug deputy process has been in place > [1,2]. Since the beginning of Mitaka we have collected the following > statistics (for neutron and neutronclient): > > Total bug reports: 373 > >

Re: [openstack-dev] [Neutron] Bug deputy process

2015-12-03 Thread Armando M.
On 3 December 2015 at 01:42, Rossella Sblendido wrote: > Hi Armando, > > On 12/02/2015 07:49 PM, Armando M. wrote: > >> Hi neutrinos, >> >> It's been a couple of months that the Bug deputy process has been in >> place [1,2]. Since the beginning of Mitaka we have collected the >> following statist

Re: [openstack-dev] [Neutron] Bug deputy process

2015-12-03 Thread Armando M.
On 3 December 2015 at 07:58, Ihar Hrachyshka wrote: > Armando M. wrote: > > Hi neutrinos, >> >> It's been a couple of months that the Bug deputy process has been in >> place [1,2]. Since the beginning of Mitaka we have collected the following >> statistics (for neutron and neutronclient): >> >>

Re: [openstack-dev] [Neutron] Bug deputy process

2015-12-03 Thread Armando M.
On 2 December 2015 at 17:38, Sean M. Collins wrote: > I was not a deputy - but I had been subscribed to launchpad bugs for > years, but had a procmail filter set so it went into a folder that prior > to this new initiative, had remained unread for years. As part of this > new effort I try and spe

Re: [openstack-dev] [Neutron] Bug deputy process

2015-12-03 Thread Armando M.
On 2 December 2015 at 11:02, Salvatore Orlando wrote: > I only have some historical, anecdotal, and rapidly waning memory of > previous releases. > Nevertheless my feeling is that the process has been a success so far. > In past times it would not have been a surprise if a bug fell under the > ra

Re: [openstack-dev] [Neutron] Bug deputy process

2015-12-03 Thread Ihar Hrachyshka
Armando M. wrote: Hi neutrinos, It's been a couple of months that the Bug deputy process has been in place [1,2]. Since the beginning of Mitaka we have collected the following statistics (for neutron and neutronclient): Total bug reports: 373 • Fix committed: 144 • Unassi

Re: [openstack-dev] [Neutron] Bug deputy process

2015-12-03 Thread Rossella Sblendido
Hi Armando, On 12/02/2015 07:49 PM, Armando M. wrote: Hi neutrinos, It's been a couple of months that the Bug deputy process has been in place [1,2]. Since the beginning of Mitaka we have collected the following statistics (for neutron and neutronclient): Total bug reports: 373 * Fix commit

Re: [openstack-dev] [Neutron] Bug deputy process

2015-12-02 Thread Sean M. Collins
I was not a deputy - but I had been subscribed to launchpad bugs for years, but had a procmail filter set so it went into a folder that prior to this new initiative, had remained unread for years. As part of this new effort I try and spend at least 15 minutes a day checking the folder and working o

Re: [openstack-dev] [Neutron] Bug deputy process

2015-12-02 Thread Salvatore Orlando
I only have some historical, anecdotal, and rapidly waning memory of previous releases. Nevertheless my feeling is that the process has been a success so far. In past times it would not have been a surprise if a bug fell under the radar until that well known brownish matter hit the proverbial fan.