yeah, that's good idea. That can keep the doc update with code. I will try to convert the wiki to rst format, then submit to gerrit.

On 2013?12?07? 00:12, Anne Gentle wrote:
Hi all,
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.
Anne


On Wed, Nov 13, 2013 at 11:11 PM, Alex Xu <[email protected] <mailto:[email protected]>> wrote:

    On 2013?11?14? 07:09, Christopher Yeoh wrote:
    On Thu, Nov 14, 2013 at 7:52 AM, David Kranz <[email protected]
    <mailto:[email protected]>> wrote:

        On 11/13/2013 08:30 AM, Alex Xu wrote:
        Hi, guys

        This is the document for the changes from Nova v2 api to v3:
        https://wiki.openstack.org/wiki/NovaAPIv2tov3
        I will appreciate if anyone can help for review it.

        Another problem comes up - how to keep the doc updated. So
        can we ask people, who change
        something of api v3, update the doc accordingly? I think
        it's a way to resolve it.

        Thanks
        Alex



        _______________________________________________
        openstack-qa mailing list
        [email protected]  
<mailto:[email protected]>
        http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-qa
        Thanks, this is great. I fixed a bug in the os-services
        section. BTW, [email protected]
        <mailto:[email protected]> 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.


    Can we leverage off the DocImpact flag with the commit message
    somehow - say anytime there is a changeset
    with DocImpact and that changes a file under
    nova/api/openstack/compute we generate a notification?

    I think we're getting much better at enforcing the DocImpact flag
    during reviews.
    +1 for DocImpact flag, that's good idea.

    Chris.


    _______________________________________________
    OpenStack-dev mailing list
    [email protected]  
<mailto:[email protected]>
    http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


    _______________________________________________
    OpenStack-dev mailing list
    [email protected]
    <mailto:[email protected]>
    http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev




_______________________________________________
OpenStack-dev mailing list
[email protected]
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

_______________________________________________
OpenStack-dev mailing list
[email protected]
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Reply via email to