potiuk commented on PR #27946: URL: https://github.com/apache/airflow/pull/27946#issuecomment-1328227719
I reviewed and clarified (it's clearere and simpler I hope) the description of the API verification processs in the README_API.md. I've also added the "Possible future work" chapter explaining how results of experimenting with API in the `common.sql` might be eventually converted into much more comprehensive tool for internal `API` verification. This might be not only for cross-provider dependencies but also for `providers` -> `Airflow core` dependencies eventually. We've been discussing it several times before, and from those discussions, I think having such comprehensive API "snapshot" and "verification" tooling is a prerequisite for the future splitting of providers to separate repos (if we decide to do that of course). Eventually e might give external provider developers a tool to verify if the providers they develop, are API-level compatible with certain versions (+) of the Apache Airflow. With approach similar to what I described, we might not only be able to finally be able to tell "Those are the official Airflow classes/methods you can use and rely on" but also have a mechanism for provider developers to use them - we will be able to test those for our providers (once/if we split them in a separate repository. -- 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]
