Jens Scheffler

Thanks for the contribution! w/o having a full review I assume you should mark the legacy API as being migrated like e.g. in https://github.com/apache/airflow/pull/42798/files#diff-df829fc289eeca0e932974a5110a8f2c21b1962e87db7c3a3b44dacf084f54a1R47 ?

> Hi @jscheffl, since this API is migrated from the home view in `airflow/www/views.py,` and `dag_tags` is just a small part of the home view, I'm not sure if this...

I think your proposal is meaningful - whereas I am wondering what problems with Postgres are leading to this in-consistency. I think this should be addressed first. (1) You should...

Might be related to proposal in #44536 - I'd propose to have (at least parameters) in common

Thanks for the contribution! As we are discussing the new i18n challnges and alongside a required policy in https://lists.apache.org/thread/d8grrtqg2p1mpcccqqozg9ld9pnn8zf2 I assume we should at least consider the points which have...

Mis-understood the docs/apache-airflow/installation/supported-versions.rst:55 - no backport...

@potiuk for getting this into 2.11... in `dev/README_AIRFLOW3_DEV.md` there is no definition... which target merge branch to be used as "parking lot" for 2.11? Is `v2-10-test`correct? There is no v2-11-test...

Note before merge: Last 3 commits from PR #42766 are not on this back-port (yet). Backport was cut before review completed.

> Note before merge: Last 3 commits from PR #42766 are not on this back-port (yet). Backport was cut before review completed. DONE.

> Just as a comment to remind in the future - python version in the check_python_version script from #43282 (back-ported in #43310) will also need to be updated before we...