<div dir="ltr">Maybe we should defer all client releases until we know for sure if each of them are ticking timebombs.<br></div><div class="gmail_extra"><br><div class="gmail_quote">On Thu, Jan 29, 2015 at 11:00 AM, Morgan Fainberg <span dir="ltr"><<a href="mailto:morgan.fainberg@gmail.com" target="_blank">morgan.fainberg@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Good question! I was planning a keystone liens release very soon, but will hold off of it will break everything. <span class="HOEnZb"><font color="#888888"><div><br></div></font></span><div><span class="HOEnZb"><font color="#888888">--Morgan</font></span><div><div class="h5"><br><br>On Thursday, January 29, 2015, Thierry Carrez <<a href="mailto:thierry@openstack.org" target="_blank">thierry@openstack.org</a>> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Sean Dague wrote:<br>
> On 01/27/2015 05:21 PM, Sean Dague wrote:<br>
>> On 01/27/2015 03:55 PM, Douglas Mendizabal wrote:<br>
>>> Hi openstack-dev,<br>
>>><br>
>>> The barbican team would like to announce the release of<br>
>>> python-barbicanclient 3.0.2.  This is a minor release that fixes a bug<br>
>>> in the pbr versioning that was preventing the client from working correctly.<br>
>>><br>
>>> The release is available on PyPI<br>
>>><br>
>>> <a href="https://pypi.python.org/pypi/python-barbicanclient/3.0.2" target="_blank">https://pypi.python.org/pypi/python-barbicanclient/3.0.2</a><br>
>><br>
>> Which just broke everything, because it creates incompatible<br>
>> requirements in stable/juno with cinder. :(<br>
><br>
> Here is the footnote -<br>
> <a href="http://logs.openstack.org/18/150618/1/check/check-grenade-dsvm/c727602/logs/grenade.sh.txt.gz#_2015-01-28_00_04_54_429" target="_blank">http://logs.openstack.org/18/150618/1/check/check-grenade-dsvm/c727602/logs/grenade.sh.txt.gz#_2015-01-28_00_04_54_429</a><br>
<br>
This seems to have been caused by this requirements sync:<br>
<br>
<a href="http://git.openstack.org/cgit/openstack/python-barbicanclient/commit/requirements.txt?id=054d81fb63053c3ce5f1c87736f832750f6311b3" target="_blank">http://git.openstack.org/cgit/openstack/python-barbicanclient/commit/requirements.txt?id=054d81fb63053c3ce5f1c87736f832750f6311b3</a><br>
<br>
but then the same requirements sync happened in all other clients:<br>
<br>
<a href="http://git.openstack.org/cgit/openstack/python-novaclient/commit/requirements.txt?id=17367002609f011710014aef12a898e9f16db81c" target="_blank">http://git.openstack.org/cgit/openstack/python-novaclient/commit/requirements.txt?id=17367002609f011710014aef12a898e9f16db81c</a><br>
<br>
Does that mean that all the clients are time bombs that will break<br>
stable/juno when their next release is tagged ?<br>
<br>
--<br>
Thierry Carrez (ttx)<br>
<br>
</blockquote></div></div></div>
<br>__________________________________________________________________________<br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
<br></blockquote></div><br></div>