Nice article! Thanks for the authors. An off-the-topic suggestion to dev list:
Now we commit some big and new features to master branch only, which will be included in a new major version, for example, 2.0. However, a major version is not upgraded very quickly, 1.0.0 was released two years ago and we still don't release 2.0.0. HBASE-11425 is resolved more than one year ago. In the worst case, if we make some work done and commit to master branch just after cutting a new major release branch, the feature will be released two years later or even longer. It is no need and no benefits to wait so long. Bugs of the new feature in dev branches only are hardly to be found, and committers may not be familiar with a feature which is committed two years ago... So my suggestion is cutting branch-x faster and have some fixed period, for example, six month or one year? Thanks, Phil 2017-03-09 14:24 GMT+08:00 Stack <st...@duboce.net>: > See writeup on how work done by your Yu Li, Sun Yu, Anoop Sam John, and > Ramkrishna S Vasudevan improved throughput at scale on Singles Day 2016 @ > Alibaba. > > Read all about it at https://blogs.apache.org/hbase/ > > Yours, > St.Ack >
