Excerpts from Tony Breeds's message of 2016-08-09 16:38:35 +1000: > Hi all, > I guess this is aimed at the long term requirements team members. > > The current policy for approving requirements[1] bumps contains the following > text: > > Changes to update the minimum version of a library developed by the > OpenStack community can be approved by one reviewer, as long as the > constraints are correct and the tests pass. > > Perhaps I'm a little risk adverse but this seems a little strange to me. Can > folks that know more about how this came about help me understand why that is? > > Yours Tony. > > [1] > https://github.com/openstack/requirements/blob/master/README.rst#for-upgrading-requirements-versions
It's limited to libraries we maintain, so that lowers the risk some. But as Sean pointed out, it's riskier to assume the older releases continue to work because typically a request to raise a minimum version means an app wants to depend on a feature that appears in the newer version. Doug __________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: [email protected]?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
