Thanks Lakshmi, that's useful. So, we want to release Artifacts API in Kilo as experimental. We do need some early adopters to begin working with it (the initial interest was from Heat and Murano projects, and the OVA/OVF initiative for Images as well) in the next cycle and provide some feedback on the API and its usefulness, so we may take this feedback into account before releasing the stable version of API with L. I've talked to Murano folks, they are ok with that plan, some feedback from Heat and OVA teams would be great as well.
Anyways, we will not break the compatibility without serious reasons for that, and we will collaborate with any early adopters about any such breaking changes. -- Regards, Alexander Tivelkov On Thu, Mar 12, 2015 at 8:19 PM, Sampath, Lakshmi <lakshmi.samp...@hp.com> wrote: > We had a discussion with API WG today about what it means to be an > "EXPERIMENTAL API" and here's the takeway from that discussion. > > - API's can be experimental, but mark it clearly in the docs as such > - Experimental means a breaking change may be introduced > - Use /x1/ instead of /v1/ in the endpoint. > > Thoughts/Suggestions? > > > Thanks > Lakshmi. > > __________________________________________________________________________ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev >
__________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
