Mailing-List: contact cassandra-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: cassandra-dev@incubator.apache.org
Received-SPF: neutral (athena.apache.org: local policy)
Subject: Re: API versioning
From: Eric Evans <eevans@rackspace.com>
To: cassandra-dev@incubator.apache.org
In-Reply-To: <1262818548.3403.67.camel@erebus.lan>
References: <1262809418.3403.33.camel@erebus.lan>
	 <9C131766-4EA4-4C9D-9E58-76B1769034C0@Holsman.net>
	 <1262815088.3403.49.camel@erebus.lan>
	 <f38abbfa1001061433s2a0588bfr61cc495a0fe01080@mail.gmail.com>
	 <1262818548.3403.67.camel@erebus.lan>
Content-Type: text/plain; charset="UTF-8"
Date: Mon, 11 Jan 2010 13:06:50 -0600
Message-ID: <1263236810.7146.37.camel@erebus.lan>
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit

On Wed, 2010-01-06 at 16:55 -0600, Eric Evans wrote:
> On Wed, 2010-01-06 at 16:33 -0600, Denny Abraham wrote:
> > 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. 
> 
> The third value here is for "backward compatible bug fixes", (as others
> here have suggested). The wording on the page eludes to changes that
> "fix incorrect behavior", or "these are changes that could create
> problems if the library relied on buggy behavior" (my words).
> 
> I can get on board with that.
> 
> So that would make, x.y.z where x is major, y is minor, and z is patch
> level. The major is bumped for breaking changes, the minor is bumped for
> changes in features or functionality that are backward compatible, and
> the patch level is bumped for every other change.
> 

FYI, this was put in place in CASSANDRA-686. The current API version is
now "1.0.0".

Thanks everyone.

-- 
Eric Evans
eevans@rackspace.com