Re: [DISCUSS] Deprecate SubDags in favor of TaskGroups ?

One thing only here. While I am all for removing Sub-dags eventually, We either remove them in 2.0 or 3.0. We can't remove any functionality or change Airflow in a backwards-incompatible way in 2.X ( https://semver.org/#spec-item-8) We already agreed I believe, that we are using Semver

Re: [DISCUSS] Deprecate SubDags in favor of TaskGroups ?

I agree with Gerard on all fronts. SubDags are difficult, slow, and can cause a lot of strange edge cases. The difficulties in SubDags is a sticking point for Airflow competitors that I want to remove as quickly as possible. I think that 2.0 is a perfect time to introduce TaskGroups as people a

Re: [DISCUSS] Deprecate SubDags in favor of TaskGroups ?

Internally, we have blocked people from using SubDags due to its slowness and sometimes instability. I would vote for adding TaskGroups earliest as possible + remove documentation for SubDags (users can go to old versions of docs to find that) + add a notice of deprecation on new TaskGroup document

[DISCUSS] Deprecate SubDags in favor of TaskGroups ?

Hi all, One of the things we discussed on Monday's Airflow 2.0 Dev call was around *TaskGroups* - a new concept introduced by https://github.com/apache/airflow/pull/10153 (AIP-34