Greetings OpenStack community, Well, today's meeting was very brief. For the longest time, edleafe had the room to himself, and breezed through the prepared topics, until stevelle showed up. We had a good discussion about the stability guidelines and some of the issues in resolving the two different viewpoints. What came out of our discussion was the realization that these viewpoints weren't simply a matter of degree of strictness, but rather two different things: APIs that are stable to "robust" clients, and APIs that support cloud interoperability. So maybe the reason we have been having a hard time reaching agreement or compromise is that the two concepts are not congruent. edleafe agreed to try to write a blog post about this, so check out his blog [4] in the next day or so in case he actually does what he says he'll do.
# Newly Published Guidelines Nothing new this week. # API Guidelines Proposed for Freeze Guidelines that are ready for wider review by the whole community. None this week, although the pagination guideline below is close. # Guidelines Currently Under Review [3] * Define pagination guidelines https://review.openstack.org/#/c/446716/ * Create a new set of api stability guidelines https://review.openstack.org/#/c/421846/ * Microversions: add next_min_version field in version body https://review.openstack.org/#/c/446138/ * Mention max length limit information for tags https://review.openstack.org/#/c/447344/ * Add API capabilities discovery guideline https://review.openstack.org/#/c/386555/ * Recommend the correct HTTP method for tags https://review.openstack.org/451536 * Clarify the meaning of BODY (trivial fix) https://review.openstack.org/451568 * WIP: microversion architecture archival doc (very early; not yet ready for review) https://review.openstack.org/444892 # Highlighting your API impacting issues If you seek further review and insight from the API WG, please address your concerns in an email to the OpenStack developer mailing list[1] with the tag "[api]" in the subject. In your email, you should include any relevant reviews, links, and comments to help guide the discussion of the specific challenge you are facing. To learn more about the API WG mission and the work we do, see OpenStack API Working Group [2]. Thanks for reading and see you next week! # References [1] http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev [2] http://specs.openstack.org/openstack/api-wg/ [3] https://review.openstack.org/#/q/status:open+project:openstack/api-wg,n,z [4] https://blog.leafe.com Meeting Agenda https://wiki.openstack.org/wiki/Meetings/API-WG#Agenda Past Meeting Records http://eavesdrop.openstack.org/meetings/api_wg/ Open Bugs https://bugs.launchpad.net/openstack-api-wg -- Ed Leafe
signature.asc
Description: Message signed with OpenPGP
__________________________________________________________________________ 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
