+1
Can't sign up to do it myself, and EOL for HBase is making the decision
for us anyways.
On 10/17/17 1:32 PM, James Taylor wrote:
Looks like we have no volunteer (which is fine). On top of that, it appears
that HBase 1.1 is nearing EOF. Let's please stop committing to any of the
HBase-1.1 b
Looks like we have no volunteer (which is fine). On top of that, it appears
that HBase 1.1 is nearing EOF. Let's please stop committing to any of the
HBase-1.1 branches (i.e. 4.x-HBase-1.1 and 4.12-HBase-1.1) and not plan to
release further HBase 1.1 based releases.
Thanks,
James
On Wed, Oct 11,
For what it's worth, HBase community is pretty close to EOL on HBase 1.1.
Probably 1.1.13 or 1.1.14 will be the last release (though I'm still not
sure that DISCUSS thread has reached a conclusion).
On Wed, Oct 11, 2017 at 2:54 PM Josh Elser wrote:
> I'm still mulling this over, but my first rea
I'm still mulling this over, but my first reaction is that I think this
is an acceptable solution going forward (agreeing with your "lighter
burden" sentiments in the other thread).
Would kindly request a few days to give it some thought before we make
any decisions.
On 10/11/17 12:59 PM, Ja
If someone needs Phoenix to continue doing HBase 1.1 based releases, please
volunteer to be release manager. Without a volunteer, releases for HBase
1.2 will not continue.
Thanks,
James
