[openstack-dev] [neutron] Status of Neutron at Juno-3

Mark McClain mark at mcclain.xyz
Wed Sep 3 15:19:03 UTC 2014


On Sep 3, 2014, at 11:04 AM, Brian Haley <brian.haley at hp.com> wrote:

> On 09/03/2014 08:17 AM, Kyle Mestery wrote:
>> Given how deep the merge queue is (146 currently), we've effectively
>> reached feature freeze in Neutron now (likely other projects as well).
>> So this morning I'm going to go through and remove BPs from Juno which
>> did not make the merge window. I'll also be putting temporary -2s in
>> the patches to ensure they don't slip in as well. I'm looking at FFEs
>> for the high priority items which are close but didn't quite make it:
>> 
>> https://blueprints.launchpad.net/neutron/+spec/l3-high-availability
>> https://blueprints.launchpad.net/neutron/+spec/add-ipset-to-security
>> https://blueprints.launchpad.net/neutron/+spec/security-group-rules-for-devices-rpc-call-refactor
> 
> I guess I'll be the first to ask for an exception for a Medium since the code
> was originally completed in Icehouse:
> 
> https://blueprints.launchpad.net/neutron/+spec/l3-metering-mgnt-ext
> 
> The neutronclient-side code was committed in January, and the neutron side,
> https://review.openstack.org/#/c/70090 has had mostly positive reviews since
> then.  I've really just spent the last week re-basing it as things moved along.
> 

+1 for FFE.  I think this is good community that fell through the cracks.

mark  




More information about the OpenStack-dev mailing list