We have 174 open PRs. Quite a few of these are high-quality and ready to go in, and they are not from committers, so they don't stand a chance unless a committer takes the time to look at them. New contributors will become demoralized if they do good work and it is never looked at.
In the next 5 days, could every committer review one or two PRs, and merge it to master if it is ready? You would be doing your part to keep our community healthy and growing. Julian On Thu, Jul 9, 2020 at 11:26 AM Julian Hyde <jh...@apache.org> wrote: > > Chunwei, > > Thanks for kicking this off. RC on 7/14 sounds good. > > I have logged https://issues.apache.org/jira/browse/CALCITE-4117 > ("Release Calcite 1.24.0") and assigned it to you. I have a couple of > bugs that I want to make depend on it (i.e. they can only be fixed > AFTER 1.24). > > On Wed, Jul 8, 2020 at 11:25 PM Chunwei Lei <chunwei.l...@gmail.com> wrote: > > > > Hi all, > > > > Approximately one and a half months have passed from the previous release > > (Calcite > > 1.23.0) and I was thinking that it would be nice to have the next release > > around the 20 > > of July, considering there are already ~70 commits and some commits of > > pull#2024[1] > > to be merged after 1.24 is large and easy to be broken. To do this I think > > we should try > > to have an RC around the 14 of July. > > > > The progress towards the next release can be seen in [2]. As you can see, > > we have 10 > > issues marked for fixing in 1.24.0. I suggest we focus on solving these > > issues in the > > following days. Apart from these issues, if you really think other issues > > should be fixed > > in 1.24.0, please comment in this thread and set the fix version to 1.24.0. > > > > Don't hesitate to reply to this thread if the plan above is not convenient > > for you! > > > > [1] https://github.com/apache/calcite/pull/2024 > > [2] > > https://issues.apache.org/jira/secure/Dashboard.jspa?selectPageId=12333950 > > > > > > Best, > > Chunwei
