+1 for release at end of August. +1 to figure out which PRs could make it into the release, and work on that list in FIFO order. We tend to merge PRs that are in good shape, and by active contributors, and we tend to ignore old PRs that are never going to make it, but we tend to ignore the important PRs in the middle.
Julian > On Jul 21, 2019, at 2:28 AM, Stamatis Zampetakis <zabe...@gmail.com> wrote: > > 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
