Makes sense to drop the branch for HBase-1.0.x. I had proposed it here before: http://search-hadoop.com/m/9UY0h2XrnGW1d3OBF1&subj=+DISCUSS+Drop+branch+for+HBase+1+0+
Enis On Thu, Apr 21, 2016 at 8:06 AM, Andrew Purtell <andrew.purt...@gmail.com> wrote: > HBase announced at the last 1.0 release that it would be the last release > in that line and I think we would recommend any 1.0 user move up to 1.1 or > 1.2 at their earliest convenience. FWIW > > Also, as RM of the 0.98 code line I am considering ending its (mostly) > regular release cadence at the end of this calendar year. I'd continue if > there were expressed user or dev demand but otherwise place it into the > same state as 1.0. Also FWIW. I'd be curious to hear how many Phoenix users > are using 0.98 versus 1.0 and up, besides the folks at Salesforce, whom I > know well (smile). And, more generally, who in greater HBase land is still > on 0.98 and won't move off this year. > > > On Apr 20, 2016, at 5:00 PM, James Taylor <jamestay...@apache.org> > wrote: > > > > Due to some API changes in HBase, we need to have a separate branch for > our > > HBase 1.1 compatible branches. I've created a 4.x-HBase-1.1 branch for > this > > - please make sure to keep this branch in sync with the other 4.x and > > master branches. We can release 4.x-HBase-1.2 compatible releases out of > > master for 4.8. I think post 4.8 release we may not need to continue with > > the 4.x-HBase-1.0 branch. > > > > Thanks, > > James >
