Mailing-List: contact dev-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@hbase.apache.org
Received-SPF: pass (nike.apache.org: domain of elliott.neil.clark@gmail.com
 designates 74.125.82.42 as permitted sender)
MIME-Version: 1.0
Sender: elliott.neil.clark@gmail.com
In-Reply-To: 
 <CAPzbcGSJJPAOmwP1XwTzLMhxvdiN4QAh9dhPdr2dEC4-DuN0aw@mail.gmail.com>
References: 
 <CADcMMgGtw3Dr3OYNGpKENOmp3oZW+Y6BAYf9TN2+4d6FrwhWqA@mail.gmail.com>
	<CADcMMgHwQD-fYXWL9vJUT23HAC9a6HjnpauHoVbD+Qygfr+KMQ@mail.gmail.com>
	<CA+4kjVvj-KV9aRpGEeiLU+eSWb=mXBQWwUY3NaT0ref-GC46ig@mail.gmail.com>
	<CADcMMgH86E8njX+kB_rad61Btf7d3LzZ-kZ5NxKUW=_fXJ4vvw@mail.gmail.com>
	<CA+4kjVswa6RXhNXYwCFS8An8gYeatb9eaF5WtCU+j5Xhp13OLA@mail.gmail.com>
	<CADcMMgEP8c6aYvu9iOMimiXQO1uxZU660_Q1qw8sPq0oNqfRcw@mail.gmail.com>
	<CAMUu0w80FR3Q9iiFR7ixCQ+tMP+G0-bNzk1hcmfS7k_FPvx+sA@mail.gmail.com>
	<CAMUu0w_EojOyKBCgmzN9pcxhi3hygXQ5kc7HztcSpxa0=K6ejQ@mail.gmail.com>
	<CADcMMgF_QZ+xMx7x=w2sEaG99UAw+01dH1yV4hey5aEnWcS67w@mail.gmail.com>
	<CAHXxaiAr6W36s7QG00xuCWuo9cKawZANRP4HXbp2JXX_P3CJzA@mail.gmail.com>
	<CAOmV22sraTcs-UhVcag=Ff2HKJ3GvT1y_=7k74azXscu7Qh4bA@mail.gmail.com>
	<CAPzbcGSJJPAOmwP1XwTzLMhxvdiN4QAh9dhPdr2dEC4-DuN0aw@mail.gmail.com>
Date: Wed, 9 Oct 2013 14:17:19 -0700
Message-ID: 
 <CALvzVW2ZOEMKPKTmk5-nK6jWbrJGcs0vt9uHOHfHt7UbDu8uFA@mail.gmail.com>
Subject: Re: HEADSUP: Working on new 0.96.0RC
From: Elliott Clark <eclark@apache.org>
To: "dev@hbase.apache.org" <dev@hbase.apache.org>
Cc: =?ISO-8859-1?Q?Enis_S=F6ztutar?= <enis@apache.org>
Content-Type: multipart/alternative; boundary=f46d0442696a0d05a604e8556919

--f46d0442696a0d05a604e8556919
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

At this point I think that we should have real clean IT test runs before
cutting another release.  And we can't really get that until the master
always comes back up (The issue stack was working on yesterday) and until
merging is stable.  I would like to see those two things fixed before 0.96


On Wed, Oct 9, 2013 at 1:38 PM, Devaraj Das <ddas@hortonworks.com> wrote:

> I'd say we cut an RC now (without any more fixes).
>
>
> On Wed, Oct 9, 2013 at 12:45 PM, Jimmy Xiang <jxiang@cloudera.com> wrote:
>
> > It's testing now. :)
> >
> >
> > On Wed, Oct 9, 2013 at 12:42 PM, Sergey Shelukhin <
> sergey@hortonworks.com
> > >wrote:
> >
> > > 9696 looks a little bit scary... did you guys test it on your rig?
> > >
> > >
> > > On Wed, Oct 9, 2013 at 11:54 AM, Stack <stack@duboce.net> wrote:
> > >
> > > > On Wed, Oct 9, 2013 at 10:45 AM, Enis S=F6ztutar <enis@apache.org>
> > wrote:
> > > >
> > > > > I just committed
> https://issues.apache.org/jira/browse/HBASE-9730for
> > > > > this.
> > > > > Time for another RC, what do you think?
> > > > >
> > > > > You know what they say, sixth time is the charm.
> > > >
> > > >
> > > >
> > > > I can cut one no problem.  Just say.
> > > >
> > > > Does your test rig pass?  Ours hasn't yet because of HBASE-9563;
> master
> > > is
> > > > killed and won't come back though restarted and tests fail.
> > > >
> > > > Do we want HBASE-9696 in there?  It is currently under test.
> > > >
> > > > And HBASE-9724 Failed region split is not handled correctly by AM?
> > > >
> > > > But if you fellas need me to put up a new one, just say.  Just take=
s
> a
> > > few
> > > > hours.
> > > >
> > > > 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 confidentia=
l,
> > > privileged and exempt from disclosure under applicable law. If the
> reader
> > > of this message is not the intended recipient, you are hereby notifie=
d
> > that
> > > 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
> > immediately
> > > and delete it from your system. Thank You.
> > >
> >
>
> --
> 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.
>

--f46d0442696a0d05a604e8556919--