potiuk commented on pull request #15969: URL: https://github.com/apache/airflow/pull/15969#issuecomment-845141052
> The functools ones don't require provider releases since the old imports will still work, the new Airflow version will only add a shortcut to do the same thing. Not really. It also means that when we release new providers (they are always released from master) they will not work with the old versions of airflow that have no `airflow.compat` package. The only `sane` way of doing it is making those changes first (adding compat) to airflow and then at some point of time when releasing providers switching to it with >= <airflow_version_with_compat>. Which I think we should do. But I'd reserve it for major versions of Airflow. As soon as we release 2.1 version of airflow we will add-back the check where all providers are built and installed with old version of airlflow (we temporarily removed it before releasing 2.1 and adding "apply_default" incompatibility in the same way), but it will be 2.1 now) - and in this case you will get a failing job. This way we will prevent from accidental usage of this compat in providers (until we decide new wave of providers is >=2.2 for example). -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: [email protected]
