458 open PRs and climbing — the review backlog is out of control #2170
Replies: 2 comments
-
|
Hi, I understand your concern, but keep in mind we're a small team working on this in our free time. Many of the PRs we receive are one-off submissions, duplicates, or AI-generated with poor-to-medium quality. Contributors often don't respond to our reviews, or they just submit more AI-generated code instead. If you want things to move faster, don't pressure us. Instead, contribute your time and effort to help confirm issues, test PRs, and review them. Thanks and regards |
Beta Was this translation helpful? Give feedback.
-
|
@KuSh could you please following with the review of #874. I blink faster the PR and I didn't see any vulnerability added or not standard implementation. This feature will help us a lot with PHP stuffs. Thanks a lot for your attention and your work with this project. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Let's be blunt: there are 458 open PRs and 565 open issues, and the number keeps going up, not down. The queue is growing faster than it's being cleared, and at this point the backlog is effectively unreviewable.
A lot of these are small, self-contained bug fixes — green CI, no conflicts — that have sat untouched for weeks. People take the time to track down a real bug, open a clean PR, and then... nothing. That's not sustainable, and honestly it's a great way to burn through contributor goodwill. Why fix anything if it just rots in a 400-deep pile?
This needs an actual plan, not silence. Concretely:
The longer this sits, the more contributors quietly walk away. Can the maintainers commit to a concrete plan — and a rough timeline — for getting this under control?
Beta Was this translation helpful? Give feedback.
All reactions