potiuk commented on code in PR #27613: URL: https://github.com/apache/airflow/pull/27613#discussion_r1021986122
########## airflow/providers/airbyte/CHANGELOG.rst: ########## @@ -24,6 +24,25 @@ Changelog --------- +3.2.0 +..... + +This release of provider is only available for Airflow 2.3+ as explained in the Apache Airflow +providers support policy https://github.com/apache/airflow/blob/main/README.md#support-for-providers + +Misc +~~~~ + +* ``Move min airflow version to 2.3.0 for all providers (#27196)`` Review Comment: But - just to comment on that as well @jedcunningham - I thought also why I am doing it this way. There is another good reason why we should release them all at least this time (but we can think about changing it in the future). Releasing "all" providers in such cases is simply much simpler and less risky and error-prone for me as release manager. Currently you would have to manually go through pretty much all those packages and find out where minor upgrade is beacuase we have "bump" and where there are "real features". It's just way more work for me and the kind of work is far more prone to manual mistakes (unless we automate this scenario somehow, which makes it far more stresful - because being perfectiionist, I will likely have to check it 4 or five times if I made any manual mistake or not. And knowing myself some mistake will slip through anyway. I am simply human. So If we are to do that, I would likely have to first implement some automation to do it, otherwise I will find myself in a situation that I do not really like, where I have a working, automated process which has a number of safeguards in place that will prevent from making stupid mistakes. And likely it's better to do it for the next wave. -- 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]
