[jira] [Updated] (FLINK-37533) Reduce Stale PR Action timeouts

["ASF GitHub Bot (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/FLINK-37533?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

ASF GitHub Bot updated FLINK-37533:
-----------------------------------
    Labels: pull-request-available  (was: )

> Reduce Stale PR Action timeouts
> -------------------------------
>
>                 Key: FLINK-37533
>                 URL: https://issues.apache.org/jira/browse/FLINK-37533
>             Project: Flink
>          Issue Type: Improvement
>            Reporter: Thomas Cooper
>            Priority: Not a Priority
>              Labels: pull-request-available
>
> [FLINK-37026|https://issues.apache.org/jira/browse/FLINK-37026] enabled the Stale PR GitHub Action and this has been running successfully for several months, [labelling PRs older than 6 months as "stale"|https://github.com/apache/flink/labels/stale].
> The initial time-outs for the Stale PR action were 6 months inactive with 3 further months of no action before closing. This was done to give time for PR authors to react to the new action. However, during the [discussion|https://lists.apache.org/thread/6yoclzmvymxors8vlpt4nn9r7t3stcsz] it was suggested that 3 months inactive with 1 month to respond was the typical configuration used on other Apache projects and should also be used for Flink. It was decided to start with longer time-outs and move to the standard ones once the stability of the action was confirmed.
> Now that the action has been running for some time with no issues, we should reduce the time-outs to the proposed Apache standard configuration. This will allow us to start clearing the oldest stale PRs.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)