On Thu, Jan 29, 2015 at 9:52 AM, Sean Dague <[email protected]> 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 most of the oslo libs) >
We use the clients for two very different things. 1. As a python library to communicate between services 2. A command line tool that can talk to all supported versions of our APIs (stable/icehouse, stable/juno and master). With our current testing setup, we try using the latest release on stable branches for both 1. and 2. 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. Instead I propose we pin the client version for 1 and use the latest release for 2. We should be able to do this easily by putting all command line tools inside of venvs using pipsi[0]. This way we continue to test the clients API compatibility with stable branches without requiring dependency compatibility (I roped Dean Troyer into working on this at the nova mid cycle). Once this is done, we should be able to go ahead and pin all explicit dependencies on stable branches [1]. [0] https://pypi.python.org/pypi/pipsi/0.8 [1] https://review.openstack.org/#/c/147451/ > > -Sean > > On 01/29/2015 12:07 PM, Kyle Mestery wrote: > > 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 > > <[email protected] <mailto:[email protected]>> wrote: > > > > 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 <[email protected] > > <mailto:[email protected]>> wrote: > > > > 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 preventing the client from > > working correctly. > > >>> > > >>> The release is available on PyPI > > >>> > > >>> https://pypi.python.org/pypi/python-barbicanclient/3.0.2 > > >> > > >> Which just broke everything, because it creates incompatible > > >> requirements in stable/juno with cinder. :( > > > > > > Here is the footnote - > > > > > > http://logs.openstack.org/18/150618/1/check/check-grenade-dsvm/c727602/logs/grenade.sh.txt.gz#_2015-01-28_00_04_54_429 > > > > This seems to have been caused by this requirements sync: > > > > > http://git.openstack.org/cgit/openstack/python-barbicanclient/commit/requirements.txt?id=054d81fb63053c3ce5f1c87736f832750f6311b3 > > > > but then the same requirements sync happened in all other > clients: > > > > > http://git.openstack.org/cgit/openstack/python-novaclient/commit/requirements.txt?id=17367002609f011710014aef12a898e9f16db81c > > > > Does that mean that all the clients are time bombs that will > break > > stable/juno when their next release is tagged ? > > > > -- > > Thierry Carrez (ttx) > > > > > > > __________________________________________________________________________ > > OpenStack Development Mailing List (not for usage questions) > > Unsubscribe: > > [email protected]?subject:unsubscribe > > < > http://[email protected]?subject:unsubscribe> > > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > > > > > > > > > > > __________________________________________________________________________ > > OpenStack Development Mailing List (not for usage questions) > > Unsubscribe: > [email protected]?subject:unsubscribe > > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > > > > > -- > Sean Dague > http://dague.net > > > __________________________________________________________________________ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: [email protected]?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > >
__________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: [email protected]?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
