jscheffl opened a new pull request, #63217: URL: https://github.com/apache/airflow/pull/63217
As I was spending a significant time with the team today to find-out that the `max_active_tasks` parameter has semantically changed in Airflow 3 compared to Airflow 3 and the name stayed the same, being mis-leading, this PR improves the pydoc at least hoping that others will not run into the same problem. References: - https://lists.apache.org/thread/nn4y1z0yrydkmw9np4f0z5lm9gh8tmfl - https://lists.apache.org/thread/9o84d3yn934m32gtlpokpwtbbmtxj47l - https://github.com/apache/airflow/pull/42953 FYI @AutomationDev85 @clellmann --- ##### Was generative AI tooling used to co-author this PR? <!-- If generative AI tooling has been used in the process of authoring this PR, please change below checkbox to `[X]` followed by the name of the tool, uncomment the "Generated-by". --> - [ ] No (please specify the tool below) <!-- Generated-by: [Tool Name] following [the guidelines](https://github.com/apache/airflow/blob/main/contributing-docs/05_pull_requests.rst#gen-ai-assisted-contributions) --> --- * 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]
