Robert Collins wrote: > We've finally gotten all the kinks worked out and now > upper-constraints proposals should be coming in daily. > > *** These are timely and important: without them, no new releases of > *anything* are consumed. *** > > https://review.openstack.org/#/c/199353/ is an example. > > They are all in the topic > https://review.openstack.org/#/q/status:open+topic:openstack/requirements/constraints,n,z > > (there is only ever one at a time at the moment, proposed to our > master requirements repo). After liberty branches there may be > multiple ones open - one per release of OpenStack that uses > constraints files. > > I'm putting all this into the documentation too, of course.
I'm wondering if we should not refresh them less often. Some of those will trigger some discussion before approval, and having them constantly wiped out by new patchsets that add one or two extra bumps is, IMHO, counter-productive... How about we generate those once per week, before Monday starts ? Then we can process them during the week and end up discussing the same thing, rather than a moving target. (We have other things that are refreshed regularly and it's always a race to gather enough approvals before they are regenerated -- I fail to see the benefit of daily refresh vs. weekly refresh here) -- Thierry Carrez (ttx) __________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: [email protected]?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
