On Thu, Jan 13, 2011 at 1:46 PM, Ryan King <r...@twitter.com> wrote: > I'm a -1 on naming the next release 1.0 because I don't think it has > the quality that 1.0 implies, but to be honest I don't really care > that much. The version numbers don't really effect those that of use > that are running production clusters. Calling it 1.0 won't make it any > more stable or faster.
"Those of us running production clusters" jumps out at me here. Being production-ready is THE major thing that 1.0 is supposed to signal; the other things I mentioned (features, upgrade path, etc) are signals that can help determine that, but actual production clusters is the real story. In other words, at some point you have so many production users that it's silly to pretend it's ready for 1.0. I'd say we've passed that point. > those of use who've been around > have new things we care about. Of course this will always be true and > at some point we need to draw a line in the sand and put the 1.0 stamp > on it Right. 1.0 shouldn't mean "it does everything we can think of," it means "it is reasonably feature complete and stable for a given purpose," then you add features and expand your problem domain and so forth in future versions. I think that being able to put a check mark by every single item on that 2009 list and then some is a very strong signal that we've reached a milestone, even though we can now think of more things we want. Projects that reserve 1.0 for some abstract vision of unattainable perfection frustrate me. > 1. make the distributed test suite more reliable (its admittedly flaky > on ec2) and flesh it out to include all distributed functionality. We > shouldn't run a distributed system without distributed tests. We'll > work on the flakiness, but we need people to write tests (and > reviewers to require tests). I'm on board with this, to the point that Riptano is hiring a full-time QA engineer to contribute here. -- Jonathan Ellis Project Chair, Apache Cassandra co-founder of Riptano, the source for professional Cassandra support http://riptano.com
