We have to balance between the dev work of maintaining a branch for each HBase release versus the inconvenience of asking users to upgrade their HBase to get the next version of Phoenix, eg 4.8. Since in HBase, the upgrade is highly recommended (1.1 is much better than 1.0 and the upgrade is smooth in theory), I think it should be fine.
Enis On Fri, Feb 26, 2016 at 3:20 PM, Nick Dimiduk <ndimi...@gmail.com> wrote: > In this case we're effectively forcing users to upgrade their HBase if they > want to continue to receive Phoenix updates. That's probably fine? > > On Fri, Feb 26, 2016 at 3:15 PM, Enis Söztutar <e...@apache.org> wrote: > > > Hi, > > > > In case you are not following hbase-dev closely, after HBase-1.0.3, we do > > not expect any more 1.0.x releases from HBase: > > > > From > > > > > https://mail-archives.apache.org/mod_mbox/hbase-dev/201601.mbox/%3ccamuu0w8ounuaq7cgzw0-v1fcv5wxnwsxy1nq4g87u8d1+jp...@mail.gmail.com%3E > > > > Please note that 1.0.3 is the last “scheduled” release in the 1.0.x line > of > > releases since there is a limited amount of testing and release > management > > bandwidth. Users are highly encouraged to upgrade to 1.1 line of releases > > if possible. However, if there is enough interest, or needed otherwise, > we > > can still decide to do more releases. Please be encouraged to speak up if > > you want us to continue scheduled 1.0.x releases. See the hbase-dev > mailing > > thread [6] for more information. > > > > > > So, I think we can decide to drop the HBase-1.0 branch for Phoenix going > > forward (4.8+). What do you guys think? One less branch to manage. > > > > > > Enis > > >
