Shuyi, I forgot to ask: What would be your preferred time-frame for the release?
Julian > On Feb 16, 2018, at 10:59 AM, Julian Hyde <jh...@apache.org> wrote: > > My preferred time-frame would be to start a vote on Mar 1 or soon after. So > we’d have a release by say Mar 10. That gives us 2 weeks to produce an > Avatica release. But I’m flexible - the release could happen a couple of > weeks later in March. > > In my queue I have the Geode and Jethro adapters. Both are almost ready to > commit - I just need to get clean test runs. I am interested in finishing > https://issues.apache.org/jira/browse/CALCITE-2160 > <https://issues.apache.org/jira/browse/CALCITE-2160> (a grid index to support > spatial joins) or at least some blocker issues regarding CROSS APPLY that I > ran into while working on this. > > Take a look at the pull request queue https://github.com/apache/calcite/pulls > <https://github.com/apache/calcite/pulls> - there are a lot of half-complete > PRs, more than usual. If the authors want make a concerted effort to complete > them before the release they should speak up now, and we can be flexible. > > Julian > >> On Feb 16, 2018, at 10:51 AM, Shuyi Chen <suez1...@gmail.com >> <mailto:suez1...@gmail.com>> wrote: >> >> I am working on https://issues.apache.org/jira/browse/CALCITE-2045 >> <https://issues.apache.org/jira/browse/CALCITE-2045> (Create >> Type DDL). I was hoping to get it in for 1.16. Do we have the deadline for >> the 1.16 feature cut? Thanks. >> >> On Fri, Feb 16, 2018 at 10:43 AM, Julian Hyde <jh...@apache.org >> <mailto:jh...@apache.org>> wrote: >> >>> 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> < >>> https://issues.apache.org/jira/browse/CALCITE-2182 >>> <https://issues.apache.org/jira/browse/CALCITE-2182>> >>> >>> [2] https://lists.apache.org/thread.html/a72dbd9103489058562f26a943f7f5 >>> <https://lists.apache.org/thread.html/a72dbd9103489058562f26a943f7f5> >>> 84e10a0cd04e0e5f69b00c0e49@%3Cdev.calcite.apache.org >>> <http://3cdev.calcite.apache.org/>%3E < >>> https://lists.apache.org/thread.html/a72dbd9103489058562f26a943f7f5 >>> <https://lists.apache.org/thread.html/a72dbd9103489058562f26a943f7f5> >>> 84e10a0cd04e0e5f69b00c0e49@%3Cdev.calcite.apache.org >>> <http://3cdev.calcite.apache.org/>%3E> >>> >>> >>>> On Feb 16, 2018, at 10:25 AM, Jesus Camacho Rodriguez < >>> jcama...@apache.org <mailto: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 >>>> <https://issues.apache.org/jira/browse/CALCITE-2181> >>>> >>>> >>> >>> >> >> >> -- >> "So you have to trust that the dots will somehow connect in your future." >
