Return-Path: 
 <hdfs-dev-return-9929-apmail-hadoop-hdfs-dev-archive=hadoop.apache.org@hadoop.apache.org>
X-Original-To: apmail-hadoop-hdfs-dev-archive@minotaur.apache.org
Delivered-To: apmail-hadoop-hdfs-dev-archive@minotaur.apache.org
Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
	by minotaur.apache.org (Postfix) with SMTP id 59C5DF93A
	for <apmail-hadoop-hdfs-dev-archive@minotaur.apache.org>;
 Fri, 26 Apr 2013 18:02:53 +0000 (UTC)
Received: (qmail 46427 invoked by uid 500); 26 Apr 2013 18:02:50 -0000
Delivered-To: apmail-hadoop-hdfs-dev-archive@hadoop.apache.org
Received: (qmail 46260 invoked by uid 500); 26 Apr 2013 18:02:50 -0000
Mailing-List: contact hdfs-dev-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:hdfs-dev-help@hadoop.apache.org>
List-Unsubscribe: <mailto:hdfs-dev-unsubscribe@hadoop.apache.org>
List-Post: <mailto:hdfs-dev@hadoop.apache.org>
List-Id: <hdfs-dev.hadoop.apache.org>
Reply-To: hdfs-dev@hadoop.apache.org
Delivered-To: mailing list hdfs-dev@hadoop.apache.org
Received: (qmail 46239 invoked by uid 99); 26 Apr 2013 18:02:49 -0000
Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136)
    by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 26 Apr 2013 18:02:49 +0000
X-ASF-Spam-Status: No, hits=-0.7 required=5.0
	tests=RCVD_IN_DNSWL_LOW,SPF_PASS
X-Spam-Check-By: apache.org
Received-SPF: pass (athena.apache.org: domain of acm@hortonworks.com
 designates 209.85.210.43 as permitted sender)
Received: from [209.85.210.43] (HELO mail-da0-f43.google.com) (209.85.210.43)
    by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 26 Apr 2013 18:02:44 +0000
Received: by mail-da0-f43.google.com with SMTP id u36so2056254dak.16
        for <hdfs-dev@hadoop.apache.org>;
 Fri, 26 Apr 2013 11:02:24 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=google.com; s=20120113;
        h=x-received:content-type:mime-version:subject:from:in-reply-to:date
         :content-transfer-encoding:message-id:references:to:x-mailer
         :x-gm-message-state;
        bh=z5EIGCKxYRk1TeD0jGoPa+wtyp+7xlFVJx6ieuk4gyE=;
        b=nooAPXusIxYgyaO9TqvuYC+/ELqk1Qwar5GB/qEmCkyodvgsn0uQy+Xf1LMGVug8yg
         DnJg6cmysQenf7IMZGMmr8VUXc7/vahOH2I5Hs2KKPtjUi6pQZMe6yZOW0cZGP5JD2tF
         WJWEZhBv2xCU5+HqrpR4tnQswGg8FweizzNKNzRag2JwiHIiUs65u4iHPvPvUGO6Jks6
         3aSLE/H6wqwycxz1OONDDcvOkg0S7GQPz0JMW7NozKBpcnRvHtr/1knvqQAU2gRlVO8b
         vryaD+zi4yAsChRrfNLZMWqpYLRSNnt/Fk54r7MoLSw3VK9LCPQqQAynrffG7I4fQpJy
         96lw==
X-Received: by 10.66.234.198 with SMTP id ug6mr48470379pac.43.1366999344556;
        Fri, 26 Apr 2013 11:02:24 -0700 (PDT)
Received: from [10.11.3.189] (host1.hortonworks.com. [70.35.59.2])
        by mx.google.com with ESMTPSA id
 ag4sm12569908pbc.20.2013.04.26.11.02.19
        for <multiple recipients>
        (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128);
        Fri, 26 Apr 2013 11:02:20 -0700 (PDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Apple Message framework v1084)
Subject: Re: Heads up - 2.0.5-beta
From: Arun C Murthy <acm@hortonworks.com>
In-Reply-To: 
 <CADdVdVGpE_cbL8vCoYK=a31jLDpZ-yK7gnJBVdm_CjxuMmc2sQ@mail.gmail.com>
Date: Fri, 26 Apr 2013 11:02:18 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <8104CE3D-DA3B-48C6-B1F2-FBCF7EB77B9D@hortonworks.com>
References: <9408D111-C1D3-448C-A2E3-266A8CF4E176@hortonworks.com>
 <CADdVdVGpE_cbL8vCoYK=a31jLDpZ-yK7gnJBVdm_CjxuMmc2sQ@mail.gmail.com>
To: yarn-dev@hadoop.apache.org,
 common-dev@hadoop.apache.org,
 hdfs-dev@hadoop.apache.org,
 mapreduce-dev@hadoop.apache.org
X-Mailer: Apple Mail (2.1084)
X-Gm-Message-State: 
 ALoCoQntq8+hSCYLL3PcYNxecNy9wKlhRiwFrOFl7dRadyCOs8Zmp9iS/UiNj6cOcS9Y/0nUGk2x
X-Virus-Checked: Checked by ClamAV on apache.org


On Apr 25, 2013, at 6:36 PM, Suresh Srinivas wrote:

>> On Thu, Apr 25, 2013 at 6:34 PM, Arun C Murthy <acm@hortonworks.com> =
wrote:
>>=20
>> Similarly on HDFS side, can someone please help out by tagging =
features,
>> bug-fixes, protocol/API changes etc.? This way we can ensure HDFS =
APIs &
>> protocols are locked down too - I'd really appreciate it!
>=20
> To ensure a timely release of 2.0.5-beta, we should not hold back for
> individual features. However, I would like to make necessary API =
and/or
> protocol changes right-away. This will allow us to adding  features in
> subsequent releases e.g. hadoop-2.2 or hadoop-2.3 etc without breaking
> compatibility.=20

+1, sounds like a good plan. Thanks!

Arun=