potiuk commented on code in PR #28521: URL: https://github.com/apache/airflow/pull/28521#discussion_r1061563500
########## 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: The release process (for python client) is here: https://github.com/apache/airflow-client-python#release-process for go client is here: https://github.com/apache/airflow-client-go#release-process I think the we can determine the need of building it comes from: a) changes/fixes in openapi specification (internal) b) available releases of newer version of open-api generator (external) If we all agree this is a good idea, I am also happy to move the whole generation as a automated CI process (so that we automatically check out the latest generator and run the package build entirely from `apache-airflow` repository - also for Go Client (as discussed in https://github.com/apache/airflow/pull/28521#discussion_r1059948166 I think the currrent approach is not really good because we commit generated code without being able to check the code). -- 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]
