On Thu, Dec 8, 2016 at 3:48 PM, Matt Riedemann <[email protected]> wrote:
> On 12/8/2016 1:03 PM, Ian Cordasco wrote: > >> >> >> If your project were using constraints, you would not run into this >> problem. >> > > I'd like to stress this point. This was the solution for getting glance > patches to land in stable/liberty today: > > https://review.openstack.org/#/q/status:merged+project:opens > tack/glance+branch:stable/liberty+topic:liberty-constraints > > So that we can end of life the stable/liberty branch for Glance. > > Dealing with blacklisting patches is a whack-a-mole approach to deal with > the lack of upper-constraints usage in a repo, so the first solution should > be to get upper-constraints used in the stable branches on projects (or > master for that matter). Exactly. Deploying from a source stable branch should be viable - as it stands, it is not. One of the tenets of a stable branch must be repeatable from-source builds. Right now I have "effective pins" in my mitaka Ansible playbooks for kombu and keystonemiddleware. This latest kombu kerfuffle broke stable/mitaka glance, neutron and nova for me. Keystone broke a few days ago. Is there an existing effort or blueprint or whatever being worked on for pinning (or at a minimum setting upper bounds on) dependencies in stable branches? If so, I would like to follow and/or participate. > > -- > > Thanks, > > Matt Riedemann > > > > __________________________________________________________________________ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: [email protected]?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev >
__________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: [email protected]?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
