[openstack-dev] [Neutron] Plugin and Driver Inclusion Requirements
sorlando at nicira.com
Fri Nov 15 20:30:06 UTC 2013
I also completely agree with this policy - and I hope all the developers
contributing code to non-core plugins like me will agree as well.
There is nothing like verifiability. This will also make a lot easier code
reviews for non-core plugins; one of the reasons for which these reviews
tend to have a higher turnaround is that reviewers have a really hard time
and very often can't tell whether the code they're reviewing will actually
work or not.
So, I would say this is not additional burden being asked to contributors,
but is actually good for plugin developers as well.
We're already working to ensure the plugin we contribute to is compliant
with this policy.
Otherwise there is the following workaround
git clone git://github.com/openstack/neutron.git
git rm -r neutron/plugins/<your_plugin_name>
gir rm -r neutron/tests/unit/<your_plugin_name>
git rm -r etc/neutron/plugins/<your_plugin_name>
git commit -a
[The thing about the workaround was meant to be humorous]
On 15 November 2013 16:23, Russell Bryant <rbryant at redhat.com> wrote:
> On 11/14/2013 08:00 PM, Dan Smith wrote:
> >> - Each third party plugin/driver shall designate a point of contact for
> >> the coordinated release cycle.
> >> - To be designated as compatible, a third-party plugin and/or driver
> >> code must implement external third party integration testing.
> >> - Policy is in effect immediately for new plugin/drivers.
> >> - Existing plugin/drivers have until Icehouse-2 to become compliant.
> > I just wanted to say that I think this aggressive approach is great.
> > Kudos for setting a high bar, Mark!
> Huge +1 from me, too! This is great progress.
> Russell Bryant
> OpenStack-dev mailing list
> OpenStack-dev at lists.openstack.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the OpenStack-dev