+1 I’ve poked Khai Tran re. 3122 (Pig).
> On Aug 16, 2019, at 11:20 PM, Stamatis Zampetakis <zabe...@gmail.com> wrote: > > Hi all, > > The release is advancing quite well, yet we have 22 issues marked for > 1.21.0 [1]. > > From those, the following 5 seem to be the most important: > > https://issues.apache.org/jira/browse/CALCITE-1581 > https://issues.apache.org/jira/browse/CALCITE-2302 > https://issues.apache.org/jira/browse/CALCITE-3122 > https://issues.apache.org/jira/browse/CALCITE-3224 > https://issues.apache.org/jira/browse/CALCITE-3228 > > I will try to have an RC for the 26th of August so let's try to get them in. > > [1] > https://issues.apache.org/jira/secure/Dashboard.jspa?selectPageId=12333950 > > On Thu, Aug 1, 2019 at 8:51 AM Danny Chan <yuzhao....@gmail.com> wrote: > >> Let’s get the CALCITE-2302[1]: the full implicit type cast support into >> 1.21 ! >> >> [1] https://github.com/apache/calcite/pull/706 >> >> Best, >> Danny Chan >> 在 2019年7月21日 +0800 PM3:28,Stamatis Zampetakis <zabe...@gmail.com>,写道: >>> Hi all, >>> >>> Approximately one month has passed from the previous release (Calcite >>> 1.20.0) and I was thinking that it would be nice to have the next release >>> out by the end of August. To do this I think we should try to have an RC >>> around the 20 of August. >>> >>> The progress towards the next release can be seen in [1]. As you can >>> observe we do not have many issues marked for fixing for 1.21.0 but we do >>> have many pull requests. >>> >>> I would like to invite committers to go over the existing PRs and for >> those >>> that we plan to review and finalize in the next month or so set the fix >>> version to 1.21.0 adding an appropriate comment. >>> >>> In term of priorities, I think we should emphasize on finalizing and >>> merging PRs that are blocking other open source projects and commercial >>> products from upgrading to the latest release. If it is not already done >>> please assign this issues the highest priority (blocker) and set the fix >>> version to 1.21.0. >>> >>> Apart from very important issues it makes sense to treat PRs in FIFO >> order. >>> Contributors who submit a PR early will certainly get discouraged to >>> contribute again if we never merge these PRs in time. >>> >>> Don't hesitate to reply to this thread if the plan above is not >> convenient >>> for you! >>> >>> Best, >>> Stamatis >>> >>> [1] >>> >> https://issues.apache.org/jira/secure/Dashboard.jspa?selectPageId=12333950 >>