There's a couple more points to be made here, I think.
First, we've also gone to a great deal of effort to make upgrading
seamless, and we recently (1.0.3) added support for seamless
downgrading as well. Anyone with a staging cluster (which should be
everyone) can drop 1.0.4 on a single node, see
I think we definitely need better quality for the releases. Just looked at
1.0.3 and 1.0.4. I am willing to test out release candidate and report
back my finding on the mailing list. Hopefully more folks can do that to
make the testing more comprehensive. And folks with binding votes can take
t
I need at least a week, maybe two to promote anything to staging which is
mainly because we do weekly releases. I could introduce a 2 day turn around
but only with a more fixed type schedule. I am running 0.8.6 in production and
REALLY want to upgrade for nothing more than getting compression
On Tue, Nov 29, 2011 at 6:16 PM, Jeremy Hanna wrote:
> I'd like to start a discussion about ideas to improve release quality for
> Cassandra. Specifically I wonder if the community can do more to help the
> project as a whole become more solid. Cassandra has an active and vibrant
> community usi
I'd like to start a discussion about ideas to improve release quality for
Cassandra. Specifically I wonder if the community can do more to help the
project as a whole become more solid. Cassandra has an active and vibrant
community using Cassandra for a variety of things. If we all pitch in a
