Re: [DISCUSS] Airflow 2/3 providers versioning support

2024-08-20 Thread Amogh Desai
That looks quite good to me because as per the below quote from you: > Assuming that we release Airflow 3.0.0 in March 2025, if we follow this rule, we will be able to drop Airflow 2 support in providers in March 2026 - so we give about a year to Airflow 2 users to migrate to Airflow 3 - if they w

Re: [DISCUSS] Airflow 2/3 providers versioning support

2024-08-16 Thread Jarek Potiuk
Yes. Agree with Ash that when we have "sdk" that will be all-but-guaranteed (or at least intended to be) backwards compatible and no DB access from workers, or DAG processor, then yes we can change the rules for Airflow 3 going forward, but Airflow 2 support question remains. Basically it boils do

Re: [DISCUSS] Airflow 2/3 providers versioning support

2024-08-15 Thread Ash Berlin-Taylor
Going forward with Airflow 3 I also think we should re-consider what we version/depend upon from providers. If we move all providers (and likley also utility functions!) out of airflow core then the thing that a given provider needs to depend upon is the shared library/provider versions and the

Re: [DISCUSS] Airflow 2/3 providers versioning support

2024-08-15 Thread Amogh Desai
Nice points to ponder upon, Jarek. Both topics are essential for ensuring that users have a clear path forwars. > We currently guarantee that the minimum Airflow version supported by a provider is the release date of the next minor version, plus 12 months. You’re asking if this should be adjusted

Re: [DISCUSS] Airflow 2/3 providers versioning support

2024-08-14 Thread Jarek Potiuk
> We currently guarantee that the minimum Airflow version supported by a provider is the release date of the next minor version, plus 12 months. You’re asking if this should be adjusted for Airflow 3, correct? Yes > Are you asking for guarantees the other way around, so Airflow version -> guarant

Re: [DISCUSS] Airflow 2/3 providers versioning support

2024-08-14 Thread Bas Harenslak
Sorry I’m a bit lost in the long text. Is my understanding of the 2 questions correct? We currently guarantee that the minimum Airflow version supported by a provider is the release date of the next minor version, plus 12 months. You’re asking if this should be adjusted for Airflow 3, correct?

[DISCUSS] Airflow 2/3 providers versioning support

2024-08-14 Thread Jarek Potiuk
Hello everyone, I have two important topics to discuss regarding Provider <> Airflow version support rules. *1) What is the "min Airflow version" support while we are transitioning to Airflow 3? * So far we had the [1] rule: > The default support timespan for the minimum version of Airflow (the