[GitHub] [airflow] potiuk commented on a diff in pull request #28521: Update doc for API clients release policy

[GitBox <gi...@apache.org>]

potiuk commented on code in PR #28521:
URL: https://github.com/apache/airflow/pull/28521#discussion_r1059795673


##########
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:
   I think in this case we should VOTE on a bundle of the Airflow + Client. There is no particular need to have a separate vote for each artifact. Similarly as in case of providers - where we vote on many artifacts and we can verify and test a number of them. And If we find a problem in some of them, release manager can remove some of the artifacts from the release and ask for RC2 for only those fixed artifacts.
   
   Nowhere in the release procedure of the ASF it is written that the vote should be on one artifact at a time.
   
   But in this case I think we have another problem to solve.
   
   I think all our API clients should come directly from airlow  they shoudl all come even from the same source package. The source package of Airflow should be enough to generate not only Apache Airflow package, but also the clients. 
   
   This is another point that I am raising in https://github.com/apache/airflow-client-go/pull/28



-- 
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: commits-unsubscribe@airflow.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org