[openstack-dev] [Fuel][Plugins] Plugins on separate launchpad projects

Igor Kalnitsky ikalnitsky at mirantis.com
Sat Jul 25 11:03:17 UTC 2015

Hello Patrick,

Thank you for raising this topic. I think that it'd be nice to create
a separate projects for Fuel plugins if it wasn't done yet. Fuel
plugins have different release cycles and do not share core group. So
it makes pretty much sense to me to create separate projects.

Otherwise, I have no idea how to work with LP's milestones since again
- plugins have different release cycles.


On Fri, Jul 24, 2015 at 8:27 PM, Patrick Petit <ppetit at mirantis.com> wrote:
> Hi There,
> I have been thinking that it would make a lot of sense to have separate
> launchpad projects for Fuel plugins.
> The main benefits I foresee….
> - Fuel project will be less of a bottleneck for bug triage and it should be
> more effective to have team members do the bug triage. After all, they are
> best placed to make the required judgement call.
> - A feature can be spread across multiple plugins, like it’s the case with
> LMA toolchain, and so it would be better to have a separate project to
> regroup them.
> - It is counter intuitive and awkward to create blueprints for plugins in
> Fuel project itself in addition to making it cluttered with stuffs that
> unrelated to Fuel.
> Can you please tell me what’s your thinking about this?
> Thanks
> Patrick
> --
> Patrick Petit
> Mirantis France
> __________________________________________________________________________
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

More information about the OpenStack-dev mailing list