Github user srowen commented on the issue:
https://github.com/apache/spark/pull/18780
@gatorsmile @tdas to rehash the logic here:
- JIRAs track 'what' needs to happen, and PRs track a 'how' it could be
fixed. Closing a PR shouldn't necessarily mean an important issue is forgotten.
- The PR remains visible and open for comment
- PRs can be reopened at any time, or forked, by anyone
- There's too much to review, yes, and open stale PRs harm visibility into
active issues
- This is indeed a process right here for calling attention to a few issues
that need a look; thanks for looking
- Just say the word if there's any doubt about a PR and it will stay open.
This is a lightweight reaping process
I'd be careful of falling into the trap of thinking that, because something
looks important, but nobody has thought it important enough to look at in a
long time, that leaving it open somehow increases the chance that Someone will
work on it. It has never worked that way in the history of software projects.
I personally would rather close more aggressively, and if that looks like
bad news, address why all these important things aren't getting done: need more
committers? discouraged contributors? Too much complexity? how to get long-time
contributors to become more active again?
This mechanism is just a messenger. But still let's just stick to closing
the ones that nobody objects to.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional commands, e-mail: reviews-h...@spark.apache.org
