Re: [openstack-dev] [Glance] [all] python-glanceclient release 0.16.1

2015-03-05 Thread Doug Hellmann


On Thu, Mar 5, 2015, at 03:15 PM, Dr. Jens Rosenboom wrote:
> Am 05/03/15 um 17:52 schrieb Doug Hellmann:
> >
> >
> > On Thu, Mar 5, 2015, at 11:37 AM, Ian Cordasco wrote:
> >> The clients in general do not back port patches. Someone should work with
> >> stable-maint to raise the cap in Icehouse and Juno. I suspect, however,
> >> that those caps were added due to the client breaking other projects.
> >> Proposals can be made though and ideally, openstack/requirements’ gate
> >> jobs will catch any breakage.
> >
> > Under my cross-project spec proposal [1], we will want to start managing
> > stable branches for clients specifically for this sort of situation.
> >
> > Doug
> >
> > [1] https://review.openstack.org/#/c/155072/
> 
> Do you expect this proposal to be applied retrospectively to create 
> stable/{icehouse,juno} branches or will this only be applied starting 
> from Kilo onwards?

Retroactively to stable branches still under support when we need to
backport something. For Kilo we should make them as part of the release
process.

> 
> Also, your proposal is talking about libraries in general, is there 
> consensus on having the python-*client projects being included there? Or 
> would it make sense to mention them explicitly?

They're libraries, so I thought they were covered, but we can mention
them explicitly if it makes a difference.

> 
> I'm a bit worried that we have a bug currently making nova and cinder 
> API services explode after some uptime and no shorttern way of fixing 
> this bug in the stable branches.

I can understand that. We need to get someone to determine where to
create the branch for the backports and then we can go ahead with
whatever changes need to be reviewed.

Doug

> 
> 
> __
> 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


Re: [openstack-dev] [Glance] [all] python-glanceclient release 0.16.1

2015-03-05 Thread Monty Taylor
On 03/05/2015 12:02 AM, Nikhil Komawar wrote:
> The python-glanceclient release management team is pleased to announce:
> python-glanceclient version 0.16.1 has been released on Thursday, Mar 5th 
> around 04:56 UTC.
> 
> For more information, please find the details at:
> 
> 
> https://launchpad.net/python-glanceclient/+milestone/v0.16.1
> 
> Please report the issues through launchpad:
> 
> https://bugs.launchpad.net/python-glanceclient

Thank you! This includes a fix for my favorite glanceclient bug.


__
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


Re: [openstack-dev] [Glance] [all] python-glanceclient release 0.16.1

2015-03-05 Thread Dr. Jens Rosenboom

Am 05/03/15 um 17:52 schrieb Doug Hellmann:



On Thu, Mar 5, 2015, at 11:37 AM, Ian Cordasco wrote:

The clients in general do not back port patches. Someone should work with
stable-maint to raise the cap in Icehouse and Juno. I suspect, however,
that those caps were added due to the client breaking other projects.
Proposals can be made though and ideally, openstack/requirements’ gate
jobs will catch any breakage.


Under my cross-project spec proposal [1], we will want to start managing
stable branches for clients specifically for this sort of situation.

Doug

[1] https://review.openstack.org/#/c/155072/


Do you expect this proposal to be applied retrospectively to create 
stable/{icehouse,juno} branches or will this only be applied starting 
from Kilo onwards?


Also, your proposal is talking about libraries in general, is there 
consensus on having the python-*client projects being included there? Or 
would it make sense to mention them explicitly?


I'm a bit worried that we have a bug currently making nova and cinder 
API services explode after some uptime and no shorttern way of fixing 
this bug in the stable branches.



__
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


Re: [openstack-dev] [Glance] [all] python-glanceclient release 0.16.1

2015-03-05 Thread Doug Hellmann


On Thu, Mar 5, 2015, at 11:37 AM, Ian Cordasco wrote:
> The clients in general do not back port patches. Someone should work with
> stable-maint to raise the cap in Icehouse and Juno. I suspect, however,
> that those caps were added due to the client breaking other projects.
> Proposals can be made though and ideally, openstack/requirements’ gate
> jobs will catch any breakage.

