On hbase-backup, we are using in production for more then 1 year. I can vouch for it to be stable enough to be in a release version so that more people can use it and polished it further.
On Sun, Oct 16, 2022, 11:25 PM Andrew Purtell <andrew.purt...@gmail.com> wrote: > My understanding is some folks evaluating and polishing TLS for their > production are also considering hbase-backup in the same way, which is why > I linked them together. If that is incorrect then they both are still worth > considering in my opinion but would have a more tenuous link. > > Where we are with hbase-backup is it should probably be ported to where > more people would be inclined to evaluate it, in order for it to make more > progress. A new minor releasing line would fit. On the other hand if it is > too unpolished then the experience would be poor. > > > > On Oct 16, 2022, at 5:35 AM, 张铎 <palomino...@gmail.com> wrote: > > > > I believe the second one is still ongoing? > > > > Andrew Purtell <apurt...@apache.org> 于2022年10月14日周五 05:37写道： > >> > >> We will begin releasing activity for the 2.6 code line and as a > >> prerequisite to that we shall need to make a new branch branch-2.6 from > >> branch-2. > >> > >> Before we do that let's make sure all commits for the key features of > 2.6 > >> are settled in branch-2 before the branching point. Those key features > are: > >> - mTLS RPC > >> - hbase-backup backport > >> > >> -- > >> Best regards, > >> Andrew >
