Sounds good. It’s about time for 1.16, and thanks for offering to be release manager.
But I’d like to get Avatica 1.11 [1] released first — it’s been 9 months — and make Calcite 1.16 depend on Avatica 1.11. See email thread[2]. Although that thread talks about an Avatica-Go release, that should not be a blocker for Calcite 1.16. For both Avatica and Calcite we should update dependencies. Julian [1] https://issues.apache.org/jira/browse/CALCITE-2182 <https://issues.apache.org/jira/browse/CALCITE-2182> [2] https://lists.apache.org/thread.html/a72dbd9103489058562f26a943f7f584e10a0cd04e0e5f69b00c0e49@%3Cdev.calcite.apache.org%3E <https://lists.apache.org/thread.html/a72dbd9103489058562f26a943f7f584e10a0cd04e0e5f69b00c0e49@%3Cdev.calcite.apache.org%3E> > On Feb 16, 2018, at 10:25 AM, Jesus Camacho Rodriguez <jcama...@apache.org> > wrote: > > Calcite 1.15.0 was released on December 11 (more than two months ago). > We have solved over 50 issues since then, hence I think we should start > discussing about releasing Calcite 1.16.0 (I can be release manager if > nobody else steps up). > > I have created [1] to keep track. > > CALCITE-2027 (dropping JDK7 support) was targeted for 1.16.0. Julian, > Michael, you have been working on that issue, could you share the > current status? > Any other particular features that people would like to include? > > -Jesús > > [1] https://issues.apache.org/jira/browse/CALCITE-2181 > >
