I see that Chunwei has just send out a [RESULT] email announcing that the vote has passed. This is the right decision, but it is a close call.
https://issues.apache.org/jira/browse/CALCITE-4136 <https://issues.apache.org/jira/browse/CALCITE-4136> was discovered during the release vote It is a complicated bug. The problem is real, but only occurs in certain circumstances (particular JDKs, loading classes in particular orders). But the problem is caused by our attempt to fix another bug and comply with semantic versioning - i.e. not removing APIs without prior notice. Therefore my recommendation is to release 1.24 RC0, include in the release notes the strong recommendation that people immediately replace calls to deprecated APIs, and that we release 1.25 as soon as possible afterwards. I’ll start a thread to discuss the release of 1.25. Julian > On Jul 23, 2020, at 12:21 AM, Chunwei Lei <[email protected]> wrote: > > Thanks to everyone who has tested the release candidate and given their > comments. > > I have revised the release notes and updated the LICENSE[1]. Regarding > CALCITE-4136[2], > I have not looked into it yet. But from what I can see, it is not a > blocking issue. > > > > [1] https://github.com/chunweilei/calcite/commits/branch-1.24-revised > [2] https://issues.apache.org/jira/browse/CALCITE-4136 > > > Best, > Chunwei > > > On Thu, Jul 23, 2020 at 9:43 AM Danny Chan <[email protected]> wrote: > >> Thanks Chunwei for taking care of the release ~ >> >> +1 (binding) >> - verified hashes and checksums >> - built from sources and run tests (1.8.0_161 on MacOS Mojave) >> - run some tests of Flink >> >> Best, >> Danny Chan >> 在 2020年7月22日 +0800 PM11:50，[email protected]，写道： >>> >>> +1 (non binding) >>> - verified hashes and checksums >>> - built from sources and run tests (JDK14 on Linux) >>> - run tests of HerdDB and some client application >>
