Return-Path: Delivered-To: apmail-hadoop-general-archive@minotaur.apache.org Received: (qmail 15152 invoked from network); 22 Oct 2010 00:54:51 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 22 Oct 2010 00:54:51 -0000 Received: (qmail 3043 invoked by uid 500); 22 Oct 2010 00:54:49 -0000 Delivered-To: apmail-hadoop-general-archive@hadoop.apache.org Received: (qmail 3004 invoked by uid 500); 22 Oct 2010 00:54:49 -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 2996 invoked by uid 99); 22 Oct 2010 00:54:49 -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 00:54:49 +0000 X-ASF-Spam-Status: No, hits=2.9 required=10.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_NONE,SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (athena.apache.org: local policy) Received: from [74.125.82.176] (HELO mail-wy0-f176.google.com) (74.125.82.176) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 22 Oct 2010 00:54:44 +0000 Received: by wyg36 with SMTP id 36so240887wyg.35 for ; Thu, 21 Oct 2010 17:54:23 -0700 (PDT) MIME-Version: 1.0 Received: by 10.216.49.212 with SMTP id x62mr1768607web.55.1287708863171; Thu, 21 Oct 2010 17:54:23 -0700 (PDT) Received: by 10.216.87.78 with HTTP; Thu, 21 Oct 2010 17:54:23 -0700 (PDT) In-Reply-To: References: <4CC0BC80.6050303@apache.org> <211EF221-CFC5-42A5-99AD-339F120333D1@apache.org> Date: Thu, 21 Oct 2010 20:54:23 -0400 Message-ID: Subject: Re: bringing the codebases back in line From: Ian Holsman To: general@hadoop.apache.org Content-Type: multipart/alternative; boundary=001485f5ce5c5d0f3704932a1535 --001485f5ce5c5d0f3704932a1535 Content-Type: text/plain; charset=ISO-8859-1 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 does > > the yahoo distribution have ALL the patches from the trunk on it? because > 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. I 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 what 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 harder as the paths diverge. I'm sure you've seen it happen on other projects when a major branch lands on the trunk, and the amount of effort it takes to reconcile them. - Milind -- Milind Bhandarkar (mailto:milindb@yahoo-inc.com) (phone: 408-203-5213 W) --001485f5ce5c5d0f3704932a1535--