Return-Path: 
 <common-dev-return-82307-apmail-hadoop-common-dev-archive=hadoop.apache.org@hadoop.apache.org>
X-Original-To: apmail-hadoop-common-dev-archive@www.apache.org
Delivered-To: apmail-hadoop-common-dev-archive@www.apache.org
Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
	by minotaur.apache.org (Postfix) with SMTP id 61ED310423
	for <apmail-hadoop-common-dev-archive@www.apache.org>;
 Wed,  3 Jul 2013 18:06:44 +0000 (UTC)
Received: (qmail 54943 invoked by uid 500); 3 Jul 2013 18:06:42 -0000
Delivered-To: apmail-hadoop-common-dev-archive@hadoop.apache.org
Received: (qmail 54884 invoked by uid 500); 3 Jul 2013 18:06:42 -0000
Mailing-List: contact common-dev-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:common-dev-help@hadoop.apache.org>
List-Unsubscribe: <mailto:common-dev-unsubscribe@hadoop.apache.org>
List-Post: <mailto:common-dev@hadoop.apache.org>
List-Id: <common-dev.hadoop.apache.org>
Reply-To: common-dev@hadoop.apache.org
Delivered-To: mailing list common-dev@hadoop.apache.org
Received: (qmail 54870 invoked by uid 99); 3 Jul 2013 18:06:40 -0000
Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136)
    by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 03 Jul 2013 18:06:40 +0000
X-ASF-Spam-Status: No, hits=1.5 required=5.0
	tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS
X-Spam-Check-By: apache.org
Received-SPF: pass (athena.apache.org: domain of vinodkv@hortonworks.com
 designates 209.85.160.51 as permitted sender)
Received: from [209.85.160.51] (HELO mail-pb0-f51.google.com) (209.85.160.51)
    by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 03 Jul 2013 18:06:35 +0000
Received: by mail-pb0-f51.google.com with SMTP id um15so368657pbc.38
        for <common-dev@hadoop.apache.org>;
 Wed, 03 Jul 2013 11:06:15 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=google.com; s=20120113;
        h=subject:mime-version:content-type:from:in-reply-to:date:cc
         :message-id:references:to:x-mailer:x-gm-message-state;
        bh=TmCtw1LXWN5aKeGAGfTpQgcETH7txCzsohr55zIEm1w=;
        b=GIniLAnx0RyAoo+3XgoLwwMlCUZBxEEekzL5t1mP/g3g41kO+8NMh+joTi7pCJcZT3
         s/ux0OtB0aXX8OschZjoH7MQbMyneWKU5CIunDgUrkejV/xxjy2PmImPnSUqESHJj4Y8
         YBnGwPQpBBjCkKc7mDZYEPuzXvUVg8ReNu1v7pvrVPqsQHp8IscDfYPl8t9/NekhZGTd
         CYUN60J8w+YbtbXMNKtrTJy7llqMiYUqMGfgoWRbKiE1Rriy0NlBBnVvxpwRLdrQbCxX
         NyuXHyjL/g94BCyWJpDfZGhdlrjN9K1512AEPCD5xmagl2C8Yjt5tHr7YEfLAgIvJzB2
         yRlg==
X-Received: by 10.68.184.100 with SMTP id et4mr2007512pbc.48.1372874775362;
        Wed, 03 Jul 2013 11:06:15 -0700 (PDT)
Received: from [10.11.3.117] ([192.175.27.2])
        by mx.google.com with ESMTPSA id
 sb3sm34640723pac.14.2013.07.03.11.06.13
        for <multiple recipients>
        (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128);
        Wed, 03 Jul 2013 11:06:14 -0700 (PDT)
Subject: Re: [VOTE] Release Apache Hadoop 2.1.0-beta
Mime-Version: 1.0 (Apple Message framework v1283)
Content-Type: multipart/alternative;
 boundary="Apple-Mail=_05CF63E6-872E-47AF-8FDF-0C81865BFC69"
From: Vinod Kumar Vavilapalli <vinodkv@hortonworks.com>
In-Reply-To: <B307D71F-F328-418A-8B92-A65C3B2748BD@apache.org>
Date: Wed, 3 Jul 2013 11:06:14 -0700
Cc: "common-dev@hadoop.apache.org" <common-dev@hadoop.apache.org>,
 "hdfs-dev@hadoop.apache.org" <hdfs-dev@hadoop.apache.org>,
 "mapreduce-dev@hadoop.apache.org" <mapreduce-dev@hadoop.apache.org>
Message-Id: <793303BE-F2E8-4039-9B85-618B7D53BEDD@apache.org>
References: <3A68E85B-5097-4E41-8169-3307AD53983E@hortonworks.com>
 <B307D71F-F328-418A-8B92-A65C3B2748BD@apache.org>
To: yarn-dev@hadoop.apache.org
X-Mailer: Apple Mail (2.1283)
X-Gm-Message-State: 
 ALoCoQnRXJYPPH094F/kpogyVONswWwWtokghOOzHXlCqwe76PxPxdSE1QUrZgSroM+rcZ/Pu3FL
X-Virus-Checked: Checked by ClamAV on apache.org

--Apple-Mail=_05CF63E6-872E-47AF-8FDF-0C81865BFC69
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii


We should get these in, looking at them now.

Thanks,
+Vinod

On Jun 28, 2013, at 12:03 PM, Hitesh Shah wrote:

> Hi Arun,=20
>=20
> =46rom a YARN perspective, YARN-791 and YARN-727 are 2 jiras that may =
potentially change the apis. They can implemented in a backward compat =
fashion if committed after 2.1.0. However, this will require adding of =
differently-named apis ( different urls in case of the webservices ) and =
make the current version of the api deprecated and/or obsolete. YARN-818 =
which is currently patch available also changes behavior. =20
>=20
> Assuming that as soon as 2.1.0 is released, we are to follow a very =
strict backward-compat retaining approach to all user-facing layers  ( =
api/webservices/rpc/... ) in common/hdfs/yarn/mapreduce, does it make =
sense to try and pull them in and roll out a new RC after they are =
ready? Perhaps Vinod can chime in if he is aware of any other such jiras =
under YARN-386 which should be considered compat-related blockers for a =
2.1.0 RC.=20
>=20
> thanks
> -- Hitesh
>=20
> On Jun 26, 2013, at 1:17 AM, Arun C Murthy wrote:
>=20
>> Folks,
>>=20
>> I've created a release candidate (rc0) for hadoop-2.1.0-beta that I =
would like to get released.
>>=20
>> This release represents a *huge* amount of work done by the community =
(639 fixes) which includes several major advances including:
>> # HDFS Snapshots
>> # Windows support
>> # YARN API stabilization
>> # MapReduce Binary Compatibility with hadoop-1.x
>> # Substantial amount of integration testing with rest of projects in =
the ecosystem
>>=20
>> The RC is available at: =
http://people.apache.org/~acmurthy/hadoop-2.1.0-beta-rc0/
>> The RC tag in svn is here: =
http://svn.apache.org/repos/asf/hadoop/common/tags/release-2.1.0-beta-rc0
>>=20
>> The maven artifacts are available via repository.apache.org.
>>=20
>> Please try the release and vote; the vote will run for the usual 7 =
days.
>>=20
>> thanks,
>> Arun
>>=20
>> --
>> Arun C. Murthy
>> Hortonworks Inc.
>> http://hortonworks.com/
>>=20
>>=20
>=20


--Apple-Mail=_05CF63E6-872E-47AF-8FDF-0C81865BFC69--