Return-Path: X-Original-To: apmail-hbase-dev-archive@www.apache.org Delivered-To: apmail-hbase-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 7D8BC10DA4 for ; Thu, 10 Oct 2013 17:15:10 +0000 (UTC) Received: (qmail 33725 invoked by uid 500); 10 Oct 2013 17:15:05 -0000 Delivered-To: apmail-hbase-dev-archive@hbase.apache.org Received: (qmail 33551 invoked by uid 500); 10 Oct 2013 17:15:03 -0000 Mailing-List: contact dev-help@hbase.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@hbase.apache.org Delivered-To: mailing list dev@hbase.apache.org Received: (qmail 33541 invoked by uid 99); 10 Oct 2013 17:15:03 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 10 Oct 2013 17:15:03 +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 jxiang@cloudera.com designates 209.85.220.53 as permitted sender) Received: from [209.85.220.53] (HELO mail-pa0-f53.google.com) (209.85.220.53) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 10 Oct 2013 17:14:58 +0000 Received: by mail-pa0-f53.google.com with SMTP id kq14so3022422pab.26 for ; Thu, 10 Oct 2013 10:14:38 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=bG+8jvTx50pL6yNJI3Q14L78MphE7EhRvW/AJX1R2MY=; b=F4SgBg7FfUeon1cMidoluAIOKIcZZoE+/h0BBCp0WGOmuSKv2I8C0ivc3Ui+wsMV87 ZrGmedhOGBRQIJdmvYRyYWd5yILMsA898e6coxq/KVceVqXXU2pCH8oHbF9iYQ/HiJBy r2YdXrQEPumniJxuIu9BGPCOaCLOkIEvuQvMx7P1BYLok9m7bmuKkELR6i8WjpZh3hGt ECM5wkuVz2N9xw5RkXmvJ5jTePmciBJSZEaQRZY2hdpG7Z/BsjmrLmdsHNcQ5H5XycwF wlfTjBDTh5szrbLaHLcXDvnVnJHBDT2TuIoUGfAGa+A03ffPhUe4bpScX7KIKExuZPuX UNcw== X-Gm-Message-State: ALoCoQlm4NDWPK2ruyy5bY+7BwI6mYWwSKkG00y4wjimNZnYDyr5fF/OFyIpo65V7a8CDDfwXe5K MIME-Version: 1.0 X-Received: by 10.66.182.36 with SMTP id eb4mr16631126pac.125.1381425278550; Thu, 10 Oct 2013 10:14:38 -0700 (PDT) Received: by 10.68.190.33 with HTTP; Thu, 10 Oct 2013 10:14:38 -0700 (PDT) In-Reply-To: References: Date: Thu, 10 Oct 2013 10:14:38 -0700 Message-ID: Subject: Re: HEADSUP: Working on new 0.96.0RC From: Jimmy Xiang To: dev@hbase.apache.org Cc: Stack , =?ISO-8859-1?Q?Enis_S=F6ztutar?= Content-Type: multipart/alternative; boundary=047d7bd6aa5c031adf04e8662386 X-Virus-Checked: Checked by ClamAV on apache.org --047d7bd6aa5c031adf04e8662386 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Can we agree if the IT tests are green for a certain number of runs in a row, then it's stable? On Thu, Oct 10, 2013 at 10:08 AM, Sergey Shelukhin wrote: > It looks like HBASE-9724 got committed. Was it the final patch for it? It= 's > a small and hopefully safe. > > If patch is large and risky, and the feature it fixes is semi-experimenta= l, > like HBASE-9696, IMHO it should not be blocker for the release. > The concern is that we keep making large changes to AM that fix some bugs > but may introduce more bugs (like it happened with the last one), so it's > hard to tell when it will stabilize at all. > > > > On Wed, Oct 9, 2013 at 9:22 PM, Elliott Clark wrote: > > > To me it feels like HBASE-9724 should go into 0.96. We're not releasin= g > a > > new rc tonight, it seems really weird to hold up a bug fix to try and h= it > > some unknown, and un-agreed upon, deadline. > > > > > > On Wed, Oct 9, 2013 at 8:08 PM, Stack wrote: > > > > > On Wed, Oct 9, 2013 at 7:14 PM, Enis S=F6ztutar wro= te: > > > > > >> > Anyways, if you fellas can't wait anymore, just say and we'll figu= re > > out > > >> something. > > >> As I see it, HBASE-9563 is committed, > > > > > > > > > It is still open and committed with qualification "Stack:...Was going > to > > > try this first but likely needs more..." and "Elliott: +1 I think it= 's > > > an improvement even if it doesn't 100% fix the master issue." > > > > > > > > > > > >> and HBASE-9696 is not a blocker > > >> against 0.96. But if you argue that 9696 is indeed a blocker, let's > > raise > > >> it as such. > > > > > > > > > > > > Agree. > > > > > > > > > > > >> There is no point in creating an RC, an immediately sinking it > > >> if we cannot verify the RC for a +1. We don't run into data loss > issues > > >> anymore which is why I still think we can release 0.96 even without > 9696 > > >> and 9724. Nothing is preventing us to release 0.96.1, with this and > more > > >> fixes in let's say a couple of weeks or months. > > >> > > >> I guess let's wait for tomorrow to see whether there is any progress > on > > >> 9563 and 9696. > > >> > > > > > > Yes. Lets take this up tomorrow. Elliott and I are on the master > issue, > > > HBASE-9563, this evening. > > > > > > Thanks Enis, > > > St.Ack > > > > > > > -- > CONFIDENTIALITY NOTICE > NOTICE: This message is intended for the use of the individual or entity = to > which it is addressed and may contain information that is confidential, > privileged and exempt from disclosure under applicable law. If the reader > of this message is not the intended recipient, you are hereby notified th= at > any printing, copying, dissemination, distribution, disclosure or > forwarding of this communication is strictly prohibited. If you have > received this communication in error, please contact the sender immediate= ly > and delete it from your system. Thank You. > --047d7bd6aa5c031adf04e8662386--