1.3.1 appears to be (mostly?) through the paces and there's been no further activity on branch-1.1 since my original mail. RC in flight.
On Tue, Apr 4, 2017 at 9:19 PM, Andrew Purtell <andrew.purt...@gmail.com> wrote: > If you'd like to release I will certainly vote on the candidate. If that > informs your opinion on spinning a release candidate. > > > > On Apr 4, 2017, at 7:57 PM, Nick Dimiduk <ndimi...@apache.org> wrote: > > > > Hey there, > > > > It's been about a month since 1.1.9. However there's only 11 commits to > > branch-1.1 since that time. Based on commit messages, there's only [0], > [1] > > that I think would make someone really impatient for a fix. [0] is marked > > 'Critical', so I'm on the fence. Unless someone speaks up, I'm thinking > > I'll wait for 1.1.10 until after the 1.3.1 release, give a chance for > some > > backports to trickle down. Any objections? > > > > -n > > > > [0]: HBASE-17717 Explicitly use "sasl" ACL scheme for hbase superuser > > [1]: HBASE-17682 Region stuck in merging_new state indefinitely >
