potiuk commented on PR #27642: URL: https://github.com/apache/airflow/pull/27642#issuecomment-1314431773
For API clients - we actually have agreed to the versioning where MINOR.MAJOR are the same where PATCHLEVEL are separated. For example API client Python version 2.4.1 and Go client 2.4.3 might both be "latest" versions of clients - covering all fixes (1 and 3 rounds of them) since 2.4.0 has been released. By definition all 2.4 versions of Airflow only contain bug-fixes, not features/breaking changes. See: https://github.com/apache/airflow#semantic-versioning > Airflow API clients: SemVer MAJOR and MINOR versions follow MAJOR and MINOR versions of Airflow. The first MAJOR or MINOR X.Y.0 release of Airflow should always be followed by X.Y.0 release of all clients. The clients then can release their own PATCH releases with bugfixes, independently of Airflow PATCH releases. Now - for API version itself, I feel we should do similar approach. - API 2.4 and any time we release any bugfix to API, we bump patchlevel -- 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]
