Return-Path: 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 227B210DF7 for ; Wed, 17 Jul 2013 19:25:21 +0000 (UTC) Received: (qmail 57804 invoked by uid 500); 17 Jul 2013 19:25:15 -0000 Delivered-To: apmail-hadoop-hdfs-dev-archive@hadoop.apache.org Received: (qmail 57206 invoked by uid 500); 17 Jul 2013 19:25:09 -0000 Mailing-List: contact hdfs-dev-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: hdfs-dev@hadoop.apache.org Delivered-To: mailing list hdfs-dev@hadoop.apache.org Received: (qmail 57181 invoked by uid 99); 17 Jul 2013 19:25:07 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 17 Jul 2013 19:25:07 +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 (nike.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, 17 Jul 2013 19:25:00 +0000 Received: by mail-pb0-f51.google.com with SMTP id um15so2254978pbc.24 for ; Wed, 17 Jul 2013 12:24:39 -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=siQifpR7a9phZ5xCUR6fDsZjH5E7zEeva3Ym5DnF1d8=; b=iRxeqW+jdVhY/PLXzYgEf56K2Sqa98pVK7SZEkOyZEYzD0r+HBtv/2hlvsRNMbDqlk EXBXSfLT/60XktsvzN8zDcEloVi+gBo5aucNXNizRSvXh1AUf022qyF9M8fnT5SoncVR kJJMM9eXelXZgLt8agWdYdbwQ+CFhhRjmsdTHUmmpYPHRq7/f0ROH1j6wEDN+i2bupbN ydCbMG5SWk7hD+eviw99DGbXBa63bt1cfLo7LxT46rJQl5nuH4u59msAZouNGvXG79jR juYrOPofo8j2Gnqvn0M/LpO3lt+ZSpQ2/Tp2Kzi/2Q4k956Wth4PzNwJWKmR4dHl3Ls6 g2qw== X-Received: by 10.68.179.101 with SMTP id df5mr8529282pbc.33.1374089079205; Wed, 17 Jul 2013 12:24:39 -0700 (PDT) Received: from [10.11.2.112] ([192.175.27.2]) by mx.google.com with ESMTPSA id mr3sm9341078pbb.27.2013.07.17.12.24.31 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 17 Jul 2013 12:24:32 -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=_9A1FDF22-E02A-43DB-BBD7-DC2476A1A90F" From: Vinod Kumar Vavilapalli In-Reply-To: <793303BE-F2E8-4039-9B85-618B7D53BEDD@apache.org> Date: Wed, 17 Jul 2013 12:24:30 -0700 Cc: "common-dev@hadoop.apache.org" , "hdfs-dev@hadoop.apache.org" , "mapreduce-dev@hadoop.apache.org" Message-Id: <2246EC71-C343-4DC0-9476-22F0DA4D5EA0@apache.org> References: <3A68E85B-5097-4E41-8169-3307AD53983E@hortonworks.com> <793303BE-F2E8-4039-9B85-618B7D53BEDD@apache.org> To: yarn-dev@hadoop.apache.org X-Mailer: Apple Mail (2.1283) X-Gm-Message-State: ALoCoQnTNQfBtePAlnVNXysh2r8BCMMVghREgLcZT7H/P4uSqq8wuGxm5e06X8m6f6SDF79bIvfr X-Virus-Checked: Checked by ClamAV on apache.org --Apple-Mail=_9A1FDF22-E02A-43DB-BBD7-DC2476A1A90F Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii Looks like this RC has gone stale and lots of bug fixes went into 2.1 = and 2.1.0 branches and there are 4-5 outstanding blockers. And from what = I see in CHANGES.txt files there seems to be a confusion about which = branch to get in what. I'm blowing off the current 2.1.0 release branch so that we can create a = fresh release branch and call voting on that. I'll fix CHANGES.txt = entries as well as JIRA fix version for bugs committed recently if there = are inconsistencies. Let me know if something is amiss while I do this. Thanks, +Vinod On Jul 3, 2013, at 11:06 AM, Vinod Kumar Vavilapalli wrote: >=20 > We should get these in, looking at them now. >=20 > Thanks, > +Vinod >=20 > On Jun 28, 2013, at 12:03 PM, Hitesh Shah wrote: >=20 >> 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 >=20 --Apple-Mail=_9A1FDF22-E02A-43DB-BBD7-DC2476A1A90F--