[openstack-dev] [Fuel] Changes in bugs workflow on Launchpad
mscherbakov at mirantis.com
Tue Oct 13 20:24:41 UTC 2015
I think that #1 is reasonable.
For #2, separate LP projects, I'd want to assess pros/cons before making a
decision. I see more cons at the moment. I've started adding it in the
etherpad, I'd appreciate if other folks would join and provide their input
On Tue, Oct 13, 2015 at 11:34 AM Dmitry Pyzhov <dpyzhov at mirantis.com> wrote:
> 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.
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the OpenStack-dev