On Tue, 2010-04-13 at 09:50 +0100, Mark McLoughlin wrote:
- The initial release of the api has version=1.0 media types
- All changes in future releases must be backwards compatible
- We reserve the right to bump the major version of any individual
media type if we really need to make a backwards incompatible
change; in that event, clients will still be able negotiate the
original media type
I should clarify - this way, we'd never bump the minor number
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
- 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
Mark.