potiuk commented on code in PR #28521: URL: https://github.com/apache/airflow/pull/28521#discussion_r1059948166
########## 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: And another example of issue that is likely caused by outdated client of ours (thought it is hard to say because it almost looks like no-one actually cares about the Python client so far). https://github.com/apache/airflow/pull/28521 I hope by getting this one sorted out will help us to avoid the situation where the client is sort of abandonded even if we as a community release it. I believe bringing it to the repo, and making it part of the release process is the only way we can improve the situation, otherwise it looks like we are neglecting our users - we have an API that was highly requested, which is really part of the "core" offering of Airflow but we neglect it. That situation actually makes me think that we should possibly NOT split providers to separate repositories because we might end up in e similar situation. I will certainly use this as an example when we discuss it. But that's a side comment only. -- 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]
