<div dir="ltr">Hi all, <div>Now that you've got a decent start, how about checking it in as a doc/source/ document in the nova repository? Seems better than keeping it in the wiki so that you can update with code changes.</div>

<div>Anne</div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Wed, Nov 13, 2013 at 11:11 PM, Alex Xu <span dir="ltr"><<a href="mailto:xuhj@linux.vnet.ibm.com" target="_blank">xuhj@linux.vnet.ibm.com</a>></span> wrote:<br>

<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
  
    
  
  <div bgcolor="#FFFFFF" text="#000000"><div><div class="h5">
    <div>On 2013年11月14日 07:09, Christopher Yeoh
      wrote:<br>
    </div>
    <blockquote type="cite">
      <div dir="ltr">
        <div class="gmail_extra">
          <div class="gmail_quote">On Thu, Nov 14, 2013 at 7:52 AM,
            David Kranz <span dir="ltr"><<a href="mailto:dkranz@redhat.com" target="_blank">dkranz@redhat.com</a>></span>
            wrote:<br>
            <blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
              <div bgcolor="#FFFFFF" text="#000000">
                <div>
                  <div>
                    <div>On 11/13/2013 08:30 AM, Alex Xu wrote:<br>
                    </div>
                  </div>
                </div>
                <blockquote type="cite">
                  <div>
                    <div> <font size="3">Hi, guys<br>
                        <br>
                        This is the document for the changes from Nova
                        v2 api to v3: </font><br>
                      <a href="https://wiki.openstack.org/wiki/NovaAPIv2tov3" target="_blank">https://wiki.openstack.org/wiki/NovaAPIv2tov3</a><br>
                      I will appreciate if anyone can help for review
                      it.<br>
                      <br>
                      Another problem comes up - how to keep the doc
                      updated. So can we ask people, who change<br>
                      something of api v3, update the doc accordingly? I
                      think it's a way to resolve it.<br>
                      <br>
                      Thanks<br>
                      Alex<br>
                      <br>
                      <br>
                      <fieldset></fieldset>
                      <br>
                    </div>
                  </div>
                  <pre>_______________________________________________
openstack-qa mailing list
<a href="mailto:openstack-qa@lists.openstack.org" target="_blank">openstack-qa@lists.openstack.org</a>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-qa" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-qa</a>
</pre>
                </blockquote>
                Thanks, this is great. I fixed a bug in the os-services
                section. BTW, <a href="mailto:openstack-qa@lists.openstack.org" target="_blank">openstack-qa@lists.openstack.org</a>
                list is obsolete. openstack-dev with subject starting
                with [qa] is the current "qa list". About updating, I
                think this will have to be heavily socialized in the
                nova team. The initial review should happen by those
                reviewing the tempest v3 api changes. That is how I
                found the os-services bug.<span><font color="#888888"><br>
                    <br>
                  </font></span></div>
            </blockquote>
            <div><br>
            </div>
            <div>Can we leverage off the DocImpact flag with the commit
              message somehow - say anytime there is a changeset<br>
              with DocImpact and that changes a file under
              nova/api/openstack/compute we generate a notification?<br>
            </div>
            <br>
          </div>
          <div class="gmail_quote">I think we're getting much better at
            enforcing the DocImpact flag during reviews.<br>
          </div>
        </div>
      </div>
    </blockquote></div></div>
    +1 for DocImpact flag, that's good idea.<br>
    <blockquote type="cite">
      <div dir="ltr">
        <div class="gmail_extra">
          <div class="gmail_quote"><br>
            Chris.<br>
          </div>
        </div>
      </div>
      <br>
      <fieldset></fieldset>
      <br>
      <pre>_______________________________________________
OpenStack-dev mailing list
<a href="mailto:OpenStack-dev@lists.openstack.org" target="_blank">OpenStack-dev@lists.openstack.org</a>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a>
</pre>
    </blockquote>
    <br>
  </div>

<br>_______________________________________________<br>
OpenStack-dev mailing list<br>
<a href="mailto:OpenStack-dev@lists.openstack.org">OpenStack-dev@lists.openstack.org</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
<br></blockquote></div><br></div>