[openstack-dev] [Neutron] Defect management

Armando M. armamig at gmail.com
Fri Oct 2 00:37:11 UTC 2015

Hi neutrinos,

Whilst we go down the path of revising the way we manage/process bugs in
Neutron, and transition to the proposed model [1], I was wondering if I can
solicit some volunteers to screen the bugs outlined in [2]. It's only 24
bugs so it should be quick ;)

Btw, you can play with filters and Google sheets Insights to see how well
(or bad) we've done this week.


[1] https://review.openstack.org/#/c/228733/

On 28 September 2015 at 23:06, Armando M. <armamig at gmail.com> wrote:

> Hi folks,
> One of the areas I would like to look into during the Mitaka cycle is
> 'stability' [1]. The team has done a great job improving test coverage, and
> at the same time increasing reliability of the product.
> However, regressions are always around the corner, and there is a huge
> backlog of outstanding bugs (800+ of new/confirmed/triaged/in progress
> actively reported) that pressure the team. Having these slip through the
> cracks or leave them lingering is not cool.
> To this aim, I would like to propose a number of changes in the way the
> team manage defeats, and I will be going through the process of proposing
> these changes via code review by editing [2] (like done in [3]).
> Feedback most welcome.
> Many thanks,
> Armando
> [1]
> http://git.openstack.org/cgit/openstack/election/tree/candidates/mitaka/Neutron/Armando_Migliaccio.txt#n25
> [2] http://docs.openstack.org/developer/neutron/policies/index.html
> [3] https://review.openstack.org/#/c/228733/
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20151001/1a110fa0/attachment.html>

More information about the OpenStack-dev mailing list