incubator-cassandra-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jonathan Ellis <>
Subject Re: major version release schedule
Date Tue, 20 Dec 2011 14:16:23 GMT
Nobody's forcing you to upgrade.  If you want twice as much time
between upgrading, just wait for 1.2.  In the meantime, people who
need the features in 1.1 also get those early (no, running trunk in
production isn't a serious option).  I don't see any real benefit for
you in forcing your preference on everyone, and I see a big negative
for some.

It's also worth noting that waiting for 2x as many features for freeze
will result in MORE than 2x as much complexity for tracking down
regressions.  Given the limited testing we get during freeze, I think
that's a pretty strong argument in favor of more-frequent, smaller

On Tue, Dec 20, 2011 at 7:42 AM, Radim Kolar <> wrote:
> I read it but things are different now because magic 1.0 is out. If you
> implement 1.0 and put it into production, you really do not want to retest
> app on new version every 4 months and its unlikely that you will get
> migration approved by management unless you present clear benefits for such
> migration. Compression was nice new feature of 1.0 but it was rejected by
> lot of IT managers  as "too risky" for now.
> While you can test application quite easily, testing cluster stability is
> way harder in test environment because its not usually possible to fully
> replicate workload and data volume in test environment and migration back is
> difficult because Cassandra currently does not have tool for fast sstable
> downgrade (1.0 -> 0.8).
> For production use long time between major releases is better. I would
> double time between major releases, maybe not for 1.1/1.2 but later for
> sure.  Take look at postgresql project, they release 1 major version per
> year and they support 4 major versions for bugfixes and older postgresql
> versions are still common in production.
> Did you asked people running mission critical workloads about their opinion?
> Another possibility is to use ISV like Datastax to provide long term
> support.

Jonathan Ellis
Project Chair, Apache Cassandra
co-founder of DataStax, the source for professional Cassandra support

View raw message