| |
|
 |
|
 |
|
|
|
| |
|
|
xen-api
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.
Thanks!
Rob
|
evolution.pdf
Description: evolution.pdf
_______________________________________________
xen-api mailing list
xen-api@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/mailman/listinfo/xen-api
|
| <Prev in Thread] |
Current Thread |
[Next in Thread>
|
- [Xen-API] API evolution,
Rob Hoes <=
|
|
|
| |
|
Home