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 dependencies. > 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)
signature.asc
Description: OpenPGP digital signature
__________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: [email protected]?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
