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/
__________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
