Along with Ryan's SF thing I could help organize something in the Austin area if there is interest.
Would people like to do a Cassandra test-athon a week from Friday (December 10th)? That might give people some more time to finish up with remaining bug fixes of known bugs. Also hopefully counters would be worked out and committed by then. So node movement. What about bootstrapping in a cluster (various scenarios)? How about random partitioner specific tests (which were started a while back)? Or maybe doing a bunch of tests with online schema changes? How about making these tests repeatable in the integration tests - are multiple-node tests on a single machine feasible or is that better suited for manual running of scripts not as part of the build? On Dec 1, 2010, at 11:30 PM, Jonathan Ellis <jbel...@gmail.com> wrote: > It will not surprise most people who have deployed Cassandra that > there are still dragons in the node movement code. That is the > primary place I would like to see more testing. > > On Wed, Dec 1, 2010 at 3:24 PM, Jeremy Hanna <jeremy.hanna1...@gmail.com> > wrote: >> I was wondering if there was a coordinated plan for testing the 0.7 release. >> I realize that testing is ultimately up to the individual team. However, >> with 0.7 there are a _lot_ of significant changes and I wondered if there >> was interest in coordinating efforts to do more extensive testing above and >> beyond the integration tests and things built into the source tree currently. >> >> I think https://issues.apache.org/jira/browse/CASSANDRA-874 is also relevant >> for furthering the integration tests. >> >> Any thoughts? > > > > -- > Jonathan Ellis > Project Chair, Apache Cassandra > co-founder of Riptano, the source for professional Cassandra support > http://riptano.com
