Andrew, What's the planned release cycle for branch-1? As you know, I'm working on a pair of JIRAs (HBASE-22622 and 22623, which may or may not require HBASE-18127) that need to go out in a minor release due to semver (added methods to coprocessor interfaces), and they're definitely not all getting committed by Friday. I'd been assuming that 1.5 was my branch-1 release train.
HBase 1.2 was released Feb 2016; HBase 1.3 in Jan 2017; 1.4 in Dec 2017. That shows that 1.5 is long overdue, but it also means that if 1.6 follows suit, it won't come out until mid-to-late-2020, and it'll be a year or more before I can make use of them. I can't build a Phoenix feature that relies on an unreleased HBase one. Are we moving towards more frequent minors on branch-1, as I know has been discussed on this list before? If so, no problem, just let me know what train I need to aim for. If not, it'd be great if this train could stay in the station a bit longer. Thanks, Geoffrey On Wed, Jul 10, 2019 at 6:35 PM Andrew Purtell <[email protected]> wrote: > Now that HBASE-22627 (Port HBASE-22617 (Recovered WAL directories not > getting cleaned up) to branch-1) has been committed it's time to roll a new > set of 1.x releases for all releasing branches that needed this change. > > At a minimum this would be a 1.3.6 and 1.4.11. > > I would also like to try again to release 1.5.0. > > I'm back from vacation Friday. Planning on making the RCs and submitting > them for consideration next week. If you have any pending work for branch-1 > please try to get it in before then. > > -- > Best regards, > Andrew > > Words like orphans lost among the crosstalk, meaning torn from truth's > decrepit hands > - A23, Crosstalk >
