All for it :) . I think we are getting closer to have regular planning and
making some structured approach to 2.0 and starting task force for it soon,
so I think this should be perfectly fine to discuss and even start
implementing what's beyond as soon as we make sure that we are prioritizing
2.0 w
Hi Jarek,
I agree we should not change the behaviour of the existing SubDagOperator
till Airflow 2.1. Is it okay to continue the discussion about TaskGroup as
a brand new concept/feature independent from the existing SubDagOperator?
In other words, shall we add TaskGroup as a UI grouping concept l
I think it describes very well what we discussed so far. I have two points
to add:
1) Using Milestone:
I prefer to keep milestones to only mark stuff for global releases of
Airflow and nothing else. If we use Milestones for SIG groups this will
become unmanageable (and I know Milestones are used
Hello everyone,
We started to gather automatically stats about the quarantined tests:
The issue below gets automatically updated with the status of
quarantined issues and hopefully, it will let us track and fix the
flakiness status quarantined tests rather than let them stay in the
quarantine:
h
