Return-Path: Delivered-To: apmail-hadoop-general-archive@minotaur.apache.org Received: (qmail 85222 invoked from network); 21 Oct 2010 23:38:11 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 21 Oct 2010 23:38:11 -0000 Received: (qmail 43557 invoked by uid 500); 21 Oct 2010 23:38:09 -0000 Delivered-To: apmail-hadoop-general-archive@hadoop.apache.org Received: (qmail 43503 invoked by uid 500); 21 Oct 2010 23:38:09 -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 43495 invoked by uid 99); 21 Oct 2010 23:38:09 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 21 Oct 2010 23:38:09 +0000 X-ASF-Spam-Status: No, hits=-2.3 required=10.0 tests=RCVD_IN_DNSWL_MED,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of awittenauer@linkedin.com designates 69.28.149.24 as permitted sender) Received: from [69.28.149.24] (HELO esv4-mav02.corp.linkedin.com) (69.28.149.24) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 21 Oct 2010 23:38:04 +0000 DomainKey-Signature: s=prod; d=linkedin.com; c=nofws; q=dns; h=X-IronPort-AV:Received:From:To:Subject:Thread-Topic: Thread-Index:Date:Message-ID:References:In-Reply-To: Accept-Language:Content-Language:X-MS-Has-Attach: X-MS-TNEF-Correlator:x-originating-ip:Content-Type: Content-ID:Content-Transfer-Encoding:MIME-Version; b=orakKMd8SJugbec1iW7+uRsIJDUHKpiqfb3fudVCsgNLF8QVCzPGaBke cKPIV4bfWuUyIJkuT2KaU4jLb1VxEnGUV9zuLDSTOFFYy/RAJ7A8p1lXT VjfIKJ20Nj9L6EX; DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=linkedin.com; i=awittenauer@linkedin.com; q=dns/txt; s=proddkim; t=1287704284; x=1319240284; h=from:sender:reply-to:subject:date:message-id:to:cc: mime-version:content-transfer-encoding:content-id: content-description:resent-date:resent-from:resent-sender: resent-to:resent-cc:resent-message-id:in-reply-to: references:list-id:list-help:list-unsubscribe: list-subscribe:list-post:list-owner:list-archive; z=From:=20Allen=20Wittenauer=20 |Subject:=20Re:=20bringing=20the=20codebases=20back=20in =20line|Date:=20Thu,=2021=20Oct=202010=2023:37:44=20+0000 |Message-ID:=20|To:=20""=20|MIME-Version:=201.0 |Content-Transfer-Encoding:=20quoted-printable |Content-ID:=20<1DF7DBA6CCA12744BA525EB728175D43@linkedin .com>|In-Reply-To:=20|References:=20=0D=0A=20=0D=0A =20; bh=QVrBuptr9bKfWFd1Z1WFUcFGiSBGIQXPhgQ/pzK3UfY=; b=rp4QFevb/wExVJvD4N2Q7XESxPOwLLBLrSy5H/LBMqUE37zwZxhB7gc1 pihCVzjE3s/1SzwhywWIP6rZsPicqpTnUQ9/ghk/NnKYZnyOttgsX312F +SqNvmtN5zKLFzJ; X-IronPort-AV: E=Sophos;i="4.58,220,1286175600"; d="scan'208";a="16281347" Received: from ESV4-EXC01.linkedin.biz ([fe80::d7c:dc04:aea1:97d7]) by esv4-cas01.linkedin.biz ([172.18.46.140]) with mapi id 14.01.0218.012; Thu, 21 Oct 2010 16:37:44 -0700 From: Allen Wittenauer To: "" Subject: Re: bringing the codebases back in line Thread-Topic: bringing the codebases back in line Thread-Index: AQHLcVQVuqCpAAO/eUm8zw+IHmCpg5NMP34AgAAoEICAAB0MgA== Date: Thu, 21 Oct 2010 23:37:44 +0000 Message-ID: References: In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [172.18.46.247] Content-Type: text/plain; charset="us-ascii" Content-ID: <1DF7DBA6CCA12744BA525EB728175D43@linkedin.com> Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 On Oct 21, 2010, at 2:53 PM, Ian Holsman wrote: > yep.. I've heard it's a source of contention... Sure. Maybe like 8 months ago to anyone who was paying attention. > In discussing it with people, I've heard that a major issue (not the only > one i'm sure) is lack of resources to actually test the apache releases o= n > large clusters, and >=20 > So I thought I would start the thread to see if we could at least identif= y > what the people think are the problems are. I think you've asked the wrong question to begin with and I think the disc= ussion you've started is going to be completely counter productive and put = everyone on the defensive. [It is pretty clear it already has.] The team= is finally making progress towards a common goal (0.22) and (mostly) getti= ng along.=20 This question/issue > that it is very hard getting this done in short cycles > (hence the large gap between 20.x and 21). is really the cruxt of the problem. We wouldn't have had major diversions between the distributions if the mai= nline Apache distribution had been making more frequent releases. IMNSHO,= as long as the distributions don't break compatibility (forward or backwar= d) in without a word of warning... who cares?