Release 1.0.0: July 1st?

[Doug Cutting <cu...@apache.org>]

I'd like to make a release soon, so that folks can start using Avro. 
I'd like to call the first release 1.0.0.

I propose that the Avro version convention is that only major releases 
permit forward and/or backward data format incompatibilities.  So, by 
calling this 1.x.x, we commit to not altering the specification accept 
to potentially add new features whose presence does not affect 
compatibility with any existing features until release 2.x.x.

Minor releases would permit API incompatibilities.  So 1.1.X APIs may 
not be compatible with 1.0.1 APIs, but all 1.0.X releases should be API 
compatible bugfix releases.

Does that sound like a reasonable policy?

It would be nice to have more complete C and/or C++ support working in 
1.0.0, but that's not strictly required: we can add it in subsequent 
releases.

So I propose to make a 1.0.0 release on July 1st.  Objections?

Doug

Re: Release 1.0.0: July 1st?

[Amr Awadallah <aa...@cloudera.com>]

+1

really looking forward to it.

-- amr

Doug Cutting wrote:
> I'd like to make a release soon, so that folks can start using Avro. 
> I'd like to call the first release 1.0.0.
>
> I propose that the Avro version convention is that only major releases 
> permit forward and/or backward data format incompatibilities.  So, by 
> calling this 1.x.x, we commit to not altering the specification accept 
> to potentially add new features whose presence does not affect 
> compatibility with any existing features until release 2.x.x.
>
> Minor releases would permit API incompatibilities.  So 1.1.X APIs may 
> not be compatible with 1.0.1 APIs, but all 1.0.X releases should be 
> API compatible bugfix releases.
>
> Does that sound like a reasonable policy?
>
> It would be nice to have more complete C and/or C++ support working in 
> 1.0.0, but that's not strictly required: we can add it in subsequent 
> releases.
>
> So I propose to make a 1.0.0 release on July 1st.  Objections?
>
> Doug