Mailing-List: contact dev-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@hbase.apache.org
Received-SPF: pass (athena.apache.org: domain of ndimiduk@gmail.com designates
 209.85.220.181 as permitted sender)
MIME-Version: 1.0
In-Reply-To: 
 <CAHXxaiCtviDLsqFLEGQOdYRYUMFFDv246AYpHQwZnTW-KNQ2Zg@mail.gmail.com>
References: 
 <CADcMMgGa0gunuNmEstWQsf8dQRRrGaENS7d=B76A9r2G9B+C-g@mail.gmail.com>
 <CADcMMgFp3Y4R3n-KNj-jBzvTyq=tTorp2oLmRaaZLg3Qs1yvWQ@mail.gmail.com>
 <CAPzbcGTf9UgAbeVOwOe55HEYOTsZ+B0o8Tdjk37hvfaH-_ZQvQ@mail.gmail.com>
 <CAHXxaiCtviDLsqFLEGQOdYRYUMFFDv246AYpHQwZnTW-KNQ2Zg@mail.gmail.com>
From: Nick Dimiduk <ndimiduk@gmail.com>
Date: Wed, 11 Sep 2013 11:22:04 -0700
Message-ID: 
 <CANZa=GvHTFd6nVOY4Zn8k01t1TT-RyeMJ9KZ5upHzBHkJ=XoEg@mail.gmail.com>
Subject: Re: [VOTE] The 1st hbase-0.96.0 release candidate is available for
 download
To: hbase-dev <dev@hbase.apache.org>
Content-Type: multipart/alternative; boundary=089e013a2746f7162504e61fb307

--089e013a2746f7162504e61fb307
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Likewise, some subset of Jon's HBASE-9245 should be resolved before we cut
the next RC.


On Wed, Sep 11, 2013 at 11:11 AM, Sergey Shelukhin
<sergey@hortonworks.com>wrote:

> HBASE-9496 needs to be in imho, we need to keep compatible APIs. Let me
> start on it today.
>
>
> On Wed, Sep 11, 2013 at 10:51 AM, Devaraj Das <ddas@hortonworks.com>
> wrote:
>
> > In my tests, I couldn't (yet) reproduce the dataloss problem, but I
> > ran into assignment manager issues (mentioned in HBASE-9338) and all
> > except one has been committed. Could we please hold on until that last
> > one is committed (HBASE-9480).
> >
> > On Wed, Sep 11, 2013 at 10:19 AM, Stack <stack@duboce.net> wrote:
> > > I am going to roll a new RC.  The hbase-it dataloss problem has been
> > > figured as an issue in the test harness (details to follow).  Any ite=
ms
> > > folks want to be sure make the next RC?
> > >
> > > Thanks,
> > > St.Ack
> > >
> > >
> > > On Fri, Aug 30, 2013 at 8:35 PM, Stack <stack@duboce.net> wrote:
> > >
> > >> hbase-0.96.0  will be our next major release.  It is intended to
> > supplant
> > >> the 0.94.x series.
> > >>
> > >> hbase-0.96.0RC0 is our first candidate for release hbase-0.96.0.
> > >>
> > >> The signed tarballs are available here:
> > >>
> > >>  http://people.apache.org/~stack/0.96.0RC0/
> > >>
> > >> The hbase built against hadoop1 artifacts are here:
> > >>
> > >>
> https://repository.apache.org/content/repositories/orgapachehbase-126/
> > >>
> > >> The hbase built against hadoop2 artifacts are here:
> > >>
> > >>
> https://repository.apache.org/content/repositories/orgapachehbase-127/
> > >>
> > >> Note that hbase-0.96.0 comes in two flavors; a build that includes a=
nd
> > >> runs on hadoop-1.x and another for hadoop-2.x.  You must chose the
> hbase
> > >> that suits your hadoop context.
> > >>
> > >> Almost 2k issues [1] are attributed to this version (counting fixes
> done
> > >> against this and the 0.95.x developer series of releases).  Almost 1=
00
> > >> fixes have been committed since 0.95.2.  I will follow up w/ a
> synopsis
> > of
> > >> the major changes.
> > >>
> > >> Please take it for a spin.  We are interested in any issues found bu=
t
> in
> > >> particular, we would appreciate feedback on how well the migration o=
f
> a
> > >> 0.94.x dataset to run under 0.96.0 works [2].
> > >>
> > >> Should this candidate become hbase-0.96.0?  Please vote +/-1 by
> > September
> > >> 9th.
> > >>
> > >>
> > >> St.Ack
> > >>
> > >> 1.
> > >>
> >
> https://issues.apache.org/jira/issues/?jql=3Dproject%20%3D%20HBASE%20AND%=
20(%20fixVersion%20%3D%20%220.96.0%22%20or%20fixVersion%20%3D%20%220.95.0%2=
2%20%20or%20fixVersion%20%3D%20%220.95.1%22%20or%20fixVersion%20%3D%20%220.=
95.2%22%20)%20AND%20(status%20%3D%20Resolved%20OR%20status%20%3D%20Closed)%=
20ORDER%20BY%20issuetype%20DESC%2C%20priority%20DESC
> > >> 2. http://hbase.apache.org/book.html#upgrade0.96
> > >>
> >
> > --
> > CONFIDENTIALITY NOTICE
> > NOTICE: This message is intended for the use of the individual or entit=
y
> to
> > which it is addressed and may contain information that is confidential,
> > privileged and exempt from disclosure under applicable law. If the read=
er
> > of this message is not the intended recipient, you are hereby notified
> 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.
>

--089e013a2746f7162504e61fb307--