<html><head>
<meta content="text/html; charset=ISO-8859-1" http-equiv="Content-Type">
</head><body text="#000000" bgcolor="#FFFFFF">I think this is a bit of a
roadblock for us getting the new Navigator up, so the sooner we can
come to a decision the better :) Thanks for raising the issue with the
TC!<br>
<span>
</span><br>
<blockquote style="border: 0px none;"
cite="mid:a08bfeba-7b4a-8cbc-a2d5-329a56ce2f1e@openstack.org"
type="cite">
<div style="margin:30px 25px 10px 25px;" class="__pbConvHr"><div
style="width:100%;border-top:1px solid #EDEEF0;padding-top:5px"> <div
style="display:inline-block;white-space:nowrap;vertical-align:middle;width:49%;">
<a moz-do-not-send="true" href="mailto:thierry@openstack.org"
style="color:#737F92
!important;padding-right:6px;font-weight:bold;text-decoration:none
!important;">Thierry Carrez</a></div> <div
style="display:inline-block;white-space:nowrap;vertical-align:middle;width:48%;text-align:
right;"> <font color="#9FA2A5"><span style="padding-left:6px">March
31, 2017 at 3:43 AM</span></font></div> </div></div>
<div style="color:#888888;margin-left:24px;margin-right:24px;"
__pbrmquotes="true" class="__pbConvBody"><div><!----><br>I like the idea
to provide unified API information, however I'm not sure<br>the
Technical Committee should stand in the way of getting that<br>information
updated. The less we force through strict governance<br>processes, the
better, so everything that can be maintained by some<br>other group
should be.<br><br>This is closer to documentation than governance, so I
wonder if this<br>document should not be maintained at the API WG or the
Docs team or<br>service catalog level -- just keeping the same team
names so that<br>information can be easily cross-referenced with the
governance repository.<br><br>I'll raise the discussion in open
discussion at the next TC meeting.<br><br></div></div>
<div style="margin:30px 25px 10px 25px;" class="__pbConvHr"><div
style="width:100%;border-top:1px solid #EDEEF0;padding-top:5px"> <div
style="display:inline-block;white-space:nowrap;vertical-align:middle;width:49%;">
<a moz-do-not-send="true" href="mailto:rosmaita.fossdev@gmail.com"
style="color:#737F92
!important;padding-right:6px;font-weight:bold;text-decoration:none
!important;">Brian Rosmaita</a></div> <div
style="display:inline-block;white-space:nowrap;vertical-align:middle;width:48%;text-align:
right;"> <font color="#9FA2A5"><span style="padding-left:6px">March
29, 2017 at 9:23 PM</span></font></div> </div></div>
<div style="color:#888888;margin-left:24px;margin-right:24px;"
__pbrmquotes="true" class="__pbConvBody"><div>On 3/29/17 12:55 AM, Jimmy
McArthur wrote:<br>[snip]<br></div><div><!----><br>See what you think
of these. They add an "apis" section to the glance<br>section of
projects.yaml in the governance repo.<br><br><a class="moz-txt-link-freetext" href="http://paste.openstack.org/show/604775/">http://paste.openstack.org/show/604775/</a>
has a complete history, where<br>for each release, the complete set of
versions of the API that are<br>available in that release (and their
statuses) are listed.<br><br><a class="moz-txt-link-freetext" href="http://paste.openstack.org/show/604776/">http://paste.openstack.org/show/604776/</a> has
an abbreviated history,<br>where only the changes in available APIs are
listed from version to<br>version, and if there's no change, the
release isn't listed at all.<br><br>I don't know if this format would
work for microversions, though. (And<br>I don't know if it's a good
idea in the first place.)<br><br><br>__________________________________________________________________________<br>OpenStack
Development Mailing List (not for usage questions)<br>Unsubscribe:
<a class="moz-txt-link-abbreviated" href="mailto:OpenStack-dev-request@lists.openstack.org?subject:unsubscribe">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br><a class="moz-txt-link-freetext" href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br></div></div>
<div style="margin:30px 25px 10px 25px;" class="__pbConvHr"><div
style="width:100%;border-top:1px solid #EDEEF0;padding-top:5px"> <div
style="display:inline-block;white-space:nowrap;vertical-align:middle;width:49%;">
<a moz-do-not-send="true" href="mailto:jimmy@openstack.org"
style="color:#737F92
!important;padding-right:6px;font-weight:bold;text-decoration:none
!important;">Jimmy McArthur</a></div> <div
style="display:inline-block;white-space:nowrap;vertical-align:middle;width:48%;text-align:
right;"> <font color="#9FA2A5"><span style="padding-left:6px">March
28, 2017 at 11:55 PM</span></font></div> </div></div>
<div style="color:#888888;margin-left:24px;margin-right:24px;"
__pbrmquotes="true" class="__pbConvBody">
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
<br>
<span>
</span>Brian,<br>
<br>
Thanks for the response. This is a tough one. Currently we're pulling
API data manually for each project. That is no longer tenable when we're
talking about 40+ projects. Plus, this is info is something that is
really sought after by the community. Some thoughts below:<br>
<blockquote type="cite"
cite="mid:ba145185-01eb-b5b1-4897-2af8017bf2a3@gmail.com" style="border:
0px none;"><div class="__pbConvHr" style="margin:30px 25px 10px 25px;"><div
style="width:100%;border-top:1px solid #EDEEF0;padding-top:5px"> <div
style="display:inline-block;white-space:nowrap;vertical-align:middle;width:49%;">
<a style="color:#737F92
!important;padding-right:6px;font-weight:bold;text-decoration:none
!important;" href="mailto:rosmaita.fossdev@gmail.com"
moz-do-not-send="true">Brian Rosmaita</a></div> <div
style="display:inline-block;white-space:nowrap;vertical-align:middle;width:48%;text-align:
right;"> <font color="#9FA2A5"><span style="padding-left:6px">March
28, 2017 at 10:25 PM</span></font></div> </div></div>
<div class="__pbConvBody" __pbrmquotes="true" style="color: rgb(136,
136, 136); margin-left: 24px;
margin-right: 24px;"><pre wrap="">On 3/27/17 5:01 PM, Lauren Sell wrote:
</pre>
I don't have a helpful recommendation here, but the version history for
Glance is incorrect as well. We maintain a version history in the
glance api-ref [0], but that's probably not much help (and, as you point
out, is idiosyncratic to Glance anyway). At this point, though, my
primary concern is that it's showing a deprecated API version as the
latest release. What format would it be useful for you to get this data
in?</div></blockquote>
What we really need is the following:<br>
<br>
* A project history, including the date of project inception that's
included in the TC tags.<br>
* An API history in an easily digestible format that all projects share.
So whether you're doing micro releases or not, just something that
allows us to show, based on a release timeline, which API versions per
project are applicable for each OpenStack release. This really needs to
be consistent from project to project b/c at the moment everyone handles
it differently.<br>
<blockquote type="cite"
cite="mid:ba145185-01eb-b5b1-4897-2af8017bf2a3@gmail.com" style="border:
0px none;"><div class="__pbConvBody" __pbrmquotes="true"
style="color:#888888;margin-left:24px;margin-right:24px;">
<pre wrap="">thanks,
brian
[0]
<a moz-do-not-send="true" href="https://developer.openstack.org/api-ref/image/versions/index.html#version-history" class="moz-txt-link-freetext">https://developer.openstack.org/api-ref/image/versions/index.html#version-history</a>
__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: <a moz-do-not-send="true" href="mailto:OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" class="moz-txt-link-abbreviated">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a>
<a moz-do-not-send="true" href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" class="moz-txt-link-freetext">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a>
</pre>
</div></blockquote>
<br>
<pre wrap="">__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: <a class="moz-txt-link-abbreviated" href="mailto:OpenStack-dev-request@lists.openstack.org?subject:unsubscribe">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a>
<a class="moz-txt-link-freetext" href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a>
</pre></div>
<div style="margin:30px 25px 10px 25px;" class="__pbConvHr"><div
style="width:100%;border-top:1px solid #EDEEF0;padding-top:5px"> <div
style="display:inline-block;white-space:nowrap;vertical-align:middle;width:49%;">
<a moz-do-not-send="true" href="mailto:rosmaita.fossdev@gmail.com"
style="color:#737F92
!important;padding-right:6px;font-weight:bold;text-decoration:none
!important;">Brian Rosmaita</a></div> <div
style="display:inline-block;white-space:nowrap;vertical-align:middle;width:48%;text-align:
right;"> <font color="#9FA2A5"><span style="padding-left:6px">March
28, 2017 at 10:25 PM</span></font></div> </div></div>
<div style="color:#888888;margin-left:24px;margin-right:24px;"
__pbrmquotes="true" class="__pbConvBody"><pre wrap="">On 3/27/17 5:01 PM, Lauren Sell wrote:
</pre><blockquote type="cite"><pre wrap="">Hi Matt,
Thanks for the feedback.
</pre><blockquote type="cite"><pre wrap="">On Mar 24, 2017, at 3:50 PM, Matt Riedemann <a class="moz-txt-link-rfc2396E" href="mailto:mriedemos@gmail.com"><mriedemos@gmail.com></a> wrote:
</pre></blockquote></blockquote><pre wrap=""><!---->[snip]
</pre><blockquote type="cite"><blockquote type="cite"><pre wrap="">2. The "API Version History" section in the bottom right says:
"Version v2.1 (Ocata) - LATEST RELEASE"
And links to <a class="moz-txt-link-freetext" href="https://releases.openstack.org/">https://releases.openstack.org/</a> <a class="moz-txt-link-rfc2396E" href="https://releases.openstack.org/"><https://releases.openstack.org/></a>. The latest compute microversion in Ocata was actually 2.42:
<a class="moz-txt-link-freetext" href="https://docs.openstack.org/developer/nova/api_microversion_history.html">https://docs.openstack.org/developer/nova/api_microversion_history.html</a> <a class="moz-txt-link-rfc2396E" href="https://docs.openstack.org/developer/nova/api_microversion_history.html"><https://docs.openstack.org/developer/nova/api_microversion_history.html></a>
I'm wondering how we can better sort that out. I guess "API Version History" in the navigator is meant more for major versions and wasn't intended to handle microversions? That seems like something that should be dealt with at some point as more and more projects are moving to using micro versions.
</pre></blockquote><pre wrap="">Agreed, we could use some guidance here. From what we can tell, each team logs these a little bit differently, so there’s no easy way for us to pull them. Could we output the correct link as a tag for each project, or does anyone have a recommendation?
</pre></blockquote><pre wrap=""><!---->
I don't have a helpful recommendation here, but the version history for
Glance is incorrect as well. We maintain a version history in the
glance api-ref [0], but that's probably not much help (and, as you point
out, is idiosyncratic to Glance anyway). At this point, though, my
primary concern is that it's showing a deprecated API version as the
latest release. What format would it be useful for you to get this data in?
thanks,
brian
[0]
<a class="moz-txt-link-freetext" href="https://developer.openstack.org/api-ref/image/versions/index.html#version-history">https://developer.openstack.org/api-ref/image/versions/index.html#version-history</a>
__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: <a class="moz-txt-link-abbreviated" href="mailto:OpenStack-dev-request@lists.openstack.org?subject:unsubscribe">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a>
<a class="moz-txt-link-freetext" href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a>
</pre></div>
</blockquote>
<br>
</body></html>