+1
On Tue, Apr 3, 2012 at 10:21 AM, Sylvain Lebresne wrote:
> The first attempt was closed to include the fix for CASSANDRA-4112. After have
> committed said fix, I'm proposing the following artifacts for release as
> 1.0.9.
>
> sha1: 3fd0fb6aa0038f0c8aaf34f98f2ceed2f308a501
> Git:
> http://git
+1
3 apr 2012 kl. 22:38 skrev Jonathan Ellis :
> +1
>
> On Tue, Apr 3, 2012 at 10:21 AM, Sylvain Lebresne
> wrote:
>> The first attempt was closed to include the fix for CASSANDRA-4112. After
>> have
>> committed said fix, I'm proposing the following artifacts for release as
>> 1.0.9.
>>
>> s
+1
On Tue, Apr 3, 2012 at 10:21 AM, Sylvain Lebresne wrote:
> The first attempt was closed to include the fix for CASSANDRA-4112. After have
> committed said fix, I'm proposing the following artifacts for release as
> 1.0.9.
>
> sha1: 3fd0fb6aa0038f0c8aaf34f98f2ceed2f308a501
> Git:
> http://git
+1
--
Pavel Yaskevich
On Monday 2 April 2012 at 17:25, Jonathan Ellis wrote:
> +1
>
> On Mon, Apr 2, 2012 at 8:33 AM, Sylvain Lebresne (mailto:sylv...@datastax.com)> wrote:
> > 1.0.8 has been release more than a month ago, we made quite a few bug fixes
> > and don't have any major outstandi
+1
On Mon, Apr 2, 2012 at 8:33 AM, Sylvain Lebresne wrote:
> 1.0.8 has been release more than a month ago, we made quite a few bug fixes
> and don't have any major outstanding issue open. I thus propose the following
> artifacts for release as 1.0.9.
>
> sha1: 4457839b9da623d9d4a090fa444614c35d39
