I suggest keeping master closed to get some resources on this important issue. Yes, it is a form of blackmail.
On Tue, May 12, 2020 at 8:26 PM Chunwei Lei <[email protected]> wrote: > > There're some PRs which have been a long time. I suggest closing some of > them if nobody are working on it. > But I don't figure out why we should keep the master branch closed. To > avoid conflict? > > > Best, > Chunwei > > > On Wed, May 13, 2020 at 2:22 AM Julian Hyde <[email protected]> wrote: > > > I noticed that yesterday Haisheng removed the ‘fix in 1.23’ labels from > > several JIRA cases. I support this - we need to get a release out - but I > > don’t want to lose the fact that many of these cases had PRs and were ready > > to merge to master. > > > > We all know that we have a backlog of PRs. There are good contributions > > that are not being merged to master because we have too few reviewers. > > > > I would like to propose a solution. After 1.23 is released, keep the > > master branch closed until we have gone through the backlog of PRs. (Not > > all PRs, just those that were tagged ‘fix for 1.23’. And we don’t have to > > merge them all - we can reject them if not ready.) > > > > Committers who work on Calcite daily will have a strong incentive to work > > on other peoples’ PRs. > > > > If there are other suggestions for addressing this problem, I would like > > to hear them. > > > > Julian > > > >
