Re: [DISCUSS] Move stable pointer to the latest 2.3.x release

2020-09-16 Thread Guanghao Zhang
; > HBASE-24754, HBASE-24637 & HBASE-24850. > > > IMO we should move stable pointer after fixing these important issues. > > > > > > Regards, > > > Pankaj > > > > > > -----Original Message----- > > > From: Viraj Jasani [mailto:vjas...@a

Re: [DISCUSS] Move stable pointer to the latest 2.3.x release

2020-09-01 Thread Sean Busbey
ve stable pointer after fixing these important issues. > > > > Regards, > > Pankaj > > > > -Original Message- > > From: Viraj Jasani [mailto:vjas...@apache.org] > > Sent: Tuesday, September 1, 2020 12:12 AM > > To: dev@hbase.apache.org > > Subj

Re: [DISCUSS] Move stable pointer to the latest 2.3.x release

2020-09-01 Thread Viraj Jasani
e them > > HBASE-24754, HBASE-24637 & HBASE-24850. > > IMO we should move stable pointer after fixing these important issues. > > > > Regards, > > Pankaj > > > > -Original Message- > > From: Viraj Jasani [mailto:vjas...@apache.org] >

Re: [DISCUSS] Move stable pointer to the latest 2.3.x release

2020-09-01 Thread Duo Zhang
che.org > Subject: [DISCUSS] Move stable pointer to the latest 2.3.x release > > Hello everyone, > > While voting for 2.2.6 RC0, we had a short discussion reg moving stable > pointer to the latest 2.3.x and the decision was to initiate the discuss > thread when 2.3.1 and 2.2

RE: [DISCUSS] Move stable pointer to the latest 2.3.x release

2020-08-31 Thread Pankaj kr
sage- From: Viraj Jasani [mailto:vjas...@apache.org] Sent: Tuesday, September 1, 2020 12:12 AM To: dev@hbase.apache.org Subject: [DISCUSS] Move stable pointer to the latest 2.3.x release Hello everyone, While voting for 2.2.6 RC0, we had a short discussion reg moving stable pointer to the latest 2

[DISCUSS] Move stable pointer to the latest 2.3.x release

2020-08-31 Thread Viraj Jasani
Hello everyone, While voting for 2.2.6 RC0, we had a short discussion reg moving stable pointer to the latest 2.3.x and the decision was to initiate the discuss thread when 2.3.1 and 2.2.6 are out. Since 2.3.1 is already out and our RM is busy with 2.2.6 release process, I am initiating this