Bumping the major version of the providers is only half the story --
what is the behaviour if someone has pins
apache-airflow-providers-foo==1.0.0 and installs apache-airflow==2.1 --
pip check wouldn't complain but the code might not work?
That's far from ideal.
Ah, looking at the PR linked up thread , I would call this is more an
issue off forward compat, rather than back compat, so the issue is that
we want to release providers that need a feature that only exists in
2.1, and for any such provider, we will bump the major version.
Have I understood correctly, and more importantly, providers of v1 will
continue to work with Airflow 2.1?
-ash
On Wed, 14 Apr, 2021 at 22:31, Daniel Standish <dpstand...@gmail.com>
wrote:
The proposal to bump major for all providers with every core minor
version seems like a reasonable solution to me, and it sounds like
there may be consensus on that? Though eventially the version
numbers may get pretty large :)
This discussion came to my attiontion from engagement with the vault
secrets enhancement
<https://github.com/apache/airflow/pull/15013/files>. Looking at
this as a test case for this question, to implement this change while
maintaining compatibility with 2.0.0 would require an unacceptable
amount of code duplication and mess. And it's a relatively simple
change (so we can imagine it being much worse in other instances).
