The 5.0.0 release apparently was an 'alpha'. I think we should do a 5.0.1 which can work with HBase 2.0.2 and remove the 'alpha'. 5.0 has feature parity with 4.14. 5.1 would have feature parity with 4.15, the main addition being splittable syscat
On a sidenote, I've been planning a 4.14.1 release but was waiting for the CDH builds. It looks like CDH branches are no longer being maintained so I think I can just move forward with that. (btw we should clean those up) If noone else is doing it, I can try doing the 5.0.1 release concurrently. On Wed, Sep 26, 2018 at 3:01 PM Andrew Purtell <apurt...@apache.org> wrote: > If possible please continue to release for one or more of the HBase 1.x > code lines. I have a feeling the HBase 1.xes will be in production for a > long time yet. > > On Wed, Sep 26, 2018 at 11:42 AM Thomas D'Silva <tdsi...@salesforce.com> > wrote: > > > Would we also release 4.15, or just a new 5.x release to support HBase > > 2.0.1/2.0.2 ? PHOENIX-3534 has a few follow-up JIRAs that are needed for > > splittable system catalog. > > > > On Tue, Sep 25, 2018 at 7:56 PM, Josh Elser <els...@apache.org> wrote: > > > > > On the user@phoenix list, Francis pointed out how Phoenix 5.0.0 only > > > works with HBase 2.0.0 and not 2.0.1 or 2.0.2. This is pretty bad given > > the > > > big fixes that went in since 2.0.0. > > > > > > What do folks think about a new 5.x release? Is it worthwhile to bring > > > back a reduced set of commits and make a 5.0.1? Or just release a 5.1.0 > > and > > > ask people to move to that instead? > > > > > > - Josh > > > > > > > > -- > Best regards, > Andrew > > Words like orphans lost among the crosstalk, meaning torn from truth's > decrepit hands > - A23, Crosstalk >
