kaxil opened a new pull request, #74056:
URL: https://github.com/apache/airflow/pull/74056

   The bug report and feature request templates still say Airflow 2 "reaches 
EOL on April 22, 2026". That date has passed, and the README now lists Airflow 
2 as EOL, where "EOL versions will not get any fixes nor support". The bug 
template now says Airflow 2 has reached end of life and asks reporters to check 
their issue on Airflow 3 before filing. Of the 1,071 open issues, 94 are bug 
reports filed against Airflow 2.
   
   It also fixes the supported-versions link in the bug template. The 
description is a folded YAML block, so the line break between `[Airflow 2 EOL 
page]` and `(https://...)` became a space and the Markdown link never rendered.
   
   ---
   
   * Read the **[Pull Request 
Guidelines](https://github.com/apache/airflow/blob/main/contributing-docs/05_pull_requests.rst#pull-request-guidelines)**
 for more information. Note: commit author/co-author name and email in commits 
become permanently public when merged.
   * For fundamental code changes, an Airflow Improvement Proposal 
([AIP](https://cwiki.apache.org/confluence/display/AIRFLOW/Airflow+Improvement+Proposals))
 is needed.
   * When adding dependency, check compliance with the [ASF 3rd Party License 
Policy](https://www.apache.org/legal/resolved.html#category-x).
   * For significant user-facing changes create newsfragment: 
`{pr_number}.significant.rst`, in 
[airflow-core/newsfragments](https://github.com/apache/airflow/tree/main/airflow-core/newsfragments).
 You can add this file in a follow-up commit after the PR is created so you 
know the PR number.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to