This is an automated email from the ASF dual-hosted git repository.
eladkal 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 90a6d7f9ea Further clarify triage process (#40536)
90a6d7f9ea is described below
commit 90a6d7f9ead21bebc750baf38817a8f1600b3d17
Author: Elad Kalif <[email protected]>
AuthorDate: Tue Jul 2 17:49:29 2024 +0300
Further clarify triage process (#40536)
* Further clarify triage process
* update
* update
---
ISSUE_TRIAGE_PROCESS.rst | 17 +++++++++++++++++
1 file changed, 17 insertions(+)
diff --git a/ISSUE_TRIAGE_PROCESS.rst b/ISSUE_TRIAGE_PROCESS.rst
index e4217ae0c8..a80c431afb 100644
--- a/ISSUE_TRIAGE_PROCESS.rst
+++ b/ISSUE_TRIAGE_PROCESS.rst
@@ -260,6 +260,23 @@ as long as the ``needs-triage`` label remains the triage
team will keep an eye o
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.
+**area Label**
+
+``area:providers`` must be present for any provider issue. The ``provider:x``
is specifying the exact provider.
+We have ``provider:x`` for any provider that we own.
+``area:helm-chart`` must be for any helm chart issue.
+``area:core`` must be for any core issue. Additional labels like
``area:scheduler``, ``area:UI`` is specifying the exact
+core area relevant.
+
+This method allow us to quickly filter issues by the 3 major components of our
code base: core, providers and helm-chart.
+
+**affected version Label**
+
+The ``affected_version:x`` will never be present with ``kind:feature`` as
feature requests are not related to specific Airflow version.
+For bugs, The ``affected_version:x`` is expected to be used with core issues
thus normally it appears with ``area:core`` label.
+When issue is reproducible on multiple Airflow versions we apply only the
latest version with the label.
+This policy is best effort, we should try to have as little exceptions as
possible.
+
**Good First Issue**
Issues which are relatively straight forward to solve, will be tagged with
