Open Stack

On Sun, Apr 26, 2015 at 7:24 PM, Tom Fifield <tom at openstack.org> wrote:

> Hi,
>
> This isn't my patch, but I'm just pulling this on to the mailing list
> since I saw it languishing: https://review.openstack.org/#/c/155329/ :)
>
> In this patch, the sample json files are updated for new things that are
> coming in Kilo. However, as Anne notes: "This site is updated
> continually, but it seems like these JSON examples won't be accurate
> until the next version comes out. What should we do in this case?"
>
> Then it's noted that we have folks using trunk, etc.
>
> So - API site versioning - how do we solve it for "all APIs and those
> with extensions" ?
>

This needs blueprint-level design decisions and a spec. Ideally we'll rid
ourselves of WADL in the design as well.

I'd like to take this on next release and I'm looking for collaborators.
Extensible APIs make versioning especially difficult.

Thanks,
Anne


>
>
> Regards,
>
>
> Tom
>
> _______________________________________________
> OpenStack-docs mailing list
> OpenStack-docs at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-docs
>



-- 
Anne Gentle
annegentle at justwriteclick.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-docs/attachments/20150426/27353511/attachment.html>