Counting my own I count 5 binding +1, 1 other +1 and no -1's, the vote
passes.
I'lll get the artifacts published soonish.
--
Sylvain
On Tue, Dec 11, 2012 at 8:41 PM, Gary Dusbabek wrote:
> +1
>
>
> On Tue, Dec 11, 2012 at 5:19 AM, Sylvain Lebresne >wrote:
>
> > We've now fixed all remaining b
+1
On Tue, Dec 11, 2012 at 5:19 AM, Sylvain Lebresne wrote:
> We've now fixed all remaining blocking problems on the 1.2.0 branch since
> beta3, and if we want to release the final before the end of the year it's
> time
> to get serious, so I propose the following artifacts for release as
> 1.2.
+1
On Tue, Dec 11, 2012 at 11:42 AM, Pavel Yaskevich wrote:
> +1
>
> On Tuesday, December 11, 2012 at 8:28 AM, Yuki Morishita wrote:
>
>> +1
>>
>> yuki
>>
>>
>> On Tuesday, December 11, 2012 at 7:27 AM, Jonathan Ellis wrote:
>>
>> > +1
>> > On Dec 11, 2012 5:19 AM, "Sylvain Lebresne" > > (mailto:
+1
On Tuesday, December 11, 2012 at 8:28 AM, Yuki Morishita wrote:
> +1
>
> yuki
>
>
> On Tuesday, December 11, 2012 at 7:27 AM, Jonathan Ellis wrote:
>
> > +1
> > On Dec 11, 2012 5:19 AM, "Sylvain Lebresne" > (mailto:sylv...@datastax.com)> wrote:
> >
> > > We've now fixed all remaining bl
+1
yuki
On Tuesday, December 11, 2012 at 7:27 AM, Jonathan Ellis wrote:
> +1
> On Dec 11, 2012 5:19 AM, "Sylvain Lebresne" (mailto:sylv...@datastax.com)> wrote:
>
> > We've now fixed all remaining blocking problems on the 1.2.0 branch since
> > beta3, and if we want to release the final befo
+1
On Dec 11, 2012 5:19 AM, "Sylvain Lebresne" wrote:
> We've now fixed all remaining blocking problems on the 1.2.0 branch since
> beta3, and if we want to release the final before the end of the year it's
> time
> to get serious, so I propose the following artifacts for release as
> 1.2.0-rc1.
We've now fixed all remaining blocking problems on the 1.2.0 branch since
beta3, and if we want to release the final before the end of the year it's
time
to get serious, so I propose the following artifacts for release as
1.2.0-rc1.
sha1: d791e0b3fa5a615f2df200ecd40f82dc9a5874d6
Git:
http://git-wi
On Sun, Dec 2, 2012 at 10:45 PM, Jonathan Ellis wrote:
> I'm not a fan of blocking a new rc because of bugs that are not
> regressions new in that release. I'd also like to get more testing on
> the 1.2 fixes since b2. But we can call it b3 instead of rc1 if you
> want.
I agree with everything
I'm not a fan of blocking a new rc because of bugs that are not
regressions new in that release. I'd also like to get more testing on
the 1.2 fixes since b2. But we can call it b3 instead of rc1 if you
want.
On Mon, Dec 3, 2012 at 1:19 PM, Brandon Williams wrote:
> On Fri, Nov 30, 2012 at 4:17
On Fri, Nov 30, 2012 at 4:17 AM, Sylvain Lebresne wrote:
> We've fixed pretty much all know issues since beta2 (remains 2 issues tagged
> 1.2.0 but none are really critical if they don't make it anyway) so so I
> propose the following artifacts for release as 1.2.0-rc1.
I think we should solve CA
+1
Regards,
On Fri, Nov 30, 2012 at 2:17 AM, Sylvain Lebresne wrote:
> We've fixed pretty much all know issues since beta2 (remains 2 issues
> tagged
> 1.2.0 but none are really critical if they don't make it anyway) so so I
> propose the following artifacts for release as 1.2.0-rc1.
>
> sha1
+1
On Fri, Nov 30, 2012 at 7:17 PM, Sylvain Lebresne wrote:
> We've fixed pretty much all know issues since beta2 (remains 2 issues tagged
> 1.2.0 but none are really critical if they don't make it anyway) so so I
> propose the following artifacts for release as 1.2.0-rc1.
>
> sha1: 2f187c92033b5
We've fixed pretty much all know issues since beta2 (remains 2 issues tagged
1.2.0 but none are really critical if they don't make it anyway) so so I
propose the following artifacts for release as 1.2.0-rc1.
sha1: 2f187c92033b5b3f689d75375308dbf4dbac515f
Git:
http://git-wip-us.apache.org/repos/asf
13 matches
Mail list logo
