potiuk commented on code in PR #27613: URL: https://github.com/apache/airflow/pull/27613#discussion_r1022033110
########## 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: Just to give a very good example of propblems if we do not release "all" providers. Real example from just now. Before rebase I am doing now) someone merged: * ``Replace urlparse with urlsplit (#27389)`` This change is a non-breaking, non feature, "misc" kind of change, that we - regardless - shoud put in the release docs and release, just in case this caused some problems or changes we are not aware of (it's not a bugfix, not a feature, but it changes code so potentially we should be able to explain that it was the reason when someone has some problems. But this change was touching 7 providers. This means that it *could* have changed whether we release a provider or no (previously it was min-version only, now it became min-version + urlparse). Should we release it now ? I think yes - the longer we wait with realeasing any code change the better. If we hold with relasing of provider that already has some "code" change" - then if we release it in 3 months we might have detect some problems that we could hve detected 3 months earlier. By having "release all changed in any way except documentation" providers I free myself from having to review each of those manually and decide - I release this/I do not release that. Currently we automatically skip from release only providers that have "doc-only changes" - for those we only regenerate the documentation. And this is all automated. If we were to decide "and we do not realease also that change" - we would have to implement automation for exclusion of those changes. -- 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]
