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 E6C23200BB6 for ; Fri, 4 Nov 2016 17:24:35 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id E5839160B04; Fri, 4 Nov 2016 16:24:35 +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 5F1FD160AEA for ; Fri, 4 Nov 2016 17:24:35 +0100 (CET) Received: (qmail 77959 invoked by uid 500); 4 Nov 2016 16:24:33 -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 77933 invoked by uid 99); 4 Nov 2016 16:24:33 -0000 Received: from mail-relay.apache.org (HELO mail-relay.apache.org) (140.211.11.15) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 04 Nov 2016 16:24:33 +0000 Received: from mail-wm0-f53.google.com (mail-wm0-f53.google.com [74.125.82.53]) by mail-relay.apache.org (ASF Mail Server at mail-relay.apache.org) with ESMTPSA id 131171A0046; Fri, 4 Nov 2016 16:24:33 +0000 (UTC) Received: by mail-wm0-f53.google.com with SMTP id a197so61473397wmd.0; Fri, 04 Nov 2016 09:24:32 -0700 (PDT) X-Gm-Message-State: ABUngvdGoNZcYuTC0X4MFe4gNPrs8bkbDfzJrNsLYHaqaXE3Eccd2luBHbaWLseiKC8iPSnMsUv7aChUwp3XPg== X-Received: by 10.194.201.227 with SMTP id kd3mr15778124wjc.74.1478276671679; Fri, 04 Nov 2016 09:24:31 -0700 (PDT) MIME-Version: 1.0 Received: by 10.28.169.7 with HTTP; Fri, 4 Nov 2016 09:24:30 -0700 (PDT) From: Nick Dimiduk Date: Fri, 4 Nov 2016 09:24:30 -0700 X-Gmail-Original-Message-ID: Message-ID: Subject: [DISCUSS] EOL 1.1 Release Branch To: hbase-user , hbase-dev Content-Type: multipart/alternative; boundary=047d7bae4242e53ec805407c1bee archived-at: Fri, 04 Nov 2016 16:24:36 -0000 --047d7bae4242e53ec805407c1bee Content-Type: text/plain; charset=UTF-8 Hello HBase Community! We have a small matter to discuss. HBase 1.2 has been formally marked as "stable" for the last couple months. HBase 1.3.0rc0 is just around the corner. I think it's time to start a conversation about retiring the 1.1 line. The volunteer bandwidth for maintaining multiple branches is precious and as we spread ourselves more thin, odds of decay increase. I propose discontinuing 1.1 with a single release following 1.3.1. That'll give us one last chance to back port any bug fixes discovered in the diligence we're putting into the new minor release. Given the current pace of 1.3, I estimate this will happen in January or February of 2017. It's not a lot of time for existing deployments to get around to upgrading, but the upgrade path is trivial and 1.2 has been available for quite some time. This will probably make our last release from this branch at 1.1.10 or there abouts. Are there any objections or concerns with the above plan? Are there any downstream communities who need our help moving onto 1.2? Please let us know. Thanks, Nick --047d7bae4242e53ec805407c1bee--