Le 06/07/2015 19:22, Matt Riedemann a écrit :
Related to this change [1] which adds a new LIBERTY openstack version
to the metadata service API, it's pretty trivial but it's akin to
microversions in the nova-api v2.1 code, and we require blueprints and
specs for those changes generally.
So do we require a blueprint and optionally a spec for this type of
change, or is it simple enough as a bug fix on it's own?
[1] https://review.openstack.org/#/c/197185/
IMHO, all changes to internal interfaces (not only REST APIs, including
RPC) need a spec, in particular if the payload is changing.
We had the same discussion for the Scheduler API where a new field was
about to be added to the filter_properties dict. While it's pretty
trivial, I think we need to go over all that change to see why it's
needed and if it's backwards compatible.
My 2cts (EUR of course)
-Sylvain
__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: [email protected]?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
