[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Xen-API] API evolution

  • To: "'xen-api@xxxxxxxxxxxxxxxxxxx'" <xen-api@xxxxxxxxxxxxxxxxxxx>
  • From: Rob Hoes <Rob.Hoes@xxxxxxxxxx>
  • Date: Fri, 7 May 2010 14:25:54 +0100
  • Accept-language: en-US
  • Acceptlanguage: en-US
  • Delivery-date: Fri, 07 May 2010 06:26:22 -0700
  • List-id: Discussion of API issues surrounding Xen <xen-api.lists.xensource.com>
  • Thread-index: Acrt6NHordZcpKmwSC64JdWuB9A+dA==
  • Thread-topic: API evolution

Hi all,


Following the changeset related to the API Evolution document I just submitted. This is an update to the document that Dave Scott started a few weeks ago. A PDF is attached.


The intention is to agree on the best way to evolve the XenAPI from release to release. Especially now the API is becoming mature, and is used by more and more people, it is important to make clear what exactly is part of the XenAPI, how things may change over time, how we announce changes in terms of release notes, and what sort of compatibility guarantees can be made.


The attached document is an initial proposal that would benefit from a good discussion, especially on the topic of compatibility. I’d like to invite everyone who has ideas or experiences related to this to share these.





Attachment: evolution.pdf
Description: evolution.pdf

xen-api mailing list



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.