Mailing-List: contact dev-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@hbase.apache.org
MIME-Version: 1.0
In-Reply-To: <CAHxLZBUOr+fbCOaimqyNu4YoaOZcTj9othZgVK+01z1dPHmZ_g@mail.gmail.com>
References: <CAAF1JdjtH_n_f8a_rHOVi6Ky9M-UXu4YsWexyQvOay6zsGunbw@mail.gmail.com>
 <6D0460F8-E138-45B7-8E76-E33383FB64F0@gmail.com> <CAHxLZBXOc2p0HtKD1Gfcdt4KC7r9GDMCeKso6COcJ_NyHc7ung@mail.gmail.com>
 <CA+RK=_BBHa0cdZWp-RWHOnGUJBhu7SP4eXwoHMXONj4xj7-b8g@mail.gmail.com>
 <CAHxLZBXftF3g3RZq35jjJ8+y6+FMrMirpvcmGgDQuJjbzT3=Dw@mail.gmail.com> <CAHxLZBUOr+fbCOaimqyNu4YoaOZcTj9othZgVK+01z1dPHmZ_g@mail.gmail.com>
From: James Taylor <jamestaylor@apache.org>
Date: Wed, 5 Apr 2017 16:41:33 -0700
Message-ID: <CAAF1Jdi5G4mNi1K3KPw3u=8EpeuGz8MQBzi9oa5z-SunhLhUoA@mail.gmail.com>
Subject: Re: release of HBase 1.3.1?
To: HBase Dev <dev@hbase.apache.org>
Content-Type: multipart/alternative; boundary=001a11400afcc4c450054c73eec0
archived-at: Wed, 05 Apr 2017 23:41:37 -0000

--001a11400afcc4c450054c73eec0
Content-Type: text/plain; charset=UTF-8

Thanks, Mikhail, Andrew and the rest of the team! Really appreciate it.

    James

On Wed, Apr 5, 2017 at 4:39 PM, Mikhail Antonov <olorinbant@gmail.com>
wrote:

> All right, I cherry picked HBASE-17227 and the first RC is out.
>
> Thanks Andrew for the help pushing it!
>
> -Mikhail
>
> On Wed, Apr 5, 2017 at 12:47 PM, Mikhail Antonov <olorinbant@gmail.com>
> wrote:
>
> > Thanks Andrew!
> >
> > So after open jiras has been re-targeted for 1.3.2 and looking at the
> > filter
> > `affectedVersion in (1.3.0) AND fixVersion = 1.3.2 AND status in (Open,
> > "Patch Available", Reopened, "In Progress")`
> >
> > there are only few issues that warrant discussion before RC0, I think.
> >
> >  - HBASE-17513, where Thrift-1 security settings are easy to
> misconfigure.
> >    Currently marked critical, I don't think it's release blocker.
> Opinions?
> > -  HBASE-17227, a backport of HBASE-17206, a stability fix for FSHLog.
> > This one I think we should pull in.
> >
> > Everything else isn't important enough for an RC.
> >
> > Any opinions? Otherwise I'd cherry pick the latter one.
> >
> > -Mikhail
> >
> >
> > On Wed, Apr 5, 2017 at 11:20 AM, Andrew Purtell <apurtell@apache.org>
> > wrote:
> >
> >> Branch 1.3 updated and tagged for RC0.
> >>
> >> remote: hbase git commit: Update POMs and CHANGES.txt for 1.3.1 RC0
> >> To https://git-wip-us.apache.org/repos/asf/hbase.git
> >>    fd297e2..3a2f3aa  branch-1.3 -> branch-1.3
> >>  * [new tag]         1.3.1RC0 -> 1.3.1RC0
> >>
> >>
> >> On Mon, Apr 3, 2017 at 10:35 PM, Mikhail Antonov <olorinbant@gmail.com>
> >> wrote:
> >>
> >> > Hi,
> >> >
> >> > I've been planning to cut an RC for 1.3.1 for some time, apologize for
> >> the
> >> > delay here. I'm going to go over outstanding jiras tomorrow,
> >> > I think there are still few issues waiting for backports.
> >> >
> >> > Andrew - appreciate your offer! I have started preparations for 1.3.1
> >> > release, but any help with triaging changes, API compatibility tests
> >> > and general release testing would definitely be helpful.
> >> >
> >> > Thanks!
> >> > -Mikhail
> >> >
> >> > On Mon, Apr 3, 2017 at 9:52 PM, Andrew Purtell <
> >> andrew.purtell@gmail.com>
> >> > wrote:
> >> >
> >> > > I'd be happy to RM 1.3.1 unless someone already has it waiting in
> the
> >> > > wings.
> >> > >
> >> > >
> >> > > > On Apr 3, 2017, at 5:43 PM, James Taylor <jamestaylor@apache.org>
> >> > wrote:
> >> > > >
> >> > > > Hello,
> >> > > > We'd like to start supporting releases of Phoenix that work with
> the
> >> > > HBase
> >> > > > 1.3 branch, but there's a committed fix on which we rely
> >> (HBASE-17587)
> >> > > for
> >> > > > Phoenix to function correctly. Is there a time frame for an HBase
> >> 1.3.1
> >> > > > release?
> >> > > > Thanks,
> >> > > > James
> >> > >
> >> >
> >> >
> >> >
> >> > --
> >> > Thanks,
> >> > Michael Antonov
> >> >
> >>
> >>
> >>
> >> --
> >> Best regards,
> >>
> >>    - Andy
> >>
> >> If you are given a choice, you believe you have acted freely. - Raymond
> >> Teller (via Peter Watts)
> >>
> >
> >
> >
> > --
> > Thanks,
> > Michael Antonov
> >
>
>
>
> --
> Thanks,
> Michael Antonov
>

--001a11400afcc4c450054c73eec0--