potiuk commented on PR #27642: URL: https://github.com/apache/airflow/pull/27642#issuecomment-1317903474
Yes. We would need to generate documentation and release it. This is part of the Release process for Airflow: https://github.com/apache/airflow/blob/main/dev/README_RELEASE_AIRFLOW.md We have no separate "doc only" release process for Airflow (we have it for doc-only providers). If we would like to change it in "airflow-site" it would have to be either: a) wait for and make sure it is released as part of the next Airflow release (that's one more reason why it should be a part of the release process - so that we do not forget to upgrade and relase the Python and Go API clients as well when we are releasing 2.5.0) b) we would have to introduce new variant of process of releasing doc-only update for airflow - this could be done by simply cherry-picking the doc changes to latest vX-Y--test and releasing documentation from that branch @jedcunningham @ephraimbuddy -> I think this is more relevant to your side of it so I think you need to have a say here -- 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]
