It's probably too late to vote, but -1 because of CASSANDRA-6739 and
CASSANDRA-6741
-M
On 2/17/14, 9:23, Sylvain Lebresne wrote:
Cassandra 2.1 is coming along but we now need wider testing. So I propose
the
following artifacts for release as 2.1.0-beta1. Let it be clear that it is
only
a beta
+1
On Mon, Feb 17, 2014 at 11:23 AM, Sylvain Lebresne wrote:
> Cassandra 2.1 is coming along but we now need wider testing. So I propose
> the
> following artifacts for release as 2.1.0-beta1. Let it be clear that it is
> only
> a beta (and the first one at that), so we know it's not perfect, bu
+1
On Mon, Feb 17, 2014 at 9:37 PM, Brandon Williams wrote:
> +1
>
>
> On Mon, Feb 17, 2014 at 11:23 AM, Sylvain Lebresne >wrote:
>
> > Cassandra 2.1 is coming along but we now need wider testing. So I propose
> > the
> > following artifacts for release as 2.1.0-beta1. Let it be clear that it
+1
On Mon, Feb 17, 2014 at 11:23 AM, Sylvain Lebresne wrote:
> Cassandra 2.1 is coming along but we now need wider testing. So I propose
> the
> following artifacts for release as 2.1.0-beta1. Let it be clear that it is
> only
> a beta (and the first one at that), so we know it's not perfect, bu
+1
On Mon, Feb 17, 2014 at 11:23 AM, Sylvain Lebresne wrote:
> Cassandra 2.1 is coming along but we now need wider testing. So I propose
> the
> following artifacts for release as 2.1.0-beta1. Let it be clear that it is
> only
> a beta (and the first one at that), so we know it's not perfect, but
Cassandra 2.1 is coming along but we now need wider testing. So I propose
the
following artifacts for release as 2.1.0-beta1. Let it be clear that it is
only
a beta (and the first one at that), so we know it's not perfect, but the
current goal is first and foremost to get wider testing.
sha1: 73dc
