I don't really have a vote here, but I've been attempting to mentor some folks on how to get engaged and the PR backlog is very daunting, and signals that their contributions will get lost in the noise. So I'm in favor of this. I recognize that it will cause some active PRs to be closed, but this is a one-way door. Those people will be notified and the close message should be crafted in such a manner as to encourage them to reengage and reopen if the contribution is still valid and they are still interested.
Rich On Fri, Aug 29, 2025, 03:14 Xiaoqiao He <hexiaoq...@apache.org> wrote: > Hi All, > > I try to launch this thread again, and propose to close stale PRs at Github > which was updated over 100 days ago. > > There are 1180 open PRs at Github[1], which is unfriendly for reviewers or > someone who wants to be involved to review here. > > I see that we have discussed many times, including [2],[3], but there are > no more concrete follow-ups or conclusions. And there are many Apache > projects have been adopted this way for years such as Apache Spark[4], > So IMO, there will be no more blockers now. > > One thing left I didn't think it through, the related JIRA should keep > synchronized to close? Look forward to hearing more thoughts. > BTW, I think related JIRA close or not should be another thing and > it doesn't block Github Action for stale PRs. > Thanks all. > > Best Regards, > - He Xiaoqiao > > [1] https://github.com/apache/hadoop/pulls > [2] https://lists.apache.org/thread/fdnj065koh7cjgxbk4jxthlpycmo4tm7 > [3] https://lists.apache.org/thread/6g3n4wo3b3tpq2qxyyth3y8m9z4mcj8p > [4] > https://github.com/apache/spark/blob/master/.github/workflows/stale.yml >
