From c0bb957da0945508bc5d84be2b7e1e907dd74efb Mon Sep 17 00:00:00 2001
From: Elad Kalif <45845474+eladkal@users.noreply.github.com>
Date: Tue, 2 Jul 2024 08:47:39 +0300
Subject: [PATCH 1/3] Further clarify triage process

---
 ISSUE_TRIAGE_PROCESS.rst | 15 +++++++++++++++
 1 file changed, 15 insertions(+)

diff --git a/ISSUE_TRIAGE_PROCESS.rst b/ISSUE_TRIAGE_PROCESS.rst
index e4217ae0c812d..90be56461c68a 100644
--- a/ISSUE_TRIAGE_PROCESS.rst
+++ b/ISSUE_TRIAGE_PROCESS.rst
@@ -260,6 +260,21 @@ 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`` is mandatory for core issues thus it always comes with ``area:core`` label.
+When issue is reproducible on multiple Airflow versions we apply only the latest version with the label.
+
 **Good First Issue**
 
 Issues which are relatively straight forward to solve, will be tagged with

From 6274b5001ebd2ed9d72312bf06e7455d48f1b3ce Mon Sep 17 00:00:00 2001
From: Elad Kalif <45845474+eladkal@users.noreply.github.com>
Date: Tue, 2 Jul 2024 09:25:47 +0300
Subject: [PATCH 2/3] update

---
 ISSUE_TRIAGE_PROCESS.rst | 1 +
 1 file changed, 1 insertion(+)

diff --git a/ISSUE_TRIAGE_PROCESS.rst b/ISSUE_TRIAGE_PROCESS.rst
index 90be56461c68a..d6a69d376e4a7 100644
--- a/ISSUE_TRIAGE_PROCESS.rst
+++ b/ISSUE_TRIAGE_PROCESS.rst
@@ -274,6 +274,7 @@ This method allow us to quickly filter issues by the 3 major components of our c
 
 The ``affected_version:x`` is mandatory for core issues thus it always comes with ``area:core`` label.
 When issue is reproducible on multiple Airflow versions we apply only the latest version with the label.
+The ``affected_version:x`` will never be present with ``kind:feature`` as feature requests are not related to specific Airflow version.
 
 **Good First Issue**
 

From d52c851038226408dcad6edaa344b75fbf7d9410 Mon Sep 17 00:00:00 2001
From: Elad Kalif <45845474+eladkal@users.noreply.github.com>
Date: Tue, 2 Jul 2024 17:31:45 +0300
Subject: [PATCH 3/3] update

---
 ISSUE_TRIAGE_PROCESS.rst | 5 +++--
 1 file changed, 3 insertions(+), 2 deletions(-)

diff --git a/ISSUE_TRIAGE_PROCESS.rst b/ISSUE_TRIAGE_PROCESS.rst
index d6a69d376e4a7..a80c431afb52a 100644
--- a/ISSUE_TRIAGE_PROCESS.rst
+++ b/ISSUE_TRIAGE_PROCESS.rst
@@ -272,9 +272,10 @@ This method allow us to quickly filter issues by the 3 major components of our c
 
 **affected version Label**
 
-The ``affected_version:x`` is mandatory for core issues thus it always comes with ``area:core`` label.
-When issue is reproducible on multiple Airflow versions we apply only the latest version with the 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**