<html><head><meta http-equiv="Content-Type" content="text/html charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div id="magicdomid2" class="" style="margin: 0px; padding: 0px; font-variant-ligatures: normal; orphans: 2; widows: 2;"><font face="Helvetica Neue, Arial, sans-serif" class=""><span style="font-size: 12px;" class="">Greetings OpenStack community,<br class=""><br class="">Today's meeting was even shorter and sweeter than last week's, as only edleafe was present, due to cdent being on PTO and elmiko being on the road. Prior to the meeting, though, we had decided that the guideline change for raising the minimum microversion was ready for freeze, and so it was indeed frozen. Other than that, there really is nothing else to report.<br class=""><br class=""># Newly Published Guidelines<br class=""><br class="">None this week<br class=""><br class=""># API Guidelines Proposed for Freeze<br class=""><br class="">Guidelines that are ready for wider review by the whole community.<br class=""><br class="">* Microversions: add next_min_version field in version body<br class=""> <a href="https://review.openstack.org/#/c/446138/" class="">https://review.openstack.org/#/c/446138/</a><br class=""><br class=""># Guidelines Currently Under Review [3]<br class=""><br class="">* A (shrinking) suite of several documents about doing version discovery<br class=""> Start at https://review.openstack.org/#/c/459405/<br class=""><br class="">* Fix html_last_updated_fmt for Python3<br class=""> https://review.openstack.org/475219<br class=""><br class="">* WIP: microversion architecture archival doc (very early; not yet ready for review)<br class=""> https://review.openstack.org/444892<br class=""><br class=""># Highlighting your API impacting issues<br class=""><br class="">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.<br class=""><br class="">To learn more about the API WG mission and the work we do, see OpenStack API Working Group [2].<br class=""><br class="">Thanks for reading and see you next week!<br class=""><br class=""># References<br class=""><br class="">[1] http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev<br class="">[2] http://specs.openstack.org/openstack/api-wg/<br class="">[3] https://review.openstack.org/#/q/status:open+project:openstack/api-wg,n,z<br class=""><br class="">Meeting Agenda<br class="">https://wiki.openstack.org/wiki/Meetings/API-WG#Agenda<br class="">Past Meeting Records<br class="">http://eavesdrop.openstack.org/meetings/api_wg/<br class="">Open Bugs<br class="">https://bugs.launchpad.net/openstack-api-wg<br class=""></span></font><div class=""><font face="Helvetica Neue, Arial, sans-serif" class=""><span style="font-size: 12px;" class=""><br class="">-- Ed Leafe<br class=""><br class=""><br class=""><br class=""><br class=""></span></font></div><br class=""></div></body></html>