potiuk commented on code in PR #27613: URL: https://github.com/apache/airflow/pull/27613#discussion_r1021714813
########## 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: Yes I think we should because otherwise we will have to selectively do it every time when we will track any change that is 2.3 incompatible. It makes it much cleaner and easier to manage and creates far less overhead when preparing the release wave. And It gives the user no more burden - most of the users are upgrading together with Airlfow - which means that they will automatically use the new providers. It also provides a much better starting point in the future when we will have to (for example for security reasons) release a catastrofic fix in a proivider that should be installed for pre-2.2 version. We know exactly where to branch off, we still have patch-levels to use for that. Most of our users do not follow and release providers when they are released (and we don't even encourage it). The big benefit of releasing provideres independently, is that the users CAN do that when they want. Also releasing it now gives a strong signal - there will be no more feature releases for all providers with pre-2.3 version. There will be at most bugfixes. If we don't upgrade now, there is still an option to release feature version for those providers that is not 2.2 compatible, which we shoudl not do any more. And this is yet another signal to our users that they should upgrade to Airflow 2.3 asap. So yes - I think releasing all providers now makes perfect sense. Mostly that this is a clear communication "no more feature provider releases that will support Airflow 2.2" -- 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]
