+1 on early deprecation in next 2.10. But it is mostly about providers - In the core we just need to clean the "if/special cases". And such cleaning would be then the target in 3.0
If 1.16 of the chart closes the gap, there should be no blocker in my view to have a 100% replacement in 3.0 w/o the need to carry legacy. On 19.02.25 15:54, Jed Cunningham wrote:
I agree with Niko - chart support shouldn't be a hard line for experimental/stable for core features. We should get it into a released chart though :) It hasn't gotten enough attention from me recently. That said, I am close to cutting 1.16.0. I love the idea of removing hybrid support for 3. Couldn't we do the "stable" switch (removing that it's experimental from docs) and hybrid deprecations in the next 2.10 as well? I know we typically do those in minors, but earlier the better probably at this stage.
--------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@airflow.apache.org For additional commands, e-mail: dev-h...@airflow.apache.org
