incubator-cassandra-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jonathan Ellis <jbel...@gmail.com>
Subject Re: Cassandra version number policy
Date Wed, 01 Jul 2009 22:34:11 GMT
We have already committed to breaking disk format for 0.4 (to fix OOM
conditions).  To me 0.3 to 0.4 is major (like with postgresql 8.3 to
8.4) but I guess it's just semantics.

-Jonathan

On Wed, Jul 1, 2009 at 1:14 PM, Anthony Molinaro<anthonym@pinkbunny.net> wrote:
> Hi,
>
>  I've been lurking on this list for a little bit and notice that you've
> talked about a change to the on disk data format which would be incompatible
> with prior versions.
>
> Will that change be a major version bump (ie, will it be 1.0.0)? If not what
> is the policy regarding versions for cassandra?
>
> I'm used to the MAJOR.MINOR.RELEASE versioning where
>
> MAJOR is a binary incompatible change
> MINOR is new functionality added
> RELEASE is for bug fixes without new functionality
>
> Does cassandra follow this or some other strategy?
>
> -Anthony
>
> --
> ------------------------------------------------------------------------
> Anthony Molinaro                           <anthonym@alumni.caltech.edu>
>

Mime
View raw message