On 2015-09-22 15:16:26 +1200 (+1200), Robert Collins wrote: [...] > 'Is this requirements change an API break' or 'is this requirements > change feature work' or 'is this requirements change a bugfix'. [...]
It may also be worth considering whether this logic only applies to increasing minimums (and perhaps in some very rare cases, lowering maximums). Raising or removing a maximum (cap) or lowering a minimum further means that downstream consumers are expected to still be able to continue using the same dependency versions as before the change, which means at worst a patchlevel increase in the next release. -- Jeremy Stanley __________________________________________________________________________ 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
