cloudstack-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Chip Childers <chip.child...@sungard.com>
Subject Re: backwards compatibility question
Date Mon, 01 Jul 2013 13:51:38 GMT
On Mon, Jul 01, 2013 at 02:50:08PM +0200, Daan Hoogland wrote:
> H,
> 
> In the network thing I am trying to get you people to accept I want to add
> a parameter to an api call. What is the policy (does it adhere to common
> sense)? It is an extra parameter to the end of an otherwise unchanged call.
> I am still checking to make sure it is really optional. If it is not can it
> go in 4.3? Or must it wait till 5.0?
> 
> thanks,
> Daan

If you can add it as an optional param, with a reasonable default for
backward compatibility, then it wouldn't cause us to bump the major
version from 4 to 5.  If there really isn't a logical default (and the
param is *required*), then we would need to bump to 5 (based on current
consensus for version numbering).

We don't have any "plans" for a 5.x release line yet, and of course,
past consensus can be changed.  I expect that if we bump from 4 to 5,
there will be a decent number of API changes that we'd want to also make
(perhaps going so far as to switch from the query-based API approach to
a RESTful model, or perhaps not).

-chip

Mime
View raw message