[
https://issues.apache.org/jira/browse/SPARK-1739?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14207112#comment-14207112
]
Josh Rosen commented on SPARK-1739:
---
My proposal would be to have SparkQA post a comment in the PR that mentions the
component maintainers. This could happen once a PR sits inactive or unreviewed
for more than X days. I can do this myself, but I'm kind of overloaded with
other work so this is going to be a low priority. I'd welcome pull requests
for this, though: https://github.com/databricks/spark-pr-dashboard
Close PR's after period of inactivity
-
Key: SPARK-1739
URL: https://issues.apache.org/jira/browse/SPARK-1739
Project: Spark
Issue Type: Task
Components: Project Infra
Reporter: Patrick Wendell
Assignee: Josh Rosen
Sometimes PR's get abandoned if people aren't responsive to feedback or it
just falls to a lower priority. We should automatically close stale PR's in
order to keep the queue from growing infinitely.
I think we just want to do this with a friendly message that says This seems
inactive, please re-open this if you are interested in contributing the
patch.. We should also explicitly ping any reviewers (via @mentioning) them
and ask them to provide feedback one way or the other, for instance, if the
feature is being rejected.
This will help us avoid letting features slip through the cracks by forcing
some action when there is no activity after 30 days. Also, it's ASF policy
that we should really be tracking our feature backlog and prioritization in
JIRA and only be using Github for active reviews.
I don't think we should close it if there was _no_ feedback from any reviewer
- in that case we should leave it open (we should be providing at least some
feedback on all incoming patches).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: issues-unsubscr...@spark.apache.org
For additional commands, e-mail: issues-h...@spark.apache.org
