[prev in list] [next in list] [prev in thread] [next in thread] 

List:       avro-dev
Subject:    Re: version/spec number correspondence
From:       Doug Cutting <cutting () apache ! org>
Date:       2010-08-31 22:55:03
Message-ID: 4C7D8847.8060309 () apache ! org
[Download RAW message or body]

On 08/31/2010 03:03 PM, Michael Glaesemann wrote:
> What is the correspondence between the Avro Spec version number and
> the library release version number? Currently there's a release
> candidate for 1.4.0. The current spec is version 1.3.3. Is there a
> spec for 1.4.0 somewhere, or is it just what's implemented in the
> code?

The spec is in the doc/ directory, so it's versioned with the library.

> What is the procedure for providing updated releases which provide
> only bug fixes or further compliance for a particular spec version,
> rather than against current? Considering the different language
> libraries have varying bugs and spec compliance, it would be nice to
> be able to, say, provide bug fixes or further spec compliance,
> recognizing that it's just a bug fix release.

The major version number indicates spec compatibility.  No incompatible 
changes to the spec should be introduced until release 2.0.  However new 
features may be added into the spec, if they're compatible.

Minor version numbers indicate API compatibility.  No incompatible 
changes to APIs should be made for all 1.4.* releases.

Dot releases can include bugfixes, typically only regressions, and even 
new features, if those new features have little chance of creating 
regressions.  So 1.4.1 should mostly contain bugfixes for regressions, 
but might contain new features if we are convinced that they're not 
destabilizing and do not break APIs.

Doug

[prev in list] [next in list] [prev in thread] [next in thread]