On 10 June 2015 at 20:12, Matthias Runge <mru...@redhat.com> wrote: > Since our software is to be consumed by packages, shouldn't the packages > project consider itself to be responsible for global requirements? I.e. > checking, if requirements are packageable, if versions fit, etc.
I think we welcome input from distribution maintainers on global-requirements; especially for new packages. But, the responsibility is ultimately a team effort: all the components of openstack have to meet the operator/distributor co-installability requirement. If one project has a minimum version of X, its not possible for other projects to have a max version of < X otherwise we're not coinstallable. This works both ways of course. > In some distros, there are multiple versions of the same package allowed, in > others, it's forbidden. Thats true, but its also a per-distro thing. Within a distro you need to be consistent. There's no need for RHEL to match RDO for instance, and trying to make that happen across a dozen redistributors in the OpenStack context makes no sense at all. We're moving to making our ranges as wide as we can to make life easier for anyone that wants to pick slightly different versions: we can't assert that it will work, but unless we know it doesnt', we won't preclude you trying :) -Rob -- Robert Collins <rbtcoll...@hp.com> Distinguished Technologist HP Converged Cloud __________________________________________________________________________ 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
