The vote passes with 7 binding +1s:
- Adar Dembo
- William Berkeley
- David Alves
- Mike Percy
- Jean-Daniel Cryans
- Alexey Serbin
- Todd Lipcon
and one non-binding: Dinesh Bhat
Thanks for voting, everyone! I'll take care of the release mechanics
tomorrow. Since the mirrors take some time to propagate, the actual
announcement should probably go out Monday.
On Thu, Sep 15, 2016 at 11:59 PM, Todd Lipcon <t...@cloudera.com> wrote:
> +1 (binding)
> - built tag on el6 with devtoolset
> - did some stress testing of this build using a single-node YCSB
> - spent quite a bit of time the last couple of days (along with some other
> committers) looking at flaky tests, and haven't turned up anything that
> looks like a regression.
> Separately, I deployed a 5-node cluster a week and a half ago with the
> riskiest features which were in-flight at the time (log GC and a consensus
> refactor) and ran the cluster for about a week with YCSB running
> concurrently with updates/deletes/inserts/scans driven from Impala, and it
> ran like a champ. I had a machine die during this test and didn't notice
> until a day or two later, which is a good sign. This test wasn't run
> exactly on the release tag itself, but it gives me pretty good confidence
> in the release's stability, which helps inform my vote.
> On Thu, Sep 15, 2016 at 7:48 PM, Dinesh Bhat <din...@cloudera.com> wrote:
>> Compiled tarball on Centos66, ran tests in parallel(dist_test).
>> 1 test failed(still debugging to confirm if it’s flaky or not), but
>> doesn’t seem like regression.
>> Also spun a kudu cluster with 1 master + 4 tserver nodes using CM/CSD
>> parcels built from
>> equivalent binaries(thanks JD).
>> From CM tested:
>> - table creation
>> - data injection
>> - leader/follower failures
>> All tests passed.
>> > On Sep 13, 2016, at 12:39 AM, Todd Lipcon <t...@apache.org> wrote:
>> > Hi,
>> > The Apache Kudu team is happy to announce the first release candidate
>> > Apache Kudu 1.0.0.
>> > After approximately a year of beta releases, Apache Kudu has reached
>> > version 1.0.
>> > This version number signifies that the development team feels that Kudu
>> > stable
>> > enough for usage in production environments.
>> > The is a source-only release. The artifacts were staged here:
>> > https://dist.apache.org/repos/dist/dev/kudu/1.0.0-RC1/
>> > Java convenience binaries in the form of a Maven repository are staged
>> > https://repository.apache.org/content/repositories/orgapachekudu-1001/
>> > It was built from this tag:
>> > https://git-wip-us.apache.org/repos/asf?p=kudu.git;a=commit;
>> > The release notes can be found here (some links from this document will
>> > only work when this version is released):
>> > https://github.com/apache/kudu/blob/branch-1.0.x/docs/releas
>> > 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.
>> > Please try the release and vote; the vote will end in 72 hours (on
>> > 9/16/2016 at 12:30am PDT).
>> > Thanks,
>> > Todd
> Todd Lipcon
> Software Engineer, Cloudera
Software Engineer, Cloudera