[openstack-dev] [Fuel] Changes in bugs workflow on Launchpad

Dmitry Pyzhov dpyzhov at mirantis.com
Tue Oct 13 18:29:29 UTC 2015


I propose several changes in bugs workflow on Launchpad.
1) Let's stop using component based team groups as assignees for bugs
2) Let's create separate Launchpad projects for qa, docs and infra teams

It will affect everyone who tracks any list of bugs. So I want to be sure
that everyone can ask question or raise concern.

Why do we need this? We are growing community. In 7.0 release we addressed
2153 bugs. This number is almost unmanageable. We have a lot of tags (99
official and 219 other tags), a lot of Launchpad groups. We have several
big teams with their own workflows. We have 1482 bugs in our current
release. In order to understand if a bug in really a bug or some kind of
support request one have to analyse its tags, assignee and teams of
assignee. And there is a chance that the analysis will produce wrong result.

I'm trying to make our bug management as clear as possible and produce as
little extra everyday mouse clicking as possible. Here is list of required
changes: https://etherpad.openstack.org/p/fuel-bugs-taxonomy

Feel free to ask questions.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20151013/3a8f19a9/attachment.html>

More information about the OpenStack-dev mailing list