potiuk commented on code in PR #28521: URL: https://github.com/apache/airflow/pull/28521#discussion_r1061060744
########## 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: Agree. We should get to follow the reelease process and figure out all the edge case specifics. We were (are) doing it continuously. Pretty much every time we find missing/wrong pieces of the process to follow and we find out what needs to be improved - we've done through that with @eladkal for providers and that was a really helpful exercise to add some really good clarifications and improvements. BTW. maybe that is a good idea @pierrejeambrun you do the next release for Airflow with those instructions in? Similarly to what we've done with @eladkal on providers that might be helpful to go through that with @ephraimbuddy and others explaining all the questions and doubts, so that we could add some clarifications and get rid of some assumptions we have in our heads. This is encouraged by the ASF release management policies to have rotation for release management duty and people taking turns and the release manager does not have to be a PMC member - being commiter is enough https://www.apache.org/legal/release-policy.html -- 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]
