Re: [openstack-dev] [neutron][release] Releasing python-neutronclient 4.1.2?

2016-03-09 Thread Miguel Angel Ajo Pelayo
On Wed, Mar 9, 2016 at 4:16 PM, Doug Hellmann wrote: > Excerpts from Armando M.'s message of 2016-03-08 15:43:05 -0700: > > On 8 March 2016 at 15:07, Doug Hellmann wrote: > > > > > Excerpts from Armando M.'s message of 2016-03-08 12:49:16 -0700: > >

Re: [openstack-dev] [neutron][release] Releasing python-neutronclient 4.1.2?

2016-03-09 Thread Doug Hellmann
Excerpts from Armando M.'s message of 2016-03-08 15:43:05 -0700: > On 8 March 2016 at 15:07, Doug Hellmann wrote: > > > Excerpts from Armando M.'s message of 2016-03-08 12:49:16 -0700: > > > Hi folks, > > > > > > There's a feature or two that are pending to be delivered in

Re: [openstack-dev] [neutron][release] Releasing python-neutronclient 4.1.2?

2016-03-09 Thread Akihiro Motoki
2016-03-09 7:43 GMT+09:00 Armando M. : > > > On 8 March 2016 at 15:07, Doug Hellmann wrote: >> >> Excerpts from Armando M.'s message of 2016-03-08 12:49:16 -0700: >> > Hi folks, >> > >> > There's a feature or two that are pending to be delivered in Mitaka

Re: [openstack-dev] [neutron][release] Releasing python-neutronclient 4.1.2?

2016-03-08 Thread Armando M.
On 8 March 2016 at 15:07, Doug Hellmann wrote: > Excerpts from Armando M.'s message of 2016-03-08 12:49:16 -0700: > > Hi folks, > > > > There's a feature or two that are pending to be delivered in Mitaka > [1,2], > > and those involve changes to both the server and client

Re: [openstack-dev] [neutron][release] Releasing python-neutronclient 4.1.2?

2016-03-08 Thread Doug Hellmann
Excerpts from Armando M.'s message of 2016-03-08 12:49:16 -0700: > Hi folks, > > There's a feature or two that are pending to be delivered in Mitaka [1,2], > and those involve changes to both the server and client sides. Ideally we'd > merge both sides in time for Mitaka RC and that implies that

[openstack-dev] [neutron][release] Releasing python-neutronclient 4.1.2?

2016-03-08 Thread Armando M.
Hi folks, There's a feature or two that are pending to be delivered in Mitaka [1,2], and those involve changes to both the server and client sides. Ideally we'd merge both sides in time for Mitaka RC and that implies that we would be able to release a new version of the client including changes