Return-Path: X-Original-To: apmail-hadoop-general-archive@minotaur.apache.org Delivered-To: apmail-hadoop-general-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 724AB8ECA for ; Fri, 9 Sep 2011 17:42:19 +0000 (UTC) Received: (qmail 36408 invoked by uid 500); 9 Sep 2011 17:42:17 -0000 Delivered-To: apmail-hadoop-general-archive@hadoop.apache.org Received: (qmail 36322 invoked by uid 500); 9 Sep 2011 17:42:16 -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 36301 invoked by uid 99); 9 Sep 2011 17:42:16 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 09 Sep 2011 17:42:16 +0000 X-ASF-Spam-Status: No, hits=-5.0 required=5.0 tests=RCVD_IN_DNSWL_HI X-Spam-Check-By: apache.org Received-SPF: unknown (athena.apache.org: error in processing during lookup of jrottinghuis@ebay.com) Received: from [216.113.175.152] (HELO den-mipot-001.corp.ebay.com) (216.113.175.152) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 09 Sep 2011 17:42:10 +0000 DomainKey-Signature: s=corp; d=ebay.com; c=nofws; q=dns; h=X-EBay-Corp:X-IronPort-AV:Received:Received:From:To:Date: Subject:Thread-Topic:Thread-Index:Message-ID:References: In-Reply-To:Accept-Language:Content-Language: X-MS-Has-Attach:X-MS-TNEF-Correlator:acceptlanguage: x-ems-proccessed:x-ems-stamp:Content-Type: Content-Transfer-Encoding:MIME-Version:X-CFilter; b=IMIgm+uPnyX9ihjR5SjOBVaVUi/zDyR0LVTcrWgVm69XbILcWnwA5mmo Dgx6RPUpLwV6MUwTAACH1fWzGNcTac7jYbIQSIorFf392eocxzQLGeDwg Tlb9mklLVzpVHxb; DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=ebay.com; i=jrottinghuis@ebay.com; q=dns/txt; s=corp; t=1315590130; x=1347126130; h=from:to:date:subject:message-id:references:in-reply-to: content-transfer-encoding:mime-version; bh=OA9IkKGZXw5aH7S9MCPKOMUMwki/qW/2gh4w6/nG1Qc=; b=S+38GNJDSp/9P4gaUiL34vg4rulEmmJKVdmcE1GjEbg1PmJwVyeW+SGE dYQE6lo7/R4xwnGN8ITcZyFsgbq5DFdhyaMEHjTgqKIYI4AC774KtYEKK PngAFSIM8OQynxF; X-EBay-Corp: Yes X-IronPort-AV: E=Sophos;i="4.68,357,1312182000"; d="scan'208";a="3349894" Received: from den-vtenf-002.corp.ebay.com (HELO DEN-MEXHT-003.corp.ebay.com) ([10.101.112.213]) by den-mipot-001.corp.ebay.com with ESMTP; 09 Sep 2011 10:41:48 -0700 Received: from DEN-MEXMS-001.corp.ebay.com ([10.241.16.225]) by DEN-MEXHT-003.corp.ebay.com ([10.241.17.54]) with mapi; Fri, 9 Sep 2011 11:41:47 -0600 From: "Rottinghuis, Joep" To: "general@hadoop.apache.org" Date: Fri, 9 Sep 2011 11:41:47 -0600 Subject: RE: abandoning 22 - was: Content request for 0.20.205 Sustaining Release Thread-Topic: abandoning 22 - was: Content request for 0.20.205 Sustaining Release Thread-Index: AcxvEnfUDjdbi9RdQjCNzAuNAFIqgQAAyVXw Message-ID: References: <9C0A256C-7DA3-4C40-9F64-A6812B1E2A8B@eecs.berkeley.edu> <-4341369250559116202@unknownmsgid> <4E69ED0C.1090402@apache.org> In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US x-ems-proccessed: 10SqDH0iR7ekR7SRpKqm5A== x-ems-stamp: U3G7yG0nRa2eVCpNDVi9Fg== Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-CFilter: Scanned -----Original Message----- From: Eli Collins [mailto:eli@cloudera.com]=20 Sent: Friday, September 09, 2011 10:03 AM To: general@hadoop.apache.org Subject: Re: abandoning 22 - was: Content request for 0.20.205 Sustaining R= elease ... > MR1 is being maintained on 20x. In fact 20x is the only MR1 code that sup= ports security and disk failure handling. The MR1 code in 22 is a regressio= n in some significant aspects (features, performance, bugs) from the latest= stable MR1 (204). ... Eli, aside from the disk failure handling which is a new feature in 205 (no= t present in earlier 20x releases), could you please elaborate on which oth= er significant aspects 22 would regress from 20x?=20 > My understanding of the way Apache operates is that you can't do things l= ike "declare blocks on upgrade paths". People can try to release updates to= 21 or 22 (or some new tree). Ie the decisions are made implicitly by where= people invest cycles. If a group of committers say that they'll commit to trunk, to 0.23 and to 0= .20x, but not to 0.22, then in effect that is like to "declare a block on u= pgrade path" isn't it? The more such commits that go in to other branches, = but not the ones in between essentially is a declaration of a block, becaus= e of the very regression argument you make. I agree that nobody can be made to contribute to something they don't want,= but does that result into a split? In other words, if a significant bug fix or feature goes into trunk and int= o 22, can developers then simply say: "I'm not interested to put this into = 23, you do this yourself if you want?". Will that be tolerated or vetoed? Thanks, Joep