On 9 July 2015 at 11:43, Robert Collins <[email protected]> wrote: > On 9 July 2015 at 21:13, Thierry Carrez <[email protected]> wrote: <SNIP> >> https://review.openstack.org/#/c/199353/1/upper-constraints.txt > > So thats folk learning about what goes on. That may happen from time > to time, but since upper-constraints *isn't* a policy knob, its the > wrong place to have discussions about what should or shouldn't be in > it. <SNIP>
Are you saying that the sync' isn't a policy knob, or upper-constraints in openstack/requirements isn't a policy knob? If the later, then I suggest it very much is a policy knob. The problem is, those that are reviewing it for the separate projects are not engaged in the policy definition until it gets merged - then question it at sync' time. I think it is reasonable not to expect cores of other projects to be terribly engaged with openstack/requirements, but I suppose they need to learn to trust it. As you said later, if it is green - then the code base has presumably proved it can work with that version, so sync' it across. -- Kind Regards, Dave Walker __________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: [email protected]?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
