Re: [openstack-dev] [Fuel][Plugins] One plugin - one Launchpad project

2016-05-04 Thread Sheena Conant
9:49 AM *To:* openstack-dev@lists.openstack.org *Subject:* [openstack-dev] [Fuel][Plugins] One plugin - one Launchpad project Hi to everyone, as you possibly know (at least, those dev. teams working on their Fuel plugins) we have a fuel-plugins Launchpad project [1] which serves as all-in-one

Re: [openstack-dev] [Fuel][Plugins] One plugin - one Launchpad project

2016-05-02 Thread Evgeniy L
Hi Irina, I fully support the idea of creating separate launchpad project for each plugin, because plugins have different release cycles and different teams who support them. Fuel Plugin documentation [2] has to be updated with information for plugin developers (how to setup new project) and for

Re: [openstack-dev] [Fuel][Plugins] One plugin - one Launchpad project

2016-04-21 Thread Neil Jerram
On 19/04/16 16:52, Irina Povolotskaya wrote: > Hi to everyone, > > as you possibly know (at least, those dev. teams working on their Fuel > plugins) we have a fuel-plugins Launchpad project [1] which serves as > all-in-one entry point for filing bugs, related > to plugin-specific problems. > >

[openstack-dev] [Fuel][Plugins] One plugin - one Launchpad project

2016-04-19 Thread Irina Povolotskaya
Hi to everyone, as you possibly know (at least, those dev. teams working on their Fuel plugins) we have a fuel-plugins Launchpad project [1] which serves as all-in-one entry point for filing bugs, related to plugin-specific problems. nevertheless, this single project is a bad idea in terms of