Re: [VOTE] Release Apache Cassandra 1.0.0 (Final) - Strike 2

2011-10-11 Thread Sylvain Lebresne
The artifacts for this vote happen to have https://issues.apache.org/jira/browse/CASSANDRA-3343. This is a purely cosmetic issue, and clearly I don't want to reroll the vote for this, which would delay the release. But I also think that fixing this issue has zero chance of screwing anything up,

Re: [VOTE] Release Apache Cassandra 1.0.0 (Final) - Strike 2

2011-10-11 Thread Brandon Williams
On Tue, Oct 11, 2011 at 8:29 AM, Sylvain Lebresne sylv...@datastax.com wrote: So I have created new artifacts, based on the previous ones but with the infamous 'echo $CLASSPATH' removed from cassandra.in.sh. And what I'm proposing is to simply switch to those last artifacts for the release

Re: [VOTE] Release Apache Cassandra 1.0.0 (Final) - Strike 2

2011-10-11 Thread Jonathan Ellis
+1 On Tue, Oct 11, 2011 at 8:32 AM, Brandon Williams dri...@gmail.com wrote: On Tue, Oct 11, 2011 at 8:29 AM, Sylvain Lebresne sylv...@datastax.com wrote: So I have created new artifacts, based on the previous ones but with the infamous 'echo $CLASSPATH' removed from cassandra.in.sh. And

Re: [VOTE] Release Apache Cassandra 1.0.0 (Final) - Strike 2

2011-10-11 Thread Brandon Williams
On Mon, Oct 10, 2011 at 11:24 AM, Sylvain Lebresne sylv...@datastax.com wrote: As said while closing previous vote, CASSANDRA-3338 felt important enough to warrant a reroll. So here it is: I propose the following artifacts for release as 1.0.0 (those are the same as the previous + the patch for

[VOTE] Release Apache Cassandra 1.0.0 (Final) - Strike 2

2011-10-10 Thread Sylvain Lebresne
As said while closing previous vote, CASSANDRA-3338 felt important enough to warrant a reroll. So here it is: I propose the following artifacts for release as 1.0.0 (those are the same as the previous + the patch for CASSANDRA-3338 and a one line fix to the build file so that it picks the right

Re: [VOTE] Release Apache Cassandra 1.0.0 (Final) - Strike 2

2011-10-10 Thread Stephen Connolly
+1 (non-binding) -Stephen On 10 October 2011 17:24, Sylvain Lebresne sylv...@datastax.com wrote: As said while closing previous vote, CASSANDRA-3338 felt important enough to warrant a reroll. So here it is: I propose the following artifacts for release as 1.0.0 (those are the same as the

Re: [VOTE] Release Apache Cassandra 1.0.0 (Final) - Strike 2

2011-10-10 Thread Eric Evans
On Mon, Oct 10, 2011 at 11:24 AM, Sylvain Lebresne sylv...@datastax.com wrote: As said while closing previous vote, CASSANDRA-3338 felt important enough to warrant a reroll. So here it is: I propose the following artifacts for release as 1.0.0 (those are the same as the previous + the patch for

Re: [VOTE] Release Apache Cassandra 1.0.0 (Final) - Strike 2

2011-10-10 Thread Jake Luciani
+1 On Mon, Oct 10, 2011 at 12:24 PM, Sylvain Lebresne sylv...@datastax.comwrote: As said while closing previous vote, CASSANDRA-3338 felt important enough to warrant a reroll. So here it is: I propose the following artifacts for release as 1.0.0 (those are the same as the previous + the

Re: [VOTE] Release Apache Cassandra 1.0.0 (Final) - Strike 2

2011-10-10 Thread Todd Burruss
This is a bit preliminary, but wanted to get this to you guys knowing the vote is in progress using these artifacts I am seeing the following exception on restart. (also with RC1 and RC2.) the only interesting tidbit is that it seems to only happen when writing via direct calls to