From dev-return-71174-archive-asf-public=cust-asf.ponee.io@hbase.apache.org Mon Oct 8 17:19:54 2018 Return-Path: X-Original-To: archive-asf-public@cust-asf.ponee.io Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by mx-eu-01.ponee.io (Postfix) with SMTP id C10C8180652 for ; Mon, 8 Oct 2018 17:19:53 +0200 (CEST) Received: (qmail 88178 invoked by uid 500); 8 Oct 2018 15:19:52 -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 88167 invoked by uid 99); 8 Oct 2018 15:19:52 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd4-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 08 Oct 2018 15:19:51 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd4-us-west.apache.org (ASF Mail Server at spamd4-us-west.apache.org) with ESMTP id 9617DC032A for ; Mon, 8 Oct 2018 15:19:51 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd4-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 1.999 X-Spam-Level: * X-Spam-Status: No, score=1.999 tagged_above=-999 required=6.31 tests=[HEADER_FROM_DIFFERENT_DOMAINS=0.001, HTML_MESSAGE=2, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001] autolearn=disabled Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd4-us-west.apache.org [10.40.0.11]) (amavisd-new, port 10024) with ESMTP id 6jtra-naYlOW for ; Mon, 8 Oct 2018 15:19:50 +0000 (UTC) Received: from mail-it1-f171.google.com (mail-it1-f171.google.com [209.85.166.171]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTPS id 1AC7F5F39E for ; Mon, 8 Oct 2018 15:19:50 +0000 (UTC) Received: by mail-it1-f171.google.com with SMTP id l191-v6so11937709ita.4 for ; Mon, 08 Oct 2018 08:19:50 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to; bh=VOs6DIYhaqHhGdIsaWD3OF4QJ+LOdEf97iCzPAsASYc=; b=IxSqNdEfiUNPBWyrWMspKwjHjJbj+l149r/bwV3OchT8hdLlgihKOnDbg9hEUvVsLx usgXahf3bEWosc/Ng5OC5KzpRGjTXRDlE71U2Ejq03xHbjB18UUzO6NgI161vM33Lly0 c/dE+mjqqFKiNTXJfXj3KNLp/jy8AnqEIfklIBU+xSAYZTvaHD7xEpYedfl27CewHCCx gpYC1FpBJ8oEevJ6LqZ3hZhxzjt9TuAYtPe5ngDJgxmv3dhXC8spbcLFz40RBjPx/kFw dWCIsn6JRyR5NmW24J/qmrmw8Ps8XRa1B9axOsJAhuztBGcOwbuirJkGcbYAApW/hl2i y6/Q== X-Gm-Message-State: ABuFfojpMjACmjcV3cah8DCmgJxu34ebWW6DK/A1PlemvbBputiitaKB 0I9zvUzh1wpdfQUtBjmpsDWaT7Iusy+khHiNcVVOn4MuXXQ= X-Google-Smtp-Source: ACcGV62QsSz/wAeHsnC9iivr6zKRzI7rtxUv1J9WypxJhaepbNsU5BLdanJp0axvbvV4eRjxaoSootiNmA8DKeytbhU= X-Received: by 2002:a02:4f89:: with SMTP id r9-v6mr19594235jad.6.1539011989086; Mon, 08 Oct 2018 08:19:49 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Mike Drob Date: Mon, 8 Oct 2018 10:19:38 -0500 Message-ID: Subject: Re: [DISCUSS] 2.1.1 Release Plans? To: dev Content-Type: multipart/alternative; boundary="000000000000ea72770577b9268b" --000000000000ea72770577b9268b Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Thanks for pointing me to that discussion, Duo. I've updated HBASE-19121 to have fix version 2.1.1 and 2.0.3 so that it is easier (at least for me) to find via Jira. I'll start looking at the hbck2 patches and will leave comments there. There are a lot of subtasks against that issue, it is unclear to me which ones are critical and which ones are not for a release. Since hbck2 tool is in a different repo, have we thought about what the release actions would look like? Do we need to have two votes going at the same time? Can we release core repo with an hbck service in master, but release the hbck tool sometime later? This first release is going to be more complex I think; would be good if somebody can figure that out in parallel so we're not blocked on it later. Mike On Fri, Oct 5, 2018 at 6:41 PM =E5=BC=A0=E9=93=8E(Duo Zhang) wrote: > Stack has a plan on the 2.1.1 release where we want to finish the first > version on hbck2. In the real deploy we have met a stuck cluster several > times, and lots of users have asked that why hbck can not work any more..= . > > So the current opening issue is not important, please help reviewing the > patches for hbck2 to speed up the release... > > Thanks for bringing this up > > Mike Drob =E4=BA=8E2018=E5=B9=B410=E6=9C=885=E6=97=A5 = =E5=91=A8=E4=BA=9423:53=E5=86=99=E9=81=93=EF=BC=9A > > > Devs, > > > > It's been almost 3 months since 2.1.0 was released (Jul 19) and we have > 150 > > commits on branch-2.1 in that time. What do folks think of getting a > > release going? I know that there's been some discussion around the HBCK= 2 > > stuff landing, but I feel like the conversation has gotten a bit lost > > without an actual release to relate to. > > > > Duo, as the 2.1.0 release manager, are you interested in maintaining th= e > > 2.1 branch release cadence? If you've gotten busy, then let's find > another > > volunteer. > > > > There are 18 issues open or in progress currently. Only one is labelled > > blocker, and five more are critical -- let's evaluate these and the res= t > to > > figure out what we need for a release to happen. I went ahead and > created a > > 2.1.2 version in Jira so that we have somewhere to move issues that > aren't > > getting done soon. > > > > Meanwhile, I think we also need to look at test stabilization -- there'= s > 15 > > tests on the dashboard that might need attention. > > > > Mike > > > --000000000000ea72770577b9268b--