Re: [DISCUSSION] Make one of the next provider waves (January or February) 2.3+ only for all providers

One other solution for just using "utils" from core is we can release "airflow.backports" or "airflow.futures" package same as Python Backports and Python Future where we can handle the compat shim without restricting Airflow

Re: [DISCUSSION] Make one of the next provider waves (January or February) 2.3+ only for all providers

> At this point, I think 2.3.0 will be around early Feb to get AIP-42 in. We > can reassess how the progress is moving ahead with the AIP mid-Jan and based > on that we can either release 2.3.0 end of Jan without AIP-42 changes and > mark it for 2.4.0. Yeah Agree here. I do not think we need to

Re: [DISCUSSION] Make one of the next provider waves (January or February) 2.3+ only for all providers

> Regarding the KPO -- I think we should be able to release a version > compatible with Airflow 2.2.x . Is it 2.2.0+ or 2.1.0+ (this is the current min-version) ? Or maybe 2.2.4+ ? J.

Re: [DISCUSSION] Make one of the next provider waves (January or February) 2.3+ only for all providers

Regarding the KPO -- I think we should be able to release a version compatible with Airflow 2.2.x . At this point, I think 2.3.0 will be around early Feb to get AIP-42 in. We can reassess how the progress is moving ahead with the AIP *mid-Jan* and based on that we can either release 2.3.0 end of J

[DISCUSSION] Make one of the next provider waves (January or February) 2.3+ only for all providers

Hello Everyone, We are close to the 2.3.0 release and we are starting to accumulate changes that make the maintenance of Airflow 2.1 compatibility in Providers more and more difficult. We implemented a lot of changes in the Airflow core that we could take advantage of that we are not able to now (