On Fri, Jan 30, 2015 at 2:17 AM, Alan Pevec ape...@gmail.com wrote:
2015-01-29 19:31 GMT+01:00 Joe Gordon joe.gord...@gmail.com:
That means clients need overlapping dependencies with the stable
branches.
I don't think this is a reasonable requirement, and am not sure what we
gain from it.
2015-01-29 19:31 GMT+01:00 Joe Gordon joe.gord...@gmail.com:
That means clients need overlapping dependencies with the stable branches.
I don't think this is a reasonable requirement, and am not sure what we gain
from it.
Capping all Oslo and clients on stable/juno was reverted[1] due to
Sean Dague wrote:
On 01/27/2015 05:21 PM, Sean Dague wrote:
On 01/27/2015 03:55 PM, Douglas Mendizabal wrote:
Hi openstack-dev,
The barbican team would like to announce the release of
python-barbicanclient 3.0.2. This is a minor release that fixes a bug
in the pbr versioning that was
Good question! I was planning a keystone liens release very soon, but will
hold off of it will break everything.
--Morgan
On Thursday, January 29, 2015, Thierry Carrez thie...@openstack.org wrote:
Sean Dague wrote:
On 01/27/2015 05:21 PM, Sean Dague wrote:
On 01/27/2015 03:55 PM, Douglas
Maybe we should defer all client releases until we know for sure if each of
them are ticking timebombs.
On Thu, Jan 29, 2015 at 11:00 AM, Morgan Fainberg morgan.fainb...@gmail.com
wrote:
Good question! I was planning a keystone liens release very soon, but will
hold off of it will break
On Thu, Jan 29, 2015 at 9:52 AM, Sean Dague s...@dague.net wrote:
So, honestly, yes.
For a library to release safely it must:
* have stable-compat jobs running (this was the issue with barbican client)
* if it has a stable/juno branch it must be pinned in stable/juno (this
was the issue on
So, honestly, yes.
For a library to release safely it must:
* have stable-compat jobs running (this was the issue with barbican client)
* if it has a stable/juno branch it must be pinned in stable/juno (this
was the issue on most of the oslo libs)
-Sean
On 01/29/2015 12:07 PM, Kyle
On 2015-01-29 09:00:42 -0800 (-0800), Morgan Fainberg wrote:
Good question! I was planning a keystone liens release very soon,
but will hold off of it will break everything.
I believe part of the problem is that python-barbicanclient doesn't
yet have backward-compatibility jobs running on its
On Thu, Jan 29, 2015, at 01:31 PM, Joe Gordon wrote:
On Thu, Jan 29, 2015 at 9:52 AM, Sean Dague s...@dague.net wrote:
So, honestly, yes.
For a library to release safely it must:
* have stable-compat jobs running (this was the issue with barbican client)
* if it has a stable/juno
On Jan 29, 2015, at 1:19 PM, Doug Hellmann d...@doughellmann.com wrote:
On Thu, Jan 29, 2015, at 01:31 PM, Joe Gordon wrote:
On Thu, Jan 29, 2015 at 9:52 AM, Sean Dague s...@dague.net wrote:
So, honestly, yes.
For a library to release safely it must:
* have stable-compat jobs
On Thu, Jan 29, 2015 at 2:22 PM, Douglas Mendizabal
douglas.mendiza...@rackspace.com wrote:
On Jan 29, 2015, at 1:19 PM, Doug Hellmann d...@doughellmann.com wrote:
On Thu, Jan 29, 2015, at 01:31 PM, Joe Gordon wrote:
On Thu, Jan 29, 2015 at 9:52 AM, Sean Dague s...@dague.net wrote:
So,
On 2015-01-28 02:42:28 + (+), Douglas Mendizabal wrote:
Thanks for the heads up, and for adding the stable-compat-jobs to
the client. [1] This is an interesting problem, since the
proposal bot keeps the python-barbicanclient requirements in sync
with global-requirements. I’m not sure
On 01/27/2015 03:55 PM, Douglas Mendizabal wrote:
Hi openstack-dev,
The barbican team would like to announce the release of
python-barbicanclient 3.0.2. This is a minor release that fixes a bug
in the pbr versioning that was preventing the client from working correctly.
The release is
On 01/27/2015 05:21 PM, Sean Dague wrote:
On 01/27/2015 03:55 PM, Douglas Mendizabal wrote:
Hi openstack-dev,
The barbican team would like to announce the release of
python-barbicanclient 3.0.2. This is a minor release that fixes a bug
in the pbr versioning that was preventing the client
Hi openstack-dev,
The barbican team would like to announce the release of python-barbicanclient
3.0.2. This is a minor release that fixes a bug in the pbr versioning that was
preventing the client from working correctly.
The release is available on PyPI
Hi Sean,
Thanks for the heads up, and for adding the stable-compat-jobs to the client.
[1] This is an interesting problem, since the proposal bot keeps the
python-barbicanclient requirements in sync with global-requirements. I’m not
sure what the correct fix for this is?
- Doug
[1]
16 matches
Mail list logo
