On 08/09/2016 08:54 PM, Hayes, Graham wrote: > But then packagers are going to have to do the work anyway, as it will > have in effect raised the minimum version of routes for Glance, and thus > need a new package.
Which isn't a problem. It's perfectly ok to upload a new upstream release of a package, because only a single component of OpenStack needs that new version. In fact, this happened many times in the past already. > It might not make a difference to deployers / packagers who only deploy > one project from OpenStack, but they are in the minority - having a > known good minimum for requirements helps deployers who have multiple > services to deploy. The thing is, currently, it's one single concept, which is the issue. The global-requirements.txt should be expressing whatever is the lowest possible on the full scope of OpenStack (which it currently does). But I don't agree that every project needs to be dumb and increase lower bounds when they in fact don't need to do so. IMO they should follow what Swift does: test lower bounds. Currently John does this manually. In an ideal world, every project would be individually tested for it, automatically. Cheers, Thomas Goirand (zigo) __________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
