>
> Since I was called :)
As though you needed to be called to chime in ;)
Yeah and the other thing that your comments made me think of was... how it
could make provider management more challenging. Because though currently
we have min_airflow_version set in providers and we can use that to
Hi All,
I have created a new feature request here. Looking forward to any thoughts
on this?
https://github.com/apache/airflow/issues/33793
With Best Regards,
Dipayan Dev
And to clarify, when I talk about putting pressure on major releases, what
I mean is that there's this notion that a major release has to have some
very special or big feature change. One reason offered is marketing.
Major release is an opportunity to market airflow, so take advantage of
that.
For whatever reason, I was reminded recently of snowflake's "behavior
change" policy
See here: https://docs.snowflake.com/en/release-notes/behavior-change-policy
I think semver is problematic for core because basically you cannot
implement behavior changes until the "mythical" major release.
