[PROPOSAL] Improved compatiblity checks for Providers (running unit tests for multiple airflow versions)

Hello everyone, As part of preparation for the Airflow 3 move and (possible) provider separation (I have some ideas how to do it but that should be a separate discussion) I took on the task of improving our compatibility tests for Providers. I discussed it briefly with Kaxil and Ash and decided

Re: [VOTE] Proposal for adding Telemetry via Scarf

+1 binding. Made some comments to the draft PR. Sent from Outlook for iOS From: Kaxil Naik Sent: Thursday, May 9, 2024 4:12:32 AM To: dev@airflow.apache.org Subject: [VOTE] Proposal for adding Telemetry via Scarf Hi all, Discussion

Re: [VOTE] Proposal for adding Telemetry via Scarf

+1 binding From: Jed Cunningham Sent: Thursday, May 9, 2024 7:59:03 AM To: dev@airflow.apache.org Subject: RE: [EXTERNAL] [COURRIEL EXTERNE] [VOTE] Proposal for adding Telemetry via Scarf CAUTION: This email originated from outside of the organization. Do not

Re: [VOTE] Proposal for adding Telemetry via Scarf

+1 binding

Re: [VOTE] Proposal for adding Telemetry via Scarf

+1 non-binding On Thu, May 9, 2024 at 7:17 AM Tomasz Urbaszek wrote: > +1 binding > > On Thu, 9 May 2024 at 12:40, Andrey Anshin > wrote: > > > +1 binding > > > > > > > > > > > > On Thu, 9 May 2024 at 13:25, Wei Lee wrote: > > > > > Got it. Thanks Jarek for pointing out! > > > > > > Best, > >

Re: [VOTE] Proposal for adding Telemetry via Scarf

+1 binding On Thu, 9 May 2024 at 12:40, Andrey Anshin wrote: > +1 binding > > > > > > On Thu, 9 May 2024 at 13:25, Wei Lee wrote: > > > Got it. Thanks Jarek for pointing out! > > > > Best, > > Wei > > > > > On May 9, 2024, at 3:59 PM, Ankit Chaurasia > wrote: > > > > > > +1 non-binding > > >

Re: [VOTE] Proposal for adding Telemetry via Scarf

+1 binding On Thu, 9 May 2024 at 13:25, Wei Lee wrote: > Got it. Thanks Jarek for pointing out! > > Best, > Wei > > > On May 9, 2024, at 3:59 PM, Ankit Chaurasia wrote: > > > > +1 non-binding > > > > *Ankit Chaurasia* > > > > > > > > > > > > > > On Thu, May 9, 2024 at 11:16 AM Aritra Basu

Re: [VOTE] Proposal for adding Telemetry via Scarf

Got it. Thanks Jarek for pointing out! Best, Wei > On May 9, 2024, at 3:59 PM, Ankit Chaurasia wrote: > > +1 non-binding > > *Ankit Chaurasia* > > > > > > > On Thu, May 9, 2024 at 11:16 AM Aritra Basu > wrote: > >> +1 non-binding >> >> -- >> Regards, >> Aritra Basu >> >> On Thu, May

Re: [HUGE DISCUSSION] Airflow3 and tactical (Airflow 2) vs strategic (Airflow 3) approach

Thanks for initiating this discussion @Kaxil Naik ! Read through the document and the emails here and I like the direction in which we are proceeding. I also agree that removing code is almost as important as adding code. We need to have a clear checklist of what we want to remove and get a

Re: [VOTE] AIP-67 Multi-team deployment of Airflow components

I agree with whatever decision comes out of this conversation going forward. I personally think the below option is the best given the fact that we might be doing Airflow 3 with a certain theme in mind: *only implement multi-team as an Airflow 3 feature (which might be mucheasier to do -

Re: [VOTE] AIP-67 Multi-team deployment of Airflow components

Just to clarify the state for that one. I would like to put that one on-hold until we get clarity on Airflow 2 vs Airflow 3 approach: https://lists.apache.org/thread/3chvg9964zvh15mtrbl073f4oj3nlzp2 There is currently a veto from Ash, so until it is withdrawn or we change the problematic "team"

Re: [VOTE] Proposal for adding Telemetry via Scarf

+1 non-binding *Ankit Chaurasia* On Thu, May 9, 2024 at 11:16 AM Aritra Basu wrote: > +1 non-binding > > -- > Regards, > Aritra Basu > > On Thu, May 9, 2024, 10:36 AM Amogh Desai > wrote: > > > +1 binding > > > > Thanks & Regards, > > Amogh Desai > > > > > > On Thu, May 9, 2024 at 10:29 

Re: [HUGE DISCUSSION] Airflow3 and tactical (Airflow 2) vs strategic (Airflow 3) approach

Strong agree - I think one of the things I regret most about Airflow 2 was that we didn't remove enough. It probably eased the upgrade process for users though. > but I was hoping one day when we remove providers > from main development, I can do it personally and beat Ash to it. Grrr ;l The