ashb commented on issue #51545: URL: https://github.com/apache/airflow/issues/51545#issuecomment-2980038478
> * Testing strategy? How to test package combinations efficiently > > > There should not be combinations. All packages should have the same version and should be released together - even if there are no changes in particular distribution. They should have `==` pinned dependencies to other `apache-airflow` things. A tight coupling between task-sdk and any "server side" component is the opposite to one of the goals of AIP-72 (I'm not sure we ever explicitly said this, but the first point of motivation for the AIP says "Dependency conflicts for administrators supporting data teams using different versions of providers, libraries, or python packages") In short, my goal with TaskSDK, and the reason for introducing CalVer and Cadwyn with the execution API is to end up in a world where you can upgrade the Airflow Scheduler/API server interdependently of any worker nodes (with the exception that the server must be at least as new as the clients) This ability to have version-skew is pretty much non-negotiable to me and is (other than other languages) one of primary benefits of AIP-72 -- 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. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
