+1 (non-binding)

Built and ran tests

On Mon, Jun 12, 2017 at 9:49 AM, Jean-Daniel Cryans <[email protected]> wrote:
> Err sorry I meant to vote on Friday but then Happy Hour happened :)
>
> +1, ran the same verifications as for RC1.
>
> FWIW one of my test clusters hit the issue that killed RC1 after I had
> voted for it, so I'm glad we caught it.
>
> J-D
>
> On Mon, Jun 12, 2017 at 12:38 AM, Todd Lipcon <[email protected]> wrote:
>
>> Hmm, no votes so far? Let's extend the vote to tomorrow night (I guess it
>> wasn't so nice to have most of the voting period fall on a weekend). I'll
>> try to vote myself tomorrow as well.
>>
>> -Todd
>>
>> On Thu, Jun 8, 2017 at 7:15 PM, Todd Lipcon <[email protected]> wrote:
>>
>> > Hi,
>> >
>> > The Apache Kudu team is happy to announce the first release candidate for
>> > Apache Kudu 1.4.0.
>> >
>> > Apache Kudu 1.4.0 is a minor release which offers many improvements and
>> > fixes since the prior release. This second release candidate includes the
>> > release notes as well as two bug fixes for issues discovered during the
>> RC1
>> > voting period.
>> >
>> > The is a source-only release. The artifacts were staged here:
>> > https://dist.apache.org/repos/dist/dev/kudu/1.4.0-RC2
>> >
>> > Java convenience binaries in the form of a Maven repository are staged
>> > here:
>> > https://repository.apache.org/content/repositories/orgapachekudu-1010/
>> > (note that the Java artifacts did not change since the prior RC, so this
>> > is the same staged repository)
>> >
>> > It was built from this tag:
>> > https://git-wip-us.apache.org/repos/asf?p=kudu.git;a=commit;h=
>> > 1ed03d710ebf06afa35ee0f7813649d661f90829
>> >
>> > KEYS file:
>> > http://www.apache.org/dist/kudu/KEYS
>> >
>> > I'd suggest going through the README, building Kudu, and running the
>> > unit tests. Testing out the Maven repo would also be appreciated.
>> >
>> > The vote will run until Sunday, June 8th at 7PM PDT.
>> >
>> > Thanks,
>> > Todd
>> >
>>
>>
>>
>> --
>> Todd Lipcon
>> Software Engineer, Cloudera
>>

Reply via email to