+1 This seems similar enough to the semantic versioning spec http://semver.org/. (minus the third value) that it may be convenient and worthwhile to implement the full spec.
On Wed, Jan 6, 2010 at 3:58 PM, Eric Evans <eev...@rackspace.com> wrote: > On Thu, 2010-01-07 at 08:41 +1100, Ian Holsman wrote: >> can you add a new method api_version? >> some people will probably still want to know the version of the >> software being run, and it is still useful info to have for >> operational issues. > > Yeah, you could, and that was what I had in mind initially. The > conclusion I came to though was that with a properly versioned API, the > software version was really only of interest to operations, and that it > would be better published along with the rest of our management info, > (via JMX). > >> +1 on the numbering scheme. >> >> as for breaking something that works (ie a client library), you can >> make the client library just have a 'SUPPORTED_VERSION' api call and a >> 'reported_version' api call, and let the application decide. > > Sure. > > -- > Eric Evans > eev...@rackspace.com > >
