From general-return-2244-apmail-hadoop-general-archive=hadoop.apache.org@hadoop.apache.org Fri Oct 22 21:52:28 2010 Return-Path: Delivered-To: apmail-hadoop-general-archive@minotaur.apache.org Received: (qmail 44665 invoked from network); 22 Oct 2010 21:52:28 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 22 Oct 2010 21:52:28 -0000 Received: (qmail 26151 invoked by uid 500); 22 Oct 2010 21:52:26 -0000 Delivered-To: apmail-hadoop-general-archive@hadoop.apache.org Received: (qmail 26113 invoked by uid 500); 22 Oct 2010 21:52:26 -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 26105 invoked by uid 99); 22 Oct 2010 21:52:26 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 22 Oct 2010 21:52:26 +0000 X-ASF-Spam-Status: No, hits=0.7 required=10.0 tests=RCVD_IN_DNSWL_NONE,SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (athena.apache.org: local policy) Received: from [74.125.83.48] (HELO mail-gw0-f48.google.com) (74.125.83.48) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 22 Oct 2010 21:52:22 +0000 Received: by gwb15 with SMTP id 15so1675719gwb.35 for ; Fri, 22 Oct 2010 14:52:01 -0700 (PDT) MIME-Version: 1.0 Received: by 10.229.231.3 with SMTP id jo3mr2784777qcb.21.1287784321143; Fri, 22 Oct 2010 14:52:01 -0700 (PDT) Received: by 10.229.237.131 with HTTP; Fri, 22 Oct 2010 14:52:01 -0700 (PDT) In-Reply-To: References: <4CC0BC80.6050303@apache.org> <211EF221-CFC5-42A5-99AD-339F120333D1@apache.org> Date: Fri, 22 Oct 2010 14:52:01 -0700 Message-ID: Subject: Re: bringing the codebases back in line From: Eli Collins To: general@hadoop.apache.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable On Thu, Oct 21, 2010 at 5:54 PM, Ian Holsman wrote: > On Thu, Oct 21, 2010 at 8:42 PM, Milind A Bhandarkar > wrote: > >> >> > >> > but the other question I have which hopefully you guys can answer is d= oes >> > the yahoo distribution have ALL the patches from the trunk on it? beca= use >> if >> > it doesn't I think that is problematic as well for other reasons. >> >> >> What are these "other" reasons ? >> > > yahoo distribution runs on our production clusters, and I do not see why = any >> production cluster should run code from trunk. >> >> > right.. the trunk is not for production use. =A0I wasn't suggesting that. > > but the trunk is what will eventually become the next release. > > Then someone in yahoo will have to decide if they are going to move to > rebase their production cluster to 0.21, or just continue back-porting wh= at > they need to the version they are running on their clusters. > > and if yahoo fixes a bug in their version, it would need to be > forward-ported over to the current trunk. which will get harder and harde= r > as the paths diverge. > > I'm sure you've seen it happen on other projects when a major branch land= s > on the trunk, and the amount of effort it takes to reconcile them. Hey Ian, I think we're all in agreement that we need to re-convene on a common branch that removes most of the deltas against an Apache release that we have all accumulated (primarily security, append, trunk backports). The open question is whether we try to come up with a common 20-based branch or wait for 22. That's been previously discussed on this list and there were some concerns, re-iterated on this thread, that we should invest in 22 rather than the current 20-based branches. Our current plan is to reconvene with everyone on 22 - a well-tested release with security and append should get users off the current 20-based branches. However if you and/or the Apache community feels that there needs to be an Apache 20-based branch and release that reflects what people are using (security, append, various backports in YDH/CDH) we are willing to create and maintain this branch on Apache. Thanks, Eli > =A0- Milind > > -- > Milind Bhandarkar > (mailto:milindb@yahoo-inc.com) > (phone: 408-203-5213 W) >