Return-Path: X-Original-To: apmail-hadoop-hdfs-user-archive@minotaur.apache.org Delivered-To: apmail-hadoop-hdfs-user-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 921DBDD56 for ; Fri, 18 Jan 2013 20:38:02 +0000 (UTC) Received: (qmail 40571 invoked by uid 500); 18 Jan 2013 20:37:57 -0000 Delivered-To: apmail-hadoop-hdfs-user-archive@hadoop.apache.org Received: (qmail 40393 invoked by uid 500); 18 Jan 2013 20:37:57 -0000 Mailing-List: contact user-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@hadoop.apache.org Delivered-To: mailing list user@hadoop.apache.org Received: (qmail 40384 invoked by uid 99); 18 Jan 2013 20:37:57 -0000 Received: from minotaur.apache.org (HELO minotaur.apache.org) (140.211.11.9) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 18 Jan 2013 20:37:57 +0000 Received: from localhost (HELO mail-oa0-f53.google.com) (127.0.0.1) (smtp-auth username apurtell, mechanism plain) by minotaur.apache.org (qpsmtpd/0.29) with ESMTP; Fri, 18 Jan 2013 20:37:56 +0000 Received: by mail-oa0-f53.google.com with SMTP id j6so4297021oag.12 for ; Fri, 18 Jan 2013 12:37:56 -0800 (PST) MIME-Version: 1.0 X-Received: by 10.60.32.147 with SMTP id j19mr8087808oei.68.1358541476014; Fri, 18 Jan 2013 12:37:56 -0800 (PST) Received: by 10.60.1.101 with HTTP; Fri, 18 Jan 2013 12:37:55 -0800 (PST) In-Reply-To: <50F960D6.1010208@talend.com> References: <50F960D6.1010208@talend.com> Date: Fri, 18 Jan 2013 12:37:55 -0800 Message-ID: Subject: Re: Cohesion of Hadoop team? From: Andrew Purtell To: "common-user@hadoop.apache.org" Content-Type: multipart/alternative; boundary=e89a8fb1f5061729e904d3961664 --e89a8fb1f5061729e904d3961664 Content-Type: text/plain; charset=ISO-8859-1 It might also be helpful to differentiate between what commercial entities might do with release lines in ASF Hadoop and the relationship between the branches within ASF Hadoop itself. ASF Hadoop 1 and ASF Hadoop 2 are two versions of the same product, they do not compete with each other. On Fri, Jan 18, 2013 at 6:48 AM, Glen Mazza wrote: > One gets the impression the Hadoop committers are split into two teams, > with one team working on 0.23.x/2.0.2 and another team working on 1.x, > running the risk of increasingly diverging products eventually competing > with each other. -- Best regards, - Andy Problems worthy of attack prove their worth by hitting back. - Piet Hein (via Tom White) --e89a8fb1f5061729e904d3961664 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
It might also be helpful to dif= ferentiate between what commercial entities might do with release lines in = ASF Hadoop and the relationship between the branches within ASF Hadoop itse= lf. ASF Hadoop 1 and ASF Hadoop 2 are two versions of the same product, the= y do not compete with each other.

On Fri, Jan 18, 2= 013 at 6:48 AM, Glen Mazza <gmazza@talend.com> wrote:
One gets the impression the Hadoop committers are split into two teams, with one team working on 0.23.x/2.0.2 and another team working on 1.x, running the risk of increasingly diverging products eventually competing with each other.


--
Best regards,

=A0 =A0- Andy

Problems worthy of at= tack prove their worth by hitting back. - Piet Hein (via Tom White)
--e89a8fb1f5061729e904d3961664--