Return-Path: 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 ABD3FD557 for ; Fri, 17 May 2013 19:52:37 +0000 (UTC) Received: (qmail 29120 invoked by uid 500); 17 May 2013 19:52:36 -0000 Delivered-To: apmail-hadoop-common-dev-archive@hadoop.apache.org Received: (qmail 29010 invoked by uid 500); 17 May 2013 19:52:36 -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 29001 invoked by uid 99); 17 May 2013 19:52:36 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 17 May 2013 19:52:36 +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 (nike.apache.org: domain of shaposhnik@gmail.com designates 209.85.210.169 as permitted sender) Received: from [209.85.210.169] (HELO mail-ia0-f169.google.com) (209.85.210.169) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 17 May 2013 19:52:29 +0000 Received: by mail-ia0-f169.google.com with SMTP id k38so5304019iah.14 for ; Fri, 17 May 2013 12:52:08 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:content-type; bh=GXP03aG6AnPbfbNsb98CmJ4TAJreE5rjdbmQarYWxk0=; b=sW1X/nqGZO5C0yo4ww8+qbbUH/PJvJMwcBGeau7m5xThRcz+7ypG4rXGEuvchY89zq EUBXl/SHKGE6AKzlEPmIX+u69eB/R6z95iDJtZrQ1ZUnV51QGzJ1TWTl/EwlwFson2uv l6MwwdOZx50tYGRvDP8E636GVsZi3qL09NGaqA+c5RGo27CD/hkjdg+HzMRBAvQwk1QG +5AStW1UGWMVg4ybJ9k8IgjGhZJd5Dcv2KMuSIUUdszpQXL9uoerv/H/SzU48W80teli EzRN+v3pnJcvu/4bRyxr+nNKBIDxhj8e+mIcLpE4KX1R/K8KuXhz/1o0kUkSCKD/y5+4 sbVw== MIME-Version: 1.0 X-Received: by 10.50.111.166 with SMTP id ij6mr7279120igb.47.1368820328173; Fri, 17 May 2013 12:52:08 -0700 (PDT) Sender: shaposhnik@gmail.com Received: by 10.43.6.70 with HTTP; Fri, 17 May 2013 12:52:07 -0700 (PDT) In-Reply-To: References: <48A037BF-5EE8-44EA-BE27-0BBB46DA0B5B@hortonworks.com> <548593E8-2791-4975-9710-D5D1EC51C516@apache.org> <426D7387-6CE0-4857-BFF0-AB52F0F4EEAD@hortonworks.com> <745A2B4D-86AE-4D03-8741-C2A99BD8AC06@hortonworks.com> Date: Fri, 17 May 2013 12:52:07 -0700 X-Google-Sender-Auth: wab_RZsZFA4OHqsXwFilRgFGygs Message-ID: Subject: Re: [VOTE] - Release 2.0.5-beta From: Roman Shaposhnik To: common-dev@hadoop.apache.org Content-Type: text/plain; charset=ISO-8859-1 X-Virus-Checked: Checked by ClamAV on apache.org Apologies for a bunch of delayed responses (and as such adding even more emails to this thread). On Wed, May 15, 2013 at 4:47 PM, Arun C Murthy wrote: >> My reading of your response is that while you appreciate the feedback >> Bigtop is providing you're not of an opinion that investigating the level >> of stability of Hadoop wrt. downstream any further than what is currently >> happening would be a worthy investment of Hadoop's community >> (or your personal for that matter) time? > > Everyone is welcome to contribute in any and all manner. I can't speak for everyone. > It would be useful if Bigtop could run regressions on releases here consistently. > We've also talked in the past about running Bigtop on branch-2, nightly. > Is that something you could help with? You'd earn my personal gratitude. There's a bunch of stuff that Bigtop can offer wrt. infrastructure and existing functionality that helps with integration testing of Hadoop. There's 10x more stuff we can do if folks other than Bigtop members would be willing to pitch in. I think a good closure to this discussion would be to identify things that we can do in Bigtop to help Hadoop stabilize quicker and also identify anybody who's potentially willing to help implementing these ideas. I'll try to collect all the good points that you and others have made on this thread wrt. this approach and will fork it into a separate discussion shortly. Thanks, Roman.