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

2015-10-13 Thread Dmitry Pyzhov
Guys, 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

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

2015-10-13 Thread Mike Scherbakov
Dmitry, 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 there. Thank you, On Tue, Oct 13, 201

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

2015-10-13 Thread Vladimir Kuklin
Dima What I think is that we need to somehow group the bugs so that after they are initially triaged particular component developers can understand which bugs to get from the pool of unassigned bugs. Could you please show how you are going to tackle this? On Tue, Oct 13, 2015 at 11:24 PM, Mike Sc