Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 4702C200CBC for ; Tue, 20 Jun 2017 18:20:27 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 3EA09160BE1; Tue, 20 Jun 2017 16:20:27 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 3908D160BD3 for ; Tue, 20 Jun 2017 18:20:26 +0200 (CEST) Received: (qmail 72982 invoked by uid 500); 20 Jun 2017 16:20:25 -0000 Mailing-List: contact dev-help@hbase.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@hbase.apache.org Delivered-To: mailing list dev@hbase.apache.org Received: (qmail 72970 invoked by uid 99); 20 Jun 2017 16:20:24 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd3-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 20 Jun 2017 16:20:24 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd3-us-west.apache.org (ASF Mail Server at spamd3-us-west.apache.org) with ESMTP id 7348019204D for ; Tue, 20 Jun 2017 16:20:24 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 2.481 X-Spam-Level: ** X-Spam-Status: No, score=2.481 tagged_above=-999 required=6.31 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.001, HTML_MESSAGE=2, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RCVD_IN_SORBS_SPAM=0.5, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=disabled Authentication-Results: spamd3-us-west.apache.org (amavisd-new); dkim=pass (2048-bit key) header.d=cloudera-com.20150623.gappssmtp.com Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd3-us-west.apache.org [10.40.0.10]) (amavisd-new, port 10024) with ESMTP id zoBFOr5CYSsi for ; Tue, 20 Jun 2017 16:20:22 +0000 (UTC) Received: from mail-qt0-f172.google.com (mail-qt0-f172.google.com [209.85.216.172]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTPS id 1C15860DB6 for ; Tue, 20 Jun 2017 16:20:09 +0000 (UTC) Received: by mail-qt0-f172.google.com with SMTP id u12so137555491qth.0 for ; Tue, 20 Jun 2017 09:20:09 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cloudera-com.20150623.gappssmtp.com; s=20150623; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to; bh=16g47nx3oP8KoLzKzwCOmxN/KB9iKpakQcBtRWaYca8=; b=C+hKnvKFmEaYXIhhopvXcTAL4R9i2eF34fik9UybsWBb6fv7TyCllL7bqGuJmYUux0 sC59OjXQsdHboUaK6BFQP9KWcdNrsK9h31HQgUJfio6cn7CuVhLo6Z0iikjq599/w4SR zPD3VUs2yGRlr+n1CyeD12quSvzyAFh9lBSGaiplS8a7JRMwTCuoe8jioUcEqlxnOpJI MNa8OoiqGDhc4tYFM5nnA5TE3x/vr9U7V6eC6u+rJ6otBzXpykFhlTcu/zn0MHCZgWe4 dLITiuoqyCmykQTUZUMMNBBCt2XZWCH4KmWUK0h/u5Y4XUhG4zBZjJY36wL6+/jqg+AG h3LA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to; bh=16g47nx3oP8KoLzKzwCOmxN/KB9iKpakQcBtRWaYca8=; b=VJnMWZTDOuVfhDvRADmCcCvsEYnQNeqw9xJlP//aYM0IgID5IIglfyRv90hmHcCywl 32/DL/2WanAhLh/DTI2GdNZw/D/OzN7n8c/fJ/Os5v6nfgC3DNfcPqovMHzvcYCnxSPW wT2HrDi0taQbHJIM3MTD5RVp/pfA1Vg6Kt0kGn1i0pTSSJI9KphtIFcmxVTXjPGlk7fr zC5yYDkH8FW6hiErL0Y9gj36/ZHOKU+6DltfTwUNhDAGK+GovSum4isqkK9YzXYvATTx wMQgsKPSrPjWiv4T8Mj5qysAVpwBRvycbX719gvugCJVgiM9E7BfU1y0IFauNXhjiWDq VHPw== X-Gm-Message-State: AKS2vOwuB0OpUGNYE52LMmFB184K016l+kBD9lhDTp+zNfmNPv7b2WjM v7pgVuwKGFb/kjeVND9aKSmici2rFBKAA+s= X-Received: by 10.200.50.145 with SMTP id z17mr496175qta.114.1497975607717; Tue, 20 Jun 2017 09:20:07 -0700 (PDT) MIME-Version: 1.0 Sender: mdrob@cloudera.com Received: by 10.237.59.247 with HTTP; Tue, 20 Jun 2017 09:19:47 -0700 (PDT) In-Reply-To: References: From: Mike Drob Date: Tue, 20 Jun 2017 11:19:47 -0500 X-Google-Sender-Auth: 0SAqBcQYQQR2rYKLpEZGKxXU4FU Message-ID: Subject: Re: [RESULT] [VOTE] First hbase-2.0.0-alpha-1 Release Candidate is available To: dev Content-Type: multipart/alternative; boundary="001a113c7720fb13f90552669f59" archived-at: Tue, 20 Jun 2017 16:20:27 -0000 --001a113c7720fb13f90552669f59 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Hi Stack, Can you mark jira version 2.0.0-alpha-1 as released? Thanks, Mike On Sat, Jun 10, 2017 at 10:55 PM, Stack wrote: > With 4 binding votes and 1 non-binding, vote passes. Let me push out the > alpha. > Thanks to all who voted. > St.Ack > > > On Sat, Jun 10, 2017 at 11:40 AM, Stack wrote: > > > Great. Thanks Sean. In-line... > > > > On Fri, Jun 9, 2017 at 11:35 PM, Sean Busbey wrote: > > > >> +1 > >> > >> details below, a few things to clean up for later alpha/betas. > >> > >> * checksums are all good > >> * signatures are made with two different keys. should clean up by next > >> alpha. > >> > >> src / bin artifacts are signed with 8ACC93D2, as you mentioned in the > >> VOTE. However, this key is not in our project's KEYS file. > >> > >> > > Yes. Will fix. > > > > > >> maven staged repository are signed with 30CD0996, which is in our KEYS > >> file so those check out fine. > >> > >> * the tag 2.0.0-alpha-1RC0 does point to > >> c830a0f47f58d4892dd3300032c8244d6278aecc, which matches the source > >> artifact after accounting HBASE-13088 > >> > >> The tag isn't signed; would be good to make sure we do tag signing in > >> betas so that it's ready to go come GA time. > >> > >> > > Next time through, I'll update our 'How to RC' doc and will add above. > > > > > > > >> (side note, it would be good to get a decision on HBASE-13088 for the > >> beta releases. been over 2 years) > >> > >> * the source tarball creates a binary assembly that looks as close to > >> the posted binary artifact as I've seen branch-1 do. > >> > >> idle interest, but our binary convenience artifact has jumped from > >> ~100MiB in branch-1 release to ~160MiB. If anyone has time to dig in > >> on why, probably worth checking. (e.g. the docs directory is ~585 MiB > >> when untared.) > >> > >> > > Yes. Its obnoxious (HBASE-18208). > > > > > >> * shaded artifact binaries are a reasonable number of MiB in size > >> (incorrect build flags will result in ~empty jars) > >> > >> * LICENSE/NOTICE spot check looks okay. > >> > >> we have a ton of places where we have velocity variables instead of > >> copyright years, but IIRC that's a problem on branch-1 right now too. > >> > >> * CHANGES file hasn't been updated correctly > >> > >> currently has details for 0.93. > >> > >> > > Will fix next time through. > > > > Thanks Sean, > > S > > > > > > > >> On Fri, Jun 9, 2017 at 12:06 PM, Andrew Purtell > >> wrote: > >> > +1 > >> > > >> > On Thu, Jun 8, 2017 at 12:33 AM, Stack wrote: > >> > > >> >> The first release candidate for HBase 2.0.0-alpha-1 is up at: > >> >> > >> >> https://dist.apache.org/repos/dist/dev/hbase/hbase-2.0.0- > alpha-1RC0/ > >> >> > >> >> Maven artifacts are available from a staging directory here: > >> >> > >> >> https://repository.apache.org/content/repositories/orgapache > >> hbase-1169 > >> >> > >> >> All was signed w/ my key 8ACC93D2 > >> >> > >> >> > >> >> I tagged the RC as 2.0.0-alpha-1RC0 > >> >> (c830a0f47f58d4892dd3300032c8244d6278aecc). > >> >> > >> >> hbase-2.0.0-alpha-1 will be our first 2.0.0 release. It is a rough > cut > >> >> ('alpha') not-for-production preview of what hbase-2.0.0 will look > >> like. It > >> >> is what we used to call a 'Developer' release[1] meant mostly for > devs > >> and > >> >> downstreamers to test drive and flag us early if we there are issue= s > >> we=E2=80=99ve > >> >> missed ahead of our rolling a production-worthy release. > >> >> > >> >> hbase-2.0.0 includes a fleet of new features that include a new > >> assignment > >> >> manager, means for keeping read and write path off-heap, in-memory > >> >> compactions, and more. I have been keeping a running doc on the sta= te > >> of > >> >> 2.0.0 here [2]. There is much to do still (see aforementioned doc). > >> >> > >> >> The list of features addressed in 2.0.0 so far can be found here [4= ]. > >> There > >> >> are about 2500. The list of ~500 fixes in 2.0.0 exclusively can be > >> found > >> >> here [3]. > >> >> > >> >> Please take it for a spin and vote on whether it ok to put out as o= ur > >> first > >> >> alpha (bar is low for an 'alpha'). Let the VOTE be open for 24 hour= s. > >> >> > >> >> Thanks, > >> >> St.Ack > >> >> > >> >> 1. http://hbase.apache.org/book.html#hbase.versioning.pre10 > >> >> 2. > >> >> https://docs.google.com/document/d/1WCsVlnHjJeKUcl7wHwqb4z9iEu_ > >> >> ktczrlKHK8N4SZzs/edit#heading=3Dh.v21r9nz8g01j > >> >> 3. > >> >> https://issues.apache.org/jira/browse/HBASE-17852?jql=3D > >> >> project%20%3D%20HBASE%20%20and%20fixVersion%20%3D%202. > >> >> 0.0%20and%20fixVersion%20not%20in%20(1.0.0%2C%201.0.1%2C% > >> >> 201.0.2%2C%201.0.3%2C%201.0.4%2C%201.0.5%2C%201.0.6%2C%201. > >> >> 1.0%2C%201.1.1%2C%201.1.2%2C%201.1.3%2C%201.1.4%2C%201.1.5% > >> >> 2C%201.1.6%2C%201.1.7%2C%201.1.8%2C%201.1.9%2C%201.1.10%2C% > >> >> 201.2.0%2C%201.2.1%2C%201.2.2%2C%201.2.3%2C%201.2.4%2C%201. > >> >> 2.5%2C%201.2.6%2C%201.3.0%2C%201.3.1%2C%201.4.0)%20and%20% > >> >> 20(status%20%3D%20Open%20or%20status%20%3D%20%22Patch% > 20Available%22) > >> >> 4. > >> >> https://issues.apache.org/jira/browse/HBASE-18191?jql=3D > >> >> project%20%3D%20HBASE%20%20and%20(%20fixVersion%20%3D% > >> >> 202.0.0)%20and%20(status%20%3D%20Resolved) > >> >> > >> > > >> > > >> > > >> > -- > >> > Best regards, > >> > > >> > - Andy > >> > > >> > If you are given a choice, you believe you have acted freely. - > Raymond > >> > Teller (via Peter Watts) > >> > > > > > --001a113c7720fb13f90552669f59--