This is just a friendly reminder that without a release from master, if your project still caps a requirement then it may be either holding back a package or not be included in upper-constraints updates.
http://logs.openstack.org/76/466476/5/check/gate-requirements-tox-py27-check-uc-ubuntu-xenial/d71b8f6/console.html#_2017-05-22_09_38_53_142301 http://logs.openstack.org/76/466476/4/check/gate-requirements-tox-py27-check-uc-ubuntu-xenial/27cb570/console.html#_2017-05-21_09_00_14_624413 The following packages are taken from those lists and holding back requirements updates. Holding back updates from upstream to be consumed by other openstack projects: mistral - holding back sqlalchemy (no release that uncaps sqlalchemy) django-openstack-auth - holding back django Being held back from being updated and being consumed, all these is because they don't have a release that uncaps pbr. mistral os-apply-config os-collect-config os-refresh-config os-vif If these projects could make a release (something fetchable by pypi) off of master that's all that's needed. They all have updated their requirements in master, just no consumable release. -- Matthew Thode (prometheanfire)
signature.asc
Description: OpenPGP digital signature
__________________________________________________________________________ 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
