[openstack-dev] [neutron] BPs for Juno-1

Edgar Magana Perdomo (eperdomo) eperdomo at cisco.com
Wed May 28 17:21:38 UTC 2014


Nader,

My understanding is that you DO need a BP for those changes as well due to the fact that neutron-client is a separate project but it should be easier to merge because the main one in Neutron has been already approved.

Edgar

From: Nader Lahouti <nader.lahouti at gmail.com<mailto:nader.lahouti at gmail.com>>
Reply-To: "OpenStack Development Mailing List (not for usage questions)" <openstack-dev at lists.openstack.org<mailto:openstack-dev at lists.openstack.org>>
Date: Tuesday, May 27, 2014 at 3:56 PM
To: "OpenStack Development Mailing List (not for usage questions)" <openstack-dev at lists.openstack.org<mailto:openstack-dev at lists.openstack.org>>
Subject: Re: [openstack-dev] [neutron] BPs for Juno-1

Thanks Kyle.

One more question: I have a BP for changes in python-neutronclient. Do I need to have add a neutron-spec for that?

Thanks,
Nader.




On Tue, May 27, 2014 at 10:08 AM, Kyle Mestery <mestery at noironetworks.com<mailto:mestery at noironetworks.com>> wrote:
On Tue, May 27, 2014 at 12:01 PM, Nader Lahouti <nader.lahouti at gmail.com<mailto:nader.lahouti at gmail.com>> wrote:
> Hi Kyle,
>
>>>> ... But I just wanted to highlight
>
>>>> that I removed a large number of BPs from targeting Juno-1 now which
>>>> did not have specifications linked to them...
>
> Will those BP be reviewed after updating the link to the specification?
>
The BPs will be reviewed per normal, but Juno-1 is 2 weeks out now, so
realistically given review cycles, it's unlikely additional things
(unless small) will land in Juno-1.

Thanks,
Kyle

>
> Thanks,
> Nader.
>
>
>
>
>
> On Tue, May 27, 2014 at 7:14 AM, Kyle Mestery <mestery at noironetworks.com<mailto:mestery at noironetworks.com>>
> wrote:
>>
>> Hi Neutron developers:
>>
>> I've spent some time cleaning up the BPs for Juno-1, and they are
>> documented at the link below [1]. There are a large number of BPs
>> currently under review right now in neutron-specs. If we land some of
>> those specs this week, it's possible some of these could make it into
>> Juno-1, pending review cycles and such. But I just wanted to highlight
>> that I removed a large number of BPs from targeting Juno-1 now which
>> did not have specifications linked to them nor specifications which
>> were actively under review in neutron-specs.
>>
>> Also, a gentle reminder that the process for submitting specifications
>> to Neutron is documented here [2].
>>
>> Thanks, and please reach out to me if you have any questions!
>>
>> Kyle
>>
>> [1] https://launchpad.net/neutron/+milestone/juno-1
>> [2] https://wiki.openstack.org/wiki/Blueprints#Neutron
>>
>> _______________________________________________
>> OpenStack-dev mailing list
>> OpenStack-dev at lists.openstack.org<mailto:OpenStack-dev at lists.openstack.org>
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
>
> _______________________________________________
> OpenStack-dev mailing list
> OpenStack-dev at lists.openstack.org<mailto:OpenStack-dev at lists.openstack.org>
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>

_______________________________________________
OpenStack-dev mailing list
OpenStack-dev at lists.openstack.org<mailto:OpenStack-dev at lists.openstack.org>
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20140528/872437e4/attachment-0001.html>


More information about the OpenStack-dev mailing list