Re: keep 2.x branch in sync with master branch?

Sounds like a plan. Please back port your commits to replace deprecated APIs (and any others possible) first so we don't run into so many merge issues. On Tue, Dec 5, 2017 at 3:23 PM, Josh Elser wrote: > If it's not too onerous, I think it would be good! > > The 5.x-HBase-2.0

Re: keep 2.x branch in sync with master branch?

If it's not too onerous, I think it would be good! The 5.x-HBase-2.0 branch has definitely been stabilized recently (thanks to the great work by Sergey, Ankit, and Rajeshbabu). If it is a pain (e.g. PreCommit broken, Tests broken, other), we can just plan to review it again later. On

keep 2.x branch in sync with master branch?

Question for folks working on 2.x branch - would you like those of us committing patches to master to commit them to the 2.x branch as well? If so, probably best to back port as many changes as possible from 2.x back to 1.x. Please advise. Thanks, James