From: rhevm-api-bounces(a)lists.fedorahosted.org [mailto:rhevm-api-
bounces(a)lists.fedorahosted.org] On Behalf Of Mark McLoughlin
...
I guess there are two things I'm trying to avoid:
- Having to support a client requesting 1.0 when the current version
is 1.1 - if the changes between 1.0 and 1.1 are compatible, it
really only adds a headache for us with no big benefit
[IH] I wouldn't set
as a goal backward compatibility for all times.
Deprecating an API should be possible between major versions (or between
two major versions, giving users time to adjust).
- Getting into a situation where we can't backport features because
we can't bump the version number - i.e. it's better to do feature
negotiation on a per-feature basis rather than using a version
number that identifies a set of features
[IH] this has a testing overhead
though