You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@kafka.apache.org by "Grant Henke (JIRA)" <ji...@apache.org> on 2016/04/27 19:35:13 UTC
[jira] [Updated] (KAFKA-3630) Consider auto closing outdated pull
requests
[ https://issues.apache.org/jira/browse/KAFKA-3630?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Grant Henke updated KAFKA-3630:
-------------------------------
Description:
Currently we don't have access to close pull requests and the list of open pull requests is growing. We are nearing 200 open pull requests and many are outdated.
I am not sure if this is possible but I think a potential improvement would be to have a Jenkins job that runs periodically to:
1. Find all pull requests that have had no activity for 15 days
2. Comment on the pull requests that they were auto closed and should be re-opened if there is still interest
3. Close the pull requests
I don't think closing the outdated pull request will hurt project progress in anyway because:
- Jira still tracks the feature or fix
- The pull requests likely need a rebase or feedback needs to be address
- The notification will encourage the pull request owner and reviewers to follow up
As of today the break down of older pull requests is:
- [Older than 15 days|https://github.com/apache/kafka/pulls?utf8=%E2%9C%93&q=is%3Apr+is%3Aopen+updated%3A%3C%3D2016-04-12+]: 153
- [Older than 30 days|https://github.com/apache/kafka/pulls?utf8=%E2%9C%93&q=is%3Apr+is%3Aopen+updated%3A%3C%3D2016-03-28]: 107
- [Older than 60 days|https://github.com/apache/kafka/pulls?utf8=%E2%9C%93&q=is%3Apr+is%3Aopen+updated%3A%3C%3D2016-02-28+]: 73
- [Older than 90 days|https://github.com/apache/kafka/pulls?utf8=%E2%9C%93&q=is%3Apr+is%3Aopen+updated%3A%3C%3D2016-01-28+]: 52
This jira is mainly to track discussion and ideas around this challenge. Please feel free to propose an alternate solution.
was:
Currently we don't have access to close pull requests and the list of open pull requests is growing. We are nearing 200 open pull requests and many are outdated.
I am not sure if this is possible but I think a potential improvement would be to have a Jenkins job that runs periodically to:
1. Find all pull requests that have had no activity for 15 days
2. Comment on the pull requests that they were auto closed and should be re-opened if there is still interest
3. Close the pull requests
I don't think closing the outdated pull request will hurt project progress in anyway because:
- Jira still tracks the feature or fix
- The pull requests likely need a rebase or feedback needs to be address
- The notification will encourage the pull request owner and reviewers to follow up
As of today the break down of older pull requests is:
- [Older than 15 days|https://github.com/apache/kafka/pulls?utf8=%E2%9C%93&q=is%3Apr+is%3Aopen+updated%3A%3C%3D2016-04-12+]: 153
- [Older than 30 days|https://github.com/apache/kafka/pulls?utf8=%E2%9C%93&q=is%3Apr+is%3Aopen+updated%3A%3C%3D2016-03-28]: 107
- [Older than 90 days|https://github.com/apache/kafka/pulls?utf8=%E2%9C%93&q=is%3Apr+is%3Aopen+updated%3A%3C%3D2016-01-28+]: 52
This jira is mainly to track discussion and ideas around this challenge. Please feel free to propose an alternate solution.
> Consider auto closing outdated pull requests
> --------------------------------------------
>
> Key: KAFKA-3630
> URL: https://issues.apache.org/jira/browse/KAFKA-3630
> Project: Kafka
> Issue Type: Improvement
> Reporter: Grant Henke
>
> Currently we don't have access to close pull requests and the list of open pull requests is growing. We are nearing 200 open pull requests and many are outdated.
> I am not sure if this is possible but I think a potential improvement would be to have a Jenkins job that runs periodically to:
> 1. Find all pull requests that have had no activity for 15 days
> 2. Comment on the pull requests that they were auto closed and should be re-opened if there is still interest
> 3. Close the pull requests
> I don't think closing the outdated pull request will hurt project progress in anyway because:
> - Jira still tracks the feature or fix
> - The pull requests likely need a rebase or feedback needs to be address
> - The notification will encourage the pull request owner and reviewers to follow up
> As of today the break down of older pull requests is:
> - [Older than 15 days|https://github.com/apache/kafka/pulls?utf8=%E2%9C%93&q=is%3Apr+is%3Aopen+updated%3A%3C%3D2016-04-12+]: 153
> - [Older than 30 days|https://github.com/apache/kafka/pulls?utf8=%E2%9C%93&q=is%3Apr+is%3Aopen+updated%3A%3C%3D2016-03-28]: 107
> - [Older than 60 days|https://github.com/apache/kafka/pulls?utf8=%E2%9C%93&q=is%3Apr+is%3Aopen+updated%3A%3C%3D2016-02-28+]: 73
> - [Older than 90 days|https://github.com/apache/kafka/pulls?utf8=%E2%9C%93&q=is%3Apr+is%3Aopen+updated%3A%3C%3D2016-01-28+]: 52
> This jira is mainly to track discussion and ideas around this challenge. Please feel free to propose an alternate solution.
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)