Under my cross-project spec proposal [1], we will want to start managing
stable branches for clients specifically for this sort of situation.

Doug

[1] https://review.openstack.org/#/c/155072/

> 
> On 3/5/15, 10:28, "Dr. Jens Rosenboom"  wrote:
> 
> >Am 05/03/15 um 06:02 schrieb Nikhil Komawar:
> >> The python-glanceclient release management team is pleased to announce:
> >>  python-glanceclient version 0.16.1 has been released on Thursday,
> >>Mar 5th around 04:56 UTC.
> >
> >The release includes a bugfix for [1], which is affecting us in
> >Icehouse, most likely Juno is also affected. However, due to the
> >requirements caps recently introduced, the bugfix will not be picked up
> >by the stable branches (caps are <=0.14.2 for Icehouse and <=0.15.0 for
> >Juno).
> >
> >The patch itself [2] applies cleanly to the older code, so in theory it
> >should be possible to build some 0.14.3 release with that and update the
> >stable requirements accordingly. But I guess that this would require
> >setting up stable branches for the client git repo, which currently
> >don't exist.
> >
> >Are there plans to do this or is there some other way to backport the
> >fix? I assume that the same issue may happen with other client releases
> >in the future.
> >
> >[1] https://bugs.launchpad.net/python-glanceclient/+bug/1423165
> >[2] https://review.openstack.org/156975
> >
> >
> >__
> >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

__
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


Re: [openstack-dev] [Glance] [all] python-glanceclient release 0.16.1

2015-03-05 Thread Ian Cordasco
The clients in general do not back port patches. Someone should work with
stable-maint to raise the cap in Icehouse and Juno. I suspect, however,
that those caps were added due to the client breaking other projects.
Proposals can be made though and ideally, openstack/requirements’ gate
jobs will catch any breakage.

On 3/5/15, 10:28, "Dr. Jens Rosenboom"  wrote:

>Am 05/03/15 um 06:02 schrieb Nikhil Komawar:
>> The python-glanceclient release management team is pleased to announce:
>>  python-glanceclient version 0.16.1 has been released on Thursday,
>>Mar 5th around 04:56 UTC.
>
>The release includes a bugfix for [1], which is affecting us in
>Icehouse, most likely Juno is also affected. However, due to the
>requirements caps recently introduced, the bugfix will not be picked up
>by the stable branches (caps are <=0.14.2 for Icehouse and <=0.15.0 for
>Juno).
>
>The patch itself [2] applies cleanly to the older code, so in theory it
>should be possible to build some 0.14.3 release with that and update the
>stable requirements accordingly. But I guess that this would require
>setting up stable branches for the client git repo, which currently
>don't exist.
>
>Are there plans to do this or is there some other way to backport the
>fix? I assume that the same issue may happen with other client releases
>in the future.
>
>[1] https://bugs.launchpad.net/python-glanceclient/+bug/1423165
>[2] https://review.openstack.org/156975
>
>
>__
>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


Re: [openstack-dev] [Glance] [all] python-glanceclient release 0.16.1

2015-03-05 Thread Dr. Jens Rosenboom

Am 05/03/15 um 06:02 schrieb Nikhil Komawar:

The python-glanceclient release management team is pleased to announce:
 python-glanceclient version 0.16.1 has been released on Thursday, Mar 5th 
around 04:56 UTC.


The release includes a bugfix for [1], which is affecting us in 
Icehouse, most likely Juno is also affected. However, due to the 
requirements caps recently introduced, the bugfix will not be picked up 
by the stable branches (caps are <=0.14.2 for Icehouse and <=0.15.0 for 
Juno).


The patch itself [2] applies cleanly to the older code, so in theory it 
should be possible to build some 0.14.3 release with that and update the 
stable requirements accordingly. But I guess that this would require 
setting up stable branches for the client git repo, which currently 
don't exist.


Are there plans to do this or is there some other way to backport the 
fix? I assume that the same issue may happen with other client releases 
in the future.


[1] https://bugs.launchpad.net/python-glanceclient/+bug/1423165
[2] https://review.openstack.org/156975


__
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