<div dir="ltr">Hi folks,<div><br></div><div>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.</div><div><br></div><div>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.</div><div><br></div><div></div><div>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]).</div><div><br></div><div>Feedback most welcome.</div><div><br></div><div>Many thanks,</div><div>Armando</div><div><br></div><div><br></div><div><div>[1] <a href="http://git.openstack.org/cgit/openstack/election/tree/candidates/mitaka/Neutron/Armando_Migliaccio.txt#n25" target="_blank">http://git.openstack.org/cgit/openstack/election/tree/candidates/mitaka/Neutron/Armando_Migliaccio.txt#n25</a></div></div><div>[2] <a href="http://docs.openstack.org/developer/neutron/policies/index.html" target="_blank">http://docs.openstack.org/developer/neutron/policies/index.html</a></div><div>[3] <a href="https://review.openstack.org/#/c/228733/" target="_blank">https://review.openstack.org/#/c/228733/</a></div></div>