[openstack-dev] [requirements][mistral][tripleo][horizon][nova][releases] release models for projects tracked in global-requirements.txt

Thierry Carrez thierry at openstack.org
Wed May 31 08:06:56 UTC 2017

Matthew Thode wrote:
> We have a problem in requirements that projects that don't have the
> cycle-with-intermediary release model (most of the cycle-with-milestones
> model) don't get integrated with requirements until the cycle is fully
> done.  This causes a few problems.
> [...]

Makes sense. Rules that apply for libraries should apply to other strong

> This has hit us with the mistral and tripleo projects particularly
> (tagged in the title).  They disallow pbr-3.0.0 and in the case of
> mistral sqlalchemy updates.
> [mistral]
> mistral - blocking sqlalchemy - milestones

I wonder why mistral is in requirements. Looks like tripleo-common is
depending on it ? Could someone shine some light on this ? It might just
mean mistral-lib is missing a few functions, and switching the release
model of mistral itself might be overkill ?

Thierry Carrez (ttx)

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: OpenPGP digital signature
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20170531/210f17e7/attachment.sig>

More information about the OpenStack-dev mailing list