Mailing-List: contact dev-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@hbase.apache.org
Message-ID: <58D409AA.40701@apache.org>
Date: Thu, 23 Mar 2017 13:45:14 -0400
From: Josh Elser <elserj@apache.org>
User-Agent: Postbox 3.0.11 (Macintosh/20140602)
MIME-Version: 1.0
To: dev <dev@hbase.apache.org>
Subject: Re: [DISCUSS] Moving towards merge on HBASE-16961 (space quota)
References: <58D0496E.4060101@apache.org> <58D05CF4.7050705@apache.org>
In-Reply-To: <58D05CF4.7050705@apache.org>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
archived-at: Thu, 23 Mar 2017 17:45:24 -0000

bump

Josh Elser wrote:
> Rebase is done for those who want to just look at some code.
>
> https://github.com/apache/hbase/compare/HBASE-16961
>
> Josh Elser wrote:
>> Hiya folks,
>>
>> As advertised (warned? *winks*), all of the sub-tasks on HBASE-16961
>> have been resolved after being committed to the HBASE-16961 branch in
>> SCM.
>>
>> While Ted has been a stalwart reviewer, it would be good to get another
>> set of eyes (or a few sets) on the changes before considering I start a
>> vote to merge into master.
>>
>> Presently, I'm rebasing the branch on top of master (as it's been a
>> while since I've done that). While I do that, I wanted to ask: what can
>> I do to help make this review process easiest?
>>
>> * Squash commits into one and put on RB?
>> * Pointers to tests that outline how users interact via API?
>> * Put together a little example devs can work through locally?
>>
>> I want to avoid this work lingering in the ether for a long period of
>> time -- I'm happy to try to make what will surely be a difficult review
>> any easier.
>>
>> - Josh