On Tue, Jul 1, 2014 at 8:16 PM, Jonathan Ellis wrote:
> Yes, and I'd even lean towards taking 1.2.17 down until that's fixed.
>
I'd prefer doing a quick re-roll of 1.2.18 (which I'll start shortly) and
simply sending a small warning email to the user list (which I'll do) but
leaving 1.2.17 be un
Yes, and I'd even lean towards taking 1.2.17 down until that's fixed.
On Tue, Jul 1, 2014 at 1:09 PM, Michael Shuler wrote:
> It seems a bit of a flaw in our test builds allowed us to miss a problem
> with this release. Cassandra 1.2.x is intended to remain java_1.6
> compatible, to the best of m
It seems a bit of a flaw in our test builds allowed us to miss a problem
with this release. Cassandra 1.2.x is intended to remain java_1.6
compatible, to the best of my knowledge. Unfortunately, CASSANDRA-7147
includes a bit of code that breaks the build when using Oracle JDK 1.6.
Should this
Including my own, I count 4 binding +1 and no -1's. The vote passes, I'll
get the artifacts published shortly.
On Thu, Jun 26, 2014 at 6:59 PM, Gary Dusbabek wrote:
> +1
>
>
> On Wed, Jun 25, 2014 at 12:06 PM, Sylvain Lebresne
> wrote:
>
> > I propose the following artifacts for release as 1.2
