This is an automated email from the ASF dual-hosted git repository.
shahar 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 8a109dbcb11 Update issue templates regarding Airflow 2 and misc.
(#59384)
8a109dbcb11 is described below
commit 8a109dbcb11f2edaa6255f543b0a8d37466cb439
Author: Shahar Epstein <[email protected]>
AuthorDate: Sun Dec 14 23:19:31 2025 +0200
Update issue templates regarding Airflow 2 and misc. (#59384)
---
.github/ISSUE_TEMPLATE/1-airflow_bug_report.yml | 27 ++++++++++++++++------
.github/ISSUE_TEMPLATE/2-feature_request.yml | 17 ++++++++++----
.../3-airflow_providers_bug_report.yml | 19 ++++++++++++---
.../4-airflow_helmchart_bug_report.yml | 17 ++++++++++++--
.../ISSUE_TEMPLATE/5-airflow_doc_issue_report.yml | 4 ++++
5 files changed, 67 insertions(+), 17 deletions(-)
diff --git a/.github/ISSUE_TEMPLATE/1-airflow_bug_report.yml
b/.github/ISSUE_TEMPLATE/1-airflow_bug_report.yml
index f162c0ec7e8..49b648dfcad 100644
--- a/.github/ISSUE_TEMPLATE/1-airflow_bug_report.yml
+++ b/.github/ISSUE_TEMPLATE/1-airflow_bug_report.yml
@@ -15,29 +15,42 @@ body:
Note, you do not need to create an issue if you have a change ready to
submit!
You can open a [pull request](https://github.com/apache/airflow/pulls)
immediately instead.
+
+ Please note that reporting a bug does not guarantee it will be fixed,
as the implementation depends
+ on community interest and availability.
+ Therefore, please do not request or expect specific timelines or ETAs.
The fastest way to fix bugs is
+ to submit a PR yourself.
+
+ For reporting security issues in any version, please **do not** use
this form and refer to the
+ [Security Reporting
Guidelines](https://github.com/apache/airflow/blob/main/.github/SECURITY.md)
+ instead.
<br clear='left'/>"
# yamllint enable rule:line-length
- type: dropdown
attributes:
label: Apache Airflow version
description: >
- What Apache Airflow version are you using? If you do not see your
version, please (ideally) test on
- the latest release or main to see if the issue is fixed before
reporting it.
+ Select your Airflow version.
+ **Please note:** Airflow 2.x is in limited support (critical and
security fixes only), and reaches
+ EOL on April 22, 2026 - see the
+ [Airflow 2 EOL page]
+
(https://airflow.apache.org/docs/apache-airflow/stable/installation/supported-versions.html)
+ for more information.
multiple: false
options:
- "3.1.5"
- - "2.11.0"
+ - "2.11.X"
- "main (development)"
- - "Other Airflow 2/3 version (please specify below)"
+ - "Other Airflow 3 version (please specify below)"
validations:
required: true
- type: input
attributes:
- label: If "Other Airflow 2/3 version" selected, which one?
+ label: If "Other Airflow 3 version" selected, which one?
# yamllint disable rule:line-length
description: >
- On what 2.X version of Airflow are you currently experiencing the
issue? Remember, you are encouraged to
- test with the latest release or on the main branch to verify your
issue still exists, especially if
+ On what 3.X version of Airflow are you currently experiencing the
issue? Remember, you are encouraged to
+ test with the latest release or on the `main` branch to verify your
issue still exists, especially if
your version is at least a minor version older than the [current
stable
release](https://airflow.apache.org/docs/apache-airflow/stable/installation/supported-versions.html#version-life-cycle).
# yamllint enable rule:line-length
- type: textarea
diff --git a/.github/ISSUE_TEMPLATE/2-feature_request.yml
b/.github/ISSUE_TEMPLATE/2-feature_request.yml
index 402417c4088..e32dae293e4 100644
--- a/.github/ISSUE_TEMPLATE/2-feature_request.yml
+++ b/.github/ISSUE_TEMPLATE/2-feature_request.yml
@@ -12,9 +12,12 @@ body:
We really appreciate the community efforts to improve Airflow.
- Features should be small improvements that do not dramatically change
Airflow assumptions.
- Note, that in this case you do not even need to create an issue if you
have a code change ready to submit!
- You can open [Pull Request](https://github.com/apache/airflow/pulls)
immediately instead.
+ Features suggested via this form should be small to medium
improvements that do not dramatically change Airflow assumptions.
+ Note that if you have a code change ready to submit - you don't need
to create an feature request
+ and can instead open a [Pull
Request](https://github.com/apache/airflow/pulls) directly.
+ However, if you don't have the time or the knowledge to implement the
feature yourself, this form is the right place to suggest it.
+ Please note that suggesting a feature does not guarantee it will be
implemented, and any implementation depends on community interest and
availability.
+ Therefore, please do not request or expect specific timelines or ETAs.
The fastest way to get new features is to submit a PR yourself.
For bigger features, those that are impacting Airflow's architecture,
security assumptions,
backwards compatibility etc. should be discussed in the [airflow
devlist](https://lists.apache.org/[email protected]).
@@ -24,8 +27,12 @@ body:
among the community and eventually conduct a successful
[vote](https://www.apache.org/foundation/voting.html) in the community.
- If unsure - open a
[discussion](https://github.com/apache/airflow/discussions) first to gather
- an initial feedback on your idea.
+ **Please note:** Airflow 2.x is in limited support (critical and
security fixes only), and reaches
+ EOL on April 22, 2026.
+ For reporting security issues in any version, please **do not** use
this form and refer to the [Security Reporting
Guidelines](https://github.com/apache/airflow/blob/main/.github/SECURITY.md)
instead.
+
+ If unsure about the impact of your feature or how to formulate it -
please open a [discussion](https://github.com/apache/airflow/discussions) first
to gather
+ an initial feedback on your idea, or ask in the other [communication
channels](https://airflow.apache.org/community/).
<br clear='left'/>"
diff --git a/.github/ISSUE_TEMPLATE/3-airflow_providers_bug_report.yml
b/.github/ISSUE_TEMPLATE/3-airflow_providers_bug_report.yml
index 844ea18ea4d..4dc8cdce326 100644
--- a/.github/ISSUE_TEMPLATE/3-airflow_providers_bug_report.yml
+++ b/.github/ISSUE_TEMPLATE/3-airflow_providers_bug_report.yml
@@ -15,6 +15,10 @@ body:
Note, you do not need to create an issue if you have a change ready to
submit!
You can open a [pull request](https://github.com/apache/airflow/pulls)
immediately instead.
+
+ Please note that reporting a bug does not guarantee it will be fixed,
as the implementation depends
+ on community interest and availability.
+ Therefore, please do not request or expect specific timelines or ETAs.
The fastest way to fix bugs is to submit a PR yourself.
<br clear='left'/>"
# yamllint enable rule:line-length
- type: dropdown
@@ -125,14 +129,23 @@ body:
- type: textarea
attributes:
label: Versions of Apache Airflow Providers
- description: What Apache Airflow Providers versions are you using?
+ description: >
+ What Apache Airflow Providers versions are you using?
+ For reporting security issues in any version, please **do not** use
this form and refer to the
+ [Security Reporting
Guidelines](https://github.com/apache/airflow/blob/main/.github/SECURITY.md)
+ instead.
placeholder: You can use `pip freeze | grep apache-airflow-providers`
(you can leave only relevant ones)
- type: input
attributes:
label: Apache Airflow version
description: >
- What Apache Airflow version are you using?
- [Only Airflow 2 is
supported](https://github.com/apache/airflow#version-life-cycle) for bugs.
+ Enter your Airflow version.
+ **Please note:** Airflow 2.x is in limited support (critical and
security fixes only), and reaches
+ EOL on April 22, 2026 - see the
+ [Airflow 2 EOL page]
+
(https://airflow.apache.org/docs/apache-airflow/stable/installation/supported-versions.html)
+ for more information.
+ When using 2.x, please test with the latest 2.11.x; also consider
testing with Airflow 3 or `main`.
validations:
required: true
- type: input
diff --git a/.github/ISSUE_TEMPLATE/4-airflow_helmchart_bug_report.yml
b/.github/ISSUE_TEMPLATE/4-airflow_helmchart_bug_report.yml
index 64efe5ac16a..07d7352e6cb 100644
--- a/.github/ISSUE_TEMPLATE/4-airflow_helmchart_bug_report.yml
+++ b/.github/ISSUE_TEMPLATE/4-airflow_helmchart_bug_report.yml
@@ -19,6 +19,15 @@ body:
Note, you do not need to create an issue if you have a change ready to
submit!
You can open a [pull request](https://github.com/apache/airflow/pulls)
immediately instead.
+
+ Please note that reporting a bug does not guarantee it will be fixed,
as the implementation depends
+ on community interest and availability.
+ Therefore, please do not request or expect specific timelines or ETAs.
The fastest way to fix bugs is
+ to submit a PR yourself.
+
+ For reporting security issues in any version, please **do not** use
this form and refer to the
+ [Security Reporting
Guidelines](https://github.com/apache/airflow/blob/main/.github/SECURITY.md)
+ instead.
<br clear='left'/>"
# yamllint enable rule:line-length
- type: dropdown
@@ -55,8 +64,12 @@ body:
attributes:
label: Apache Airflow version
description: >
- What Apache Airflow version are you using?
- [Only Airflow 2 is
supported](https://github.com/apache/airflow#version-life-cycle) for bugs.
+ Select your Airflow version.
+ **Please note:** Airflow 2.x is in limited support (critical and
security fixes only), and reaches EOL
+ on April 22, 2026 - see the
+ [Airflow 2 EOL page]
+
(https://airflow.apache.org/docs/apache-airflow/stable/installation/supported-versions.html)
+ for more information.
validations:
required: true
- type: input
diff --git a/.github/ISSUE_TEMPLATE/5-airflow_doc_issue_report.yml
b/.github/ISSUE_TEMPLATE/5-airflow_doc_issue_report.yml
index 50e6c9ac1df..b3f6c2bb19f 100644
--- a/.github/ISSUE_TEMPLATE/5-airflow_doc_issue_report.yml
+++ b/.github/ISSUE_TEMPLATE/5-airflow_doc_issue_report.yml
@@ -15,6 +15,10 @@ body:
Note, you do not need to create an issue if you have a change ready to
submit!
You can open a [pull request](https://github.com/apache/airflow/pulls)
immediately instead.
+
+ Please note that reporting a doc issue does not guarantee it will be
fixed, as prioritization and implementation depend on impact, severity, and
community availability.
+ Therefore, please do not request or expect specific timelines or ETAs.
Remember that the fastest way to fix documentation issues is to submit a PR
yourself.
+
<br clear='left'/>"
# yamllint enable rule:line-length
- type: textarea
