Avatica has around 14 commits since the last release, but I think it
would be good to have a release to maintain release cadence.
I have been working on a script to automate most of the release in a
docker container and would like to get that in for this release (if
possible).
On 20/09/2018 9:26 AM, Julian Hyde wrote:
I have logged
* https://issues.apache.org/jira/browse/CALCITE-2576
<https://issues.apache.org/jira/browse/CALCITE-2576> Release Avatica 1.13
* https://issues.apache.org/jira/browse/CALCITE-2575
<https://issues.apache.org/jira/browse/CALCITE-2575> Release Calcite 1.18.0
On Sep 19, 2018, at 4:19 PM, Julian Hyde <[email protected]> wrote:
Calcite 1.17 was released on 20th July (2 months ago) and since then there have
been almost 100 commits.
Does anyone have constraints on when 1.18 should be released? (My opinion: we
should aim for 3 months after 1.17, and therefore we will need an RC before
10th October.)
Does anyone have any JIRA cases that they would like to get into 1.18 but they
have not yet finished?
Who would like to be release manager?
Do we need a new Avatica release before we make this Calcite release?
https://issues.apache.org/jira/browse/CALCITE-2467
<https://issues.apache.org/jira/browse/CALCITE-2467> describes one reason to do so:
jetty versions. Also, it would be nice if both projects used the new parent POM (see
https://issues.apache.org/jira/browse/CALCITE-2486
<https://issues.apache.org/jira/browse/CALCITE-2486>) but it’s not essential.
Julian
