So does that mean the versioning policy is UNUSED.MAJOR.MINOR
where UNUSED is well, unused or some other marker, and a change to MAJOR means binary incompatibility, and a change to MINOR is new features or bug fixes which do not mean binary incompatibility? Just want to get a sense of when I should be worried about an upgrade (I know talking about upgrades is probably fairly silly based on the fact there has only been one release, but still I like to plan ahead). A somewhat related question, I'm using an svn external to keep a tree in my svn project which builds rpms and maven packages. I currently have that tree pointed at the HEAD, but that seems risky because its a moving target. I'd like to point at the 0.3.0 release. Does the cassandra-0.3.0-rc3 tag represent that release? (ie, if I were to download the tarball and checkout that tag would the code be equivalent) Thanks, -Anthony On Wed, Jul 01, 2009 at 05:34:11PM -0500, Jonathan Ellis wrote: > 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<[email protected]> > 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 <[email protected]> > > -- ------------------------------------------------------------------------ Anthony Molinaro <[email protected]>
