On Sun, Sep 11, 2011 at 1:45 PM, Mike Nerone <[email protected]> wrote: > On Sun, Sep 11, 2011 at 2:10 PM, Andrey Zhuchkov <[email protected]>wrote: > >> So from my point of view there is a need to handle different milestones in >> different ways even if you drop API 1.0. Actually, I still don't know how >> to >> implement such support gracefully and very appreciate your suggestions. >> > > Even if we decide to support multiple API versions, I think the goal should > be to support, at most: A. Past final, published version specifications, and > B. The current state of the version that's in development. The purpose of > the latter is to have support implemented or nearly so when the spec is > finalized. Support for an unstable spec is inherently unstable, and no > attempt should be made to support milestones interim specs on an ongoing > basis.
Strictly speaking, in the past, libcloud has only supported something when there is an API out in the real world that we can hit, because specs are lies in the cloud. We've done this dance before trying to get vCloud to work, but the provider implementations all ended up doing different crap. IMO, the best thing for libcloud to do is to support what is in production, not some future standrad, or past versions that no one is running on the internet.
