ephraimbuddy commented on code in PR #28521: URL: https://github.com/apache/airflow/pull/28521#discussion_r1061473740
########## dev/README_RELEASE_AIRFLOW.md: ########## @@ -41,6 +41,7 @@ - [Summarize the voting for the Apache Airflow release](#summarize-the-voting-for-the-apache-airflow-release) - [Publish release to SVN](#publish-release-to-svn) - [Prepare PyPI "release" packages](#prepare-pypi-release-packages) + - [Manually release API clients](#manually-release-api-clients) Review Comment: Sorry for not commenting. Here's my take: Releasing the API client together with Airflow sounds good but how do we determine that an API client should be released for a particular Airflow patch release? It's not clear from this PR, I think we should state it clearly. Also, I haven't looked at the API client release process, did we document the processes for their release somewhere? @pierrejeambrun I will ping you so we both work on the next release when it's time. -- 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]
