[openstack-dev] [all] Kilo stable branches for "other" libraries

Hi everyone, As you may know, in an effort to simplify stable branch maintenance and increase their resilience to random changes, the following policy was adopted: http://specs.openstack.org/openstack/openstack-specs/specs/library-stable-branches.html TL;DR is that in the future, stable branches

Re: [openstack-dev] [all] Kilo stable branches for "other" libraries

On 08/04/15 15:55, Thierry Carrez wrote: I'm especially worried with python-cinderclient, python-designateclient and django_openstack_auth which are more than 2 months old and may well contemplate another kilo release that could be disrupting at this point. In general: a great idea, and I've be

Re: [openstack-dev] [all] Kilo stable branches for "other" libraries

Thierry, You left out python-ironicclient, which isn't a surprise as it isn't actually listed in Nova's requirements.txt file. I don't have a link handy to cite the previous discussions, but Nova felt that it was not appropriate to list a driver's dependency in their project's requirements file.

Re: [openstack-dev] [all] Kilo stable branches for "other" libraries

On Wed, Apr 8, 2015 at 8:55 AM, Thierry Carrez wrote: > The question is, how should we proceed there ? This is new procedure, so > I'm a bit unclear on the best way forward and would like to pick our > collective brain. Should we just push requirements cap for all OpenStack > libs and create stab

Re: [openstack-dev] [all] Kilo stable branches for "other" libraries

On 04/08/2015 10:42 AM, Dean Troyer wrote: > On Wed, Apr 8, 2015 at 8:55 AM, Thierry Carrez > wrote: > > The question is, how should we proceed there ? This is new procedure, so > I'm a bit unclear on the best way forward and would like to pick our > coll

Re: [openstack-dev] [all] Kilo stable branches for "other" libraries

Doug Hellmann wrote: > Excerpts from Dean Troyer's message of 2015-04-08 09:42:31 -0500: >> On Wed, Apr 8, 2015 at 8:55 AM, Thierry Carrez >> wrote: >> >>> The question is, how should we proceed there ? This is new procedure, so >>> I'm a bit unclear on the best way forward and would like to pick

Re: [openstack-dev] [all] Kilo stable branches for "other" libraries

Excerpts from Sean Dague's message of 2015-04-08 10:49:15 -0400: > On 04/08/2015 10:42 AM, Dean Troyer wrote: > > On Wed, Apr 8, 2015 at 8:55 AM, Thierry Carrez > > wrote: > > > > The question is, how should we proceed there ? This is new procedure, so > > I'

Re: [openstack-dev] [all] Kilo stable branches for "other" libraries

Excerpts from Devananda van der Veen's message of 2015-04-08 14:37:26 +: > Thierry, > > You left out python-ironicclient, which isn't a surprise as it isn't > actually listed in Nova's requirements.txt file. I don't have a link handy > to cite the previous discussions, but Nova felt that it wa

Re: [openstack-dev] [all] Kilo stable branches for "other" libraries

Excerpts from Dean Troyer's message of 2015-04-08 09:42:31 -0500: > On Wed, Apr 8, 2015 at 8:55 AM, Thierry Carrez > wrote: > > > The question is, how should we proceed there ? This is new procedure, so > > I'm a bit unclear on the best way forward and would like to pick our > > collective brain.

Re: [openstack-dev] [all] Kilo stable branches for "other" libraries

Keystonemiddleware is pending a minor fix to sync g-r in a sane way to match the rest of kilo (what we have for keystone et al). However we are blocked because there is no stable Juno and icehouse branches. I'd like to release the Python-keystone client with the requirements update for kilo. So k

Re: [openstack-dev] [all] Kilo stable branches for "other" libraries

The Barbican Team also has a plan to release a new version of barbican client for Kilo. The planned version is 3.1.0. [1] and it will include features landed during FFE. Thanks, -Douglas Mendizabal [1] https://launchpad.net/python-barbicanclient/+milestone/3.1.0

Re: [openstack-dev] [all] Kilo stable branches for "other" libraries

Neutron team has a plan to release a new version of neutornclient for Kilo. We waited the new release until all granted FFE patches land, and now we are almost ready to go. (waiting one patch in the gate) The planned new version is 2.4.0. It is because neutronclient uses 2.3.x version for a long t

Re: [openstack-dev] [all] Kilo stable branches for "other" libraries

I am also looking at a python-keystoneclient release still pending as well. This is being added to the ML topic based on the IRC conversation we just had. On Thu, Apr 9, 2015 at 8:20 AM, Morgan Fainberg wrote: > Keystonemiddleware is pending a minor fix to sync g-r in a sane way to > match the r

Re: [openstack-dev] [all] Kilo stable branches for "other" libraries

On Thu, Apr 9, 2015 at 11:23 AM, Akihiro Motoki wrote: > Neutron team has a plan to release a new version of neutornclient for Kilo. > We waited the new release until all granted FFE patches land, > and now we are almost ready to go. (waiting one patch in the gate) > > The planned new version is