Thanks for voting, all! Seems we have 6 binding +1 votes and 3 non-binding +1s.
I'll work on publishing the release tomorrow morning and send an announcement the following day. Todd On Jun 12, 2017 11:06 PM, "Alexey Serbin" <[email protected]> wrote: +1 Checked out the source code from the branch-1.4.x branch, built (DEBUG configuration) and ran tests with 'ctest -j4' on ProductName: Mac OS X ProductVersion: 10.11.6 BuildVersion: 15G1421 All tests passed. Kind regards, Alexey On 6/12/17 5:11 PM, Andrew Wong wrote: > +1 (non-binding) > > Built and ran tests in release/debug modes with macOS 10.12. > > On Mon, Jun 12, 2017 at 4:21 PM, Todd Lipcon <[email protected]> wrote: > > +1 >> >> Built RELEASE on Centos 7.3, and ran tpch_real_world import with hash >> partitioning for scale factor 300 (~1.8B rows inserted) on one node with a >> fairly tight memory limit. It took ~26m. >> >> I also ran the same test in an ASAN build for a few minutes (inserted ~35M >> rows) but the sanitized build is pretty slow so I didn't let it run to >> completion. >> >> -Todd >> >> On Mon, Jun 12, 2017 at 3:43 PM, Adar Dembo <[email protected]> wrote: >> >> +1 >>> >>> Built TSAN and ran tests on Ubuntu 16.04. >>> >>> >>> On Mon, Jun 12, 2017 at 2:51 PM, Dan Burkert <[email protected]> >>> wrote: >>> >>>> +1 >>>> >>>> Built and ran tests on OS X 10.10. >>>> >>>> - Dan >>>> >>>> On Mon, Jun 12, 2017 at 9:49 AM, Brock Noland <[email protected]> wrote: >>>> >>>> +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 >>>>>>> >>>>>>> >> >> -- >> Todd Lipcon >> Software Engineer, Cloudera >> >> > >
