Excerpts from Matthias Runge's message of 2015-06-10 12:29:45 +0200: > On 10/06/15 12:07, Robert Collins wrote: > > 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. > > My wording was not that good here. > > I know, some distro packagers are already looking at changes, but maybe > this could be improved, i.e. intensified? It was more about: giving this > more basic openstack effort a home in a project.
Given the history of lack of interest, I would want to see a significant increase in reviews from that team before giving them control of the repository. Doug __________________________________________________________________________ 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
