I won't pretend to be involved enough in the 2.0 work to give an opinion
:) -- I did say earlier that I'm happy to land this in 2.0 or 3.0
(whatever master decides to be at the time I merge).
If the spirit of the voters is to include this in 3.0 and not 2.0,
that's fine by me. I'm also happy to not immediately merge after this
vote completes.
Andrew Purtell wrote:
Would it help to cut a branch for 2.0 before attempting to merge in a new
major feature?
On Tue, May 9, 2017 at 8:41 AM, Josh Elser<els...@apache.org> wrote:
Reminder: I hope to close this in ~30hrs and there have been no votes so
far.
Josh Elser wrote:
Folks,
This is a vote to (rebase and) merge the branch HBASE-16961 into master.
Per the book, this requires 3 binding +1's from other committers to merge.
Relevant info for those who want to revisit any topics:
DISCUSS on merge[1]
Design Doc[2]
Staged user manual[3]
I'll plan to leave this open for at least 72hrs of the work days
(Wednesday May 10th EOD) in case there are any vetos. I would prefer to
abstain from voting on my own feature and plan to do so if the votes are
otherwise lacking.
- Josh
[1]
https://lists.apache.org/thread.html/a28c69bff315a791b9f7b94
6636446a60bd2ddc8d5a9f5c11c2bf6f4@%3Cdev.hbase.apache.org%3E
[2] http://home.apache.org/~elserj/hbase/FileSystemQuotasforApac
heHBase.pdf
[3] https://people.apache.org/~elserj/hbase/quotas/book.html#space-quotas
