David Lyle wrote: > So we have a couple of options. First, leave django_openstack_auth at > 1.1.9 and let deployers and distros rationalize which version of Django > they want to use and negotiate the dependency issues independently. Or > second, release a new version of django_openstack_auth and determine if > we want to fix the version django_openstack_auth in > global-requirements.txt or leave the upper cap unbound.
I pinged packagers to get their feel on the issue. It's sad that we have to do this at this point, but I feel like bumping to 1.2.0 with the correct cap is the right solution 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
