On 08/09/2016 02:38 AM, Tony Breeds wrote:
> 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
With constraints, the requirements minimum bump is pretty low risk. Very
little of our jobs are impacted by it.
It's in many ways more risking to leave minimums where they are and bump
constraints, because the minimums could be lying that they still work at
the lower level.
-Sean
--
Sean Dague
http://dague.net
__________________________________________________________________________
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
