Return-Path: Delivered-To: apmail-hadoop-general-archive@minotaur.apache.org Received: (qmail 70488 invoked from network); 23 Dec 2010 00:33:49 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 23 Dec 2010 00:33:49 -0000 Received: (qmail 72453 invoked by uid 500); 23 Dec 2010 00:33:48 -0000 Delivered-To: apmail-hadoop-general-archive@hadoop.apache.org Received: (qmail 72328 invoked by uid 500); 23 Dec 2010 00:33:47 -0000 Mailing-List: contact general-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: general@hadoop.apache.org Delivered-To: mailing list general@hadoop.apache.org Received: (qmail 72320 invoked by uid 99); 23 Dec 2010 00:33:47 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 23 Dec 2010 00:33:47 +0000 X-ASF-Spam-Status: No, hits=-0.7 required=10.0 tests=FREEMAIL_FROM,RCVD_IN_DNSWL_LOW,SPF_PASS,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of saint.ack@gmail.com designates 209.85.161.48 as permitted sender) Received: from [209.85.161.48] (HELO mail-fx0-f48.google.com) (209.85.161.48) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 23 Dec 2010 00:33:43 +0000 Received: by fxm2 with SMTP id 2so5669196fxm.35 for ; Wed, 22 Dec 2010 16:33:22 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:sender:received :in-reply-to:references:date:x-google-sender-auth:message-id:subject :from:to:content-type; bh=0jAw9WC0GYgza4DcxR4FttGwrZSFQ5VlY83PjD/nWnQ=; b=fw8IOAyjOQfeGwumItExNrNv364p3ktY5d0x/8fH+Dv2UglOiBK/ry/5lqpMlaUsws MpdR5Gpl5CzaLflpgHUkHuYs/QoQYWelpvKxchOYOFWfCfFR/LWQ2/n14W8INTEe4+Ev roaNGH63sMm5hAw8J+Gny/DuLzr1msD3f9Wj4= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:content-type; b=ir4bNJVfSQImb+lI+iJGKTRlabBZcAIE3G/hYc4ZtWAiCQBrMWn9r5DrXkxtgCQtLb DhPXMiQdMWUFwpt3OGHoM0MOPAPY/mQski1n8QNdDamQV/iOpm5whS41RBySJXuoeVyj ZyODA6I4HbtkefwZ9GCMhxbvBijiEc0qlEYyI= MIME-Version: 1.0 Received: by 10.223.122.146 with SMTP id l18mr3308711far.67.1293064402188; Wed, 22 Dec 2010 16:33:22 -0800 (PST) Sender: saint.ack@gmail.com Received: by 10.223.83.9 with HTTP; Wed, 22 Dec 2010 16:33:22 -0800 (PST) In-Reply-To: <7277DB0B-9B56-4B57-A574-F2764C11FC10@Holsman.NET> References: <7277DB0B-9B56-4B57-A574-F2764C11FC10@Holsman.NET> Date: Wed, 22 Dec 2010 16:33:22 -0800 X-Google-Sender-Auth: 5bY_mIY4tdPi9UYF3RmdTPjIqMc Message-ID: Subject: Re: DISCUSSION: Cut a hadoop-0.20.0-append release from the tip of branch-0.20-append branch? From: Stack To: general@hadoop.apache.org Content-Type: text/plain; charset=ISO-8859-1 On Wed, Dec 22, 2010 at 4:05 PM, Ian Holsman wrote: > There are already 5 Hadoop 20.x releases out there, I don't think there is a need for another. (personal opinion, not a veto or speaking as the chair) > Are you counting other than Apache releases? (I see only 4 here, two of which probably should be removed: http://www.gtlib.gatech.edu/pub/apache//hadoop/core/.) > Is there a reason why we couldn't create a hadoop 0.20.3 release that has this patch inside of it, as well as other fixes that have been applied since 0.20.2 (~26 patches)? Would this be too much effort for you to RM?.. > I'd like that but my sense is the general populace of hadoopers would think the append/sync suite of patches destabilizing -- append/sync has a long 'history' in hadoop -- and a violation of the general principal that bug fixes only are added on a branch. > I really don't want to come to a^h^h^h^hget out of the situation where we have multiple releases of 0.20 each with a unique feature. > Sure. The notion has been broached before up on these lists -- e.g. there was talk of a 0.20 Apache release that had security in it -- and at the time folks seemed amenable. Thanks for getting the discussion off the ground, St.Ack