Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Further clarify triage process #40536

Merged
merged 3 commits into from
Jul 2, 2024
Merged

Further clarify triage process #40536

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
c0bb957
Further clarify triage process
eladkal Jul 2, 2024
6274b50
update
eladkal Jul 2, 2024
d52c851
update
eladkal Jul 2, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
17 changes: 17 additions & 0 deletions ISSUE_TRIAGE_PROCESS.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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
Expand Down