Thanks for quick reply.
Let's restore the context. I develop plugin for Fuel that uses
Networking-vSphere as the network driver. Next release of Fuel, 9.1 and
maybe 9.X will based on mitaka.
For me it means that I have to have a place for commit my changes to
driver. Now I'm working on changing of devstack/plugin.sh to make possible
to install either OVSvApp or VMware DVS driver. But my ambitions are spread
much further.
I have several ideas how to improve vmware dvs and my question is can I
full-fledged develop it or not?
On Thu, Jul 14, 2016 at 3:21 PM, Jay Pipes <jaypi...@gmail.com> wrote:
> On 07/14/2016 02:41 AM, Igor Gajsin wrote:
>
>> Hi all.
>>
>> I'm going to add some improvement to Networking-vSphere. There is the
>> problem because I'm working with mitaka which already released. But I
>> see some commits in the stable/mitaka branch that were made after
>> release date.
>>
>> Does it mean, that I can commit new functionality to stable/mitaka
>> branch and work with it as usual?
>>
>
> Hello Igor!
>
> Generally, no patches should land in a stable branch that provide a new
> feature or change existing behaviour. Only bug fixes should be applied to a
> stable branch. Can you point to specific patches that you are referring to?
>
> Thanks!
> -jay
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
