[openstack-dev] [oslo][horizon][infra] oslo.policy in django-openstack-auth fails with stable/juno global requirement check
amotoki at gmail.com
Mon Mar 16 02:53:07 UTC 2015
It is a good direction to have the stable branches for all libraries.
It seems better that I wait for adopting oslo.policy in django-openstack-auth.
In the current infra, a library specified in LIBS_FROM_GIT will be installed
even if its version does not match global-requirement (for example,
even if global-requirement requires <=1.1.9, dev version of library which
is newer than 1.1.9 will be installed and leads to global-requirement failure.
It seems the version check is not so easy and seems better to wait
stable/xxxx branches are created
2015-03-16 1:45 GMT+09:00 Doug Hellmann <doug at doughellmann.com>:
> Excerpts from Akihiro Motoki's message of 2015-03-16 01:25:08 +0900:
>> Hi Oslo team,
>> I am working on adopting the graduated oslo.policy in django-openstack-auth 
>> but I have a question on how to migrate openstack.common.policy to oslo.policy
>> in libraries which have no stable branch.
>> django-openstack-auth has no stable branches as other python-*client.
>> stable/juno global-requirements requries
>> and the development is for 1.1.10 or 1.2.x,
>> so I first thought it is no problem.
>> However, in the review of ,
>> fails with the error that oslo.policy is not in global-requirements in
>> Is it a problem in the infra side? Or is it a thing we should avoid?
>> Any advise will be appreciated.
> All libraries should have stable branches going forward because we
> are capping requirements in the stable branches. See
> https://review.openstack.org/#/c/155072/ for details.
>>  https://review.openstack.org/#/c/164420/
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
Akihiro Motoki <amotoki at gmail.com>
More information about the OpenStack-dev