From common-dev-return-73703-apmail-hadoop-common-dev-archive=hadoop.apache.org@hadoop.apache.org Sun Apr 11 15:49:33 2010 Return-Path: Delivered-To: apmail-hadoop-common-dev-archive@www.apache.org Received: (qmail 95695 invoked from network); 11 Apr 2010 15:49:33 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 11 Apr 2010 15:49:33 -0000 Received: (qmail 25407 invoked by uid 500); 11 Apr 2010 15:49:31 -0000 Delivered-To: apmail-hadoop-common-dev-archive@hadoop.apache.org Received: (qmail 25360 invoked by uid 500); 11 Apr 2010 15:49:31 -0000 Mailing-List: contact common-dev-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: common-dev@hadoop.apache.org Delivered-To: mailing list common-dev@hadoop.apache.org Received: (qmail 25352 invoked by uid 99); 11 Apr 2010 15:49:31 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 11 Apr 2010 15:49:31 +0000 X-ASF-Spam-Status: No, hits=-0.3 required=10.0 tests=AWL,RCVD_IN_DNSWL_NONE,SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (athena.apache.org: local policy) Received: from [209.85.218.217] (HELO mail-bw0-f217.google.com) (209.85.218.217) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 11 Apr 2010 15:49:25 +0000 Received: by bwz9 with SMTP id 9so3735843bwz.29 for ; Sun, 11 Apr 2010 08:49:03 -0700 (PDT) MIME-Version: 1.0 Received: by 10.204.70.77 with HTTP; Sun, 11 Apr 2010 08:49:03 -0700 (PDT) In-Reply-To: References: <56DC18C4-C9B1-4632-AAFD-589EABD237C3@apache.org> <4BBFC35D.70308@apache.org> Date: Sun, 11 Apr 2010 08:49:03 -0700 Received: by 10.204.22.79 with SMTP id m15mr3148769bkb.80.1271000943613; Sun, 11 Apr 2010 08:49:03 -0700 (PDT) Message-ID: Subject: Re: Plans for a 0.21 Hadoop Release From: Tom White To: common-dev@hadoop.apache.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Hi Owen, Thanks for your offer to review the work I've been doing on compatibility. If pushing back the freeze date will help us stabilize the public API, then I'm OK moving it to 30 April. On the serialization changes, I'm +1 to backing out the changes since 0.20 rather than trying to get new changes in for 0.21. Cheers, Tom On Sun, Apr 11, 2010 at 12:07 AM, Owen O'Malley wr= ote: > On Fri, Apr 9, 2010 at 5:16 PM, Doug Cutting wrote: > >> Is this just HADOOP-6685? =A0Or does it also include MAPREDUCE-1183? >> > > I just meant h-6685. > > My instinct would rather be to revert the serialization API changes made >> since 0.20 (mostly HADOOP-6165) if that's not an API we intend to suppor= t, >> and not add new APIs at the last minute. >> > > I have the patch almost ready, but it is a fair point that reverting the > previous change is lower risk. I will file an issue. I'm still asking for > the two week extension to look at the other APIs, especially since I'll > largely be offline this week. > > -- Owen >