This is an automated email from the ASF dual-hosted git repository.
potiuk pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/airflow.git
The following commit(s) were added to refs/heads/main by this push:
new dae7bf0800 Update issue triage policy (#29554)
dae7bf0800 is described below
commit dae7bf080025a8e535a86fc588b84d0b3e294ffd
Author: eladkal <[email protected]>
AuthorDate: Mon Feb 20 11:37:50 2023 +0200
Update issue triage policy (#29554)
---
.github/ISSUE_TEMPLATE/airflow_bug_report.yml | 2 +-
.../ISSUE_TEMPLATE/airflow_doc_issue_report.yml | 2 +-
.../airflow_helmchart_bug_report.yml | 2 +-
.../airflow_providers_bug_report.yml | 2 +-
.github/ISSUE_TEMPLATE/feature_request.yml | 2 +-
.github/workflows/stale.yml | 19 +++++++++++++++++++
ISSUE_TRIAGE_PROCESS.rst | 22 +++++++++++++++++++---
7 files changed, 43 insertions(+), 8 deletions(-)
diff --git a/.github/ISSUE_TEMPLATE/airflow_bug_report.yml
b/.github/ISSUE_TEMPLATE/airflow_bug_report.yml
index 6280a37f34..aa3fa29c18 100644
--- a/.github/ISSUE_TEMPLATE/airflow_bug_report.yml
+++ b/.github/ISSUE_TEMPLATE/airflow_bug_report.yml
@@ -1,7 +1,7 @@
---
name: Airflow Bug report
description: Problems and issues with code in Apache Airflow core
-labels: ["kind:bug", "area:core"]
+labels: ["kind:bug", "area:core", "needs-triage"]
body:
- type: markdown
attributes:
diff --git a/.github/ISSUE_TEMPLATE/airflow_doc_issue_report.yml
b/.github/ISSUE_TEMPLATE/airflow_doc_issue_report.yml
index 0977e98221..5b97840b5d 100644
--- a/.github/ISSUE_TEMPLATE/airflow_doc_issue_report.yml
+++ b/.github/ISSUE_TEMPLATE/airflow_doc_issue_report.yml
@@ -1,7 +1,7 @@
---
name: Airflow Doc issue report
description: Problems and issues with Apache Airflow documentation
-labels: ["kind:bug", "kind:documentation"]
+labels: ["kind:bug", "kind:documentation", "needs-triage"]
body:
- type: markdown
attributes:
diff --git a/.github/ISSUE_TEMPLATE/airflow_helmchart_bug_report.yml
b/.github/ISSUE_TEMPLATE/airflow_helmchart_bug_report.yml
index 19e4cf5917..78d0e9f63f 100644
--- a/.github/ISSUE_TEMPLATE/airflow_helmchart_bug_report.yml
+++ b/.github/ISSUE_TEMPLATE/airflow_helmchart_bug_report.yml
@@ -1,7 +1,7 @@
---
name: Airflow Helm Chart Bug report
description: Problems and issues with the Apache Airflow Official Helm Chart
-labels: ["kind:bug", "area:helm-chart"]
+labels: ["kind:bug", "area:helm-chart", "needs-triage"]
body:
- type: markdown
attributes:
diff --git a/.github/ISSUE_TEMPLATE/airflow_providers_bug_report.yml
b/.github/ISSUE_TEMPLATE/airflow_providers_bug_report.yml
index 99ca0b5236..756fd1cffe 100644
--- a/.github/ISSUE_TEMPLATE/airflow_providers_bug_report.yml
+++ b/.github/ISSUE_TEMPLATE/airflow_providers_bug_report.yml
@@ -1,7 +1,7 @@
---
name: Airflow Providers Bug report
description: Problems and issues with code in Apache Airflow Providers
-labels: ["kind:bug", "area:providers"]
+labels: ["kind:bug", "area:providers", "needs-triage"]
body:
- type: markdown
attributes:
diff --git a/.github/ISSUE_TEMPLATE/feature_request.yml
b/.github/ISSUE_TEMPLATE/feature_request.yml
index 837a88f698..21ed060802 100644
--- a/.github/ISSUE_TEMPLATE/feature_request.yml
+++ b/.github/ISSUE_TEMPLATE/feature_request.yml
@@ -1,7 +1,7 @@
---
name: Airflow feature request
description: Suggest an idea for this project
-labels: ["kind:feature"]
+labels: ["kind:feature", "needs-triage"]
body:
- type: markdown
attributes:
diff --git a/.github/workflows/stale.yml b/.github/workflows/stale.yml
index 1dff613a5e..08c40b978d 100644
--- a/.github/workflows/stale.yml
+++ b/.github/workflows/stale.yml
@@ -47,3 +47,22 @@ jobs:
activity occurs from the issue author.
close-issue-message: >
This issue has been closed because it has not received response
from the issue author.
+ recheck-old-bug-report:
+ runs-on: ubuntu-20.04
+ steps:
+ - uses: actions/stale@v7
+ with:
+ only-issue-labels: 'kind:bug'
+ stale-issue-label: 'Stale Bug Report'
+ days-before-issue-stale: 365
+ days-before-issue-close: 30
+ remove-stale-when-updated: true
+ labels-to-add-when-unstale: 'needs-triage'
+ stale-issue-message: >
+ This issue has been automatically marked as stale because it has
been open for 365 days
+ without any activity. There has been several Airflow releases
since last activity on this issue.
+ Kindly asking to recheck the report against latest Airflow version
and let us know
+ if the issue is reproducible. The issue will be closed in next 30
days if no further activity
+ occurs from the issue author.
+ close-issue-message: >
+ This issue has been closed because it has not received response
from the issue author.
diff --git a/ISSUE_TRIAGE_PROCESS.rst b/ISSUE_TRIAGE_PROCESS.rst
index ef79a0276e..9870c3ade3 100644
--- a/ISSUE_TRIAGE_PROCESS.rst
+++ b/ISSUE_TRIAGE_PROCESS.rst
@@ -251,9 +251,14 @@ the label ``pending-response``.
Also, during this stage, additional labels may be added to the issue to help
classification and triage, such as ``affected_version`` and ``area``.
-Some issues may need a detailed review by one of the core committers of the
project
-and this could be tagged with a ``needs:triage`` label.
-
+New issues are automatically assigned with ``needs-triage`` label. This labels
goal
+is to help us detect issues that are waiting for initial triage. The label
will be removed by the triager
+once the issue is accepted (and assigned with relevant kind and area labels).
This sometimes can take a while as we might
+ask for other members of the community for consultation or ask for further
information from the issue author.
+Removing the ``needs-triage`` label means that the issue has been accepted and
awaits implementation (no further triage action required),
+as long as the ``needs-triage`` label remains the triage team will keep an eye
on the issue and check periodically
+if it needs to be accepted or closed/converted to Github Discussion.
+``needs-triage`` label may also be applied manually by committers if they
think a further action from the triage team is required.
**Good First Issue**
@@ -307,3 +312,14 @@ we normally convert such issues to discussions in the
Ideas category.
Issues that seems more like support requests are also converted to discussions
in the Q&A category.
We use judgment about which Issues to convert to discussions, it's best to
always clarify with a comment why the issue is being converted.
Note that we can always convert discussions back to issues.
+
+
+**Stale Policy **
+
+As time passes bug reports that have been accepted may be out dated.
+Bot will scan older bug reports and if the report is inactive it will comment
+and ask the author to recheck if the bug is still reproducible on latest
version.
+If the issue is reconfirmed triage team will check if labels needs to be
updated (for example: ``reported_version`` label)
+If no one respond after some time, we will consider the issue as resolved (may
have already been fixed) and bot will resolve the issue.
+The exact timeframes for each one of the actions is subject to change from
time to time.
+The updated values can be checked in ``.github/workflow`` where we define the
bots policy.
