We are about three weeks before RC0 and we still have a big number of pending PRs. Moreover there are only a few Jira cases that are marked to be fixed in 1.21.0.
If we assume that we have 10 active committers at the moment and each one of them takes on ~5 PRs till the 20th of August, we should have at least 50 Jiras marked to be resolved for the next version. I would like to kindly ask people to go through the PRs, select those that are going to make it for 1.21.0, and set the fix version accordingly. At the moment we have resolved 46 issues in Jira [1]. It would be great if we could bring this number to 50 by 7th of August. I've seen that Enrico started another thread about regressions on 1.20.0. Let's try to attack this issues first to allow people upgrade to the latest release. Among the issues that we would like to include in 1.21.0, I would like to highlight the following: https://issues.apache.org/jira/browse/CALCITE-2302 https://issues.apache.org/jira/browse/CALCITE-3122 https://issues.apache.org/jira/browse/CALCITE-3142 Best, Stamatis [1] https://issues.apache.org/jira/secure/Dashboard.jspa?selectPageId=12333950 On Mon, Jul 22, 2019 at 1:56 PM Chunwei Lei <chunwei.l...@gmail.com> wrote: > +1 for release at end of August. > > > 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. > > +1 since it is very important for encouraging contributors. > > > > Best, > Chunwei > > > On Mon, Jul 22, 2019 at 9:19 AM Danny Chan <yuzhao....@gmail.com> wrote: > > > >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. > > > > There are 110+ PRs on the GitHub page, what should we do ? > > > > Best, > > Danny Chan > > 在 2019年7月22日 +0800 AM6:19，dev@calcite.apache.org，写道： > > > > > > 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. > > >
