Return-Path: X-Original-To: apmail-hive-dev-archive@www.apache.org Delivered-To: apmail-hive-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 409BB10FC1 for ; Wed, 27 May 2015 01:13:58 +0000 (UTC) Received: (qmail 74260 invoked by uid 500); 27 May 2015 01:13:48 -0000 Delivered-To: apmail-hive-dev-archive@hive.apache.org Received: (qmail 74175 invoked by uid 500); 27 May 2015 01:13:48 -0000 Mailing-List: contact dev-help@hive.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@hive.apache.org Delivered-To: mailing list dev@hive.apache.org Received: (qmail 74162 invoked by uid 99); 27 May 2015 01:13:48 -0000 Received: from Unknown (HELO spamd3-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 27 May 2015 01:13:48 +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 AA87518275B for ; Wed, 27 May 2015 01:13:47 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -0.102 X-Spam-Level: X-Spam-Status: No, score=-0.102 tagged_above=-999 required=6.31 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001] autolearn=disabled Authentication-Results: spamd3-us-west.apache.org (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com Received: from mx1-us-east.apache.org ([10.40.0.8]) by localhost (spamd3-us-west.apache.org [10.40.0.10]) (amavisd-new, port 10024) with ESMTP id sDHTU_orT6CX for ; Wed, 27 May 2015 01:13:47 +0000 (UTC) Received: from mail-qg0-f46.google.com (mail-qg0-f46.google.com [209.85.192.46]) by mx1-us-east.apache.org (ASF Mail Server at mx1-us-east.apache.org) with ESMTPS id B9CB543CCD for ; Wed, 27 May 2015 01:13:46 +0000 (UTC) Received: by qgg60 with SMTP id 60so20367160qgg.2 for ; Tue, 26 May 2015 18:13:40 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=XM8UPj8m5TYwYGccVsCpaDw3cqUNcZaKpHrSz+m392g=; b=HFDclI1Lh06zxmH+ED/aHCewzQZtsxlAUijcIfmdq22ntEjWdpU+iQfjU6EIFzH2H+ 5BLKOqpNuOCFWF/AgvBctaX60NDdMiRwz/2LzWiNA66jDnPLcjDRUNv0Sux38ruNOFQS 1/hmqrIujpXLt9Ax8GPkJDN4uHi/bgaV8KREKmvpnTgXr0WX94FvGs822hbn0/UGpfIk 20k4lY/HH6t72WABZK+VG8rsIBaCLm8awc2SdN+zWVc2E4Hm5a6D2Pp1pXzqZotc3fzI PTt9CQEgjwxF8vWE/nqQ9tFyVBYFF1b/I6/VFs0MhUPU0w8AZc6JYAt7eqCPeZ/Bt4P7 l/CQ== MIME-Version: 1.0 X-Received: by 10.140.145.88 with SMTP id 85mr39194770qhr.39.1432689220489; Tue, 26 May 2015 18:13:40 -0700 (PDT) Received: by 10.140.93.45 with HTTP; Tue, 26 May 2015 18:13:40 -0700 (PDT) In-Reply-To: <5564BE3E.4060407@gmail.com> References: <5564BE3E.4060407@gmail.com> Date: Tue, 26 May 2015 18:13:40 -0700 Message-ID: Subject: Re: [VOTE] Stable releases from branch-1 and experimental releases from master From: Thejas Nair To: dev Content-Type: text/plain; charset=UTF-8 +1 - This is great for users who want to take longer to upgrade from hadoop-1 and care mainly for bug fixes and incremental features, rather than radical new features. - The ability to release initial 2.x releases marked as alpha/beta also helps to get users to try it out, and also lets them choose what is right for them. - This also lets developers focus on major new features without the burden of maintaining hadoop-1 compatibility. On Tue, May 26, 2015 at 11:41 AM, Alan Gates wrote: > We have discussed this for several weeks now. Some concerns have been > raised which I have tried to address. I think it is time to vote on it as > our release plan. To be specific, I propose: > > Hive makes a branch-1 from the current master. This would be used for 1.3 > and future 1.x releases. This branch would not deprecate existing > functionality. Any new features in this branch would also need to be put on > master. An upgrade path for users will be maintained from one 1.x release > to the next, as well as from the latest 1.x release to the latest 2.x > release. > > Going forward releases numbered 2.x will be made from master. The purpose > of these releases will be to enable users to get access to new features > being developed in Hive and allow developers to get feedback. It is > expected that for a while these releases will not be production ready and > will be clearly so labeled. Some legacy features, such as Hadoop 1 and > MapReduce, will no longer be supported in the master. Any critical bug > fixes (security, incorrect results, crashes) fixed in master will also be > ported to branch-1 for at least a year. This time period may be extended in > the future based on the stability and adoption of 2.x releases. > > Based on Hive's bylaws this release plan vote will be open for 3 days and > all active committers have binding votes. > > Here's my +1. > > Alan.