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

+1 binding and many thanks for the lively discussion and alignment! Get it going! Sent from Outlook for iOS From: Pierre Jeambrun Sent: Thursday, April 18, 2024 7:14:39 PM To: dev@airflow.apache.org Subject: Re: [VOTE] AIP-67 Multi-team de

Re: [DISCUSS] Proposal for adding Telemetry via Scarf

+1, looking forward to having better data!

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

+1 (binding) Le jeu. 18 avr. 2024 à 18:52, Ferruzzi, Dennis a écrit : > This is exciting. +1 binding. > > > - ferruzzi > > > > From: Oliveira, Niko > Sent: Thursday, April 18, 2024 9:16 AM > To: dev@airflow.apache.org > Subject: RE: [EXTERNAL] [COURRIEL EXTERN

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

This is exciting. +1 binding. - ferruzzi From: Oliveira, Niko Sent: Thursday, April 18, 2024 9:16 AM To: dev@airflow.apache.org Subject: RE: [EXTERNAL] [COURRIEL EXTERNE] [VOTE] AIP-67 Multi-team deployment of Airflow components CAUTION: This email originat

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

+1 binding Excited for this one! From: Aritra Basu Sent: Thursday, April 18, 2024 7:37:08 AM To: dev@airflow.apache.org Subject: RE: [EXTERNAL] [COURRIEL EXTERNE] [VOTE] AIP-67 Multi-team deployment of Airflow components CAUTION: This email originated from outs

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

+1 (non-binding) -- Regards, Aritra Basu On Thu, Apr 18, 2024, 7:42 PM Bishundeo, Rajeshwar wrote: > +1 (non-binding) > > -- Rajesh > > > > > > > On 2024-04-18, 10:11 AM, "Vincent Beck" vincb...@apache.org>> wrote: > > > CAUTION: This email originated from outside of the organization. Do not

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

+1 (non-binding) -- Rajesh On 2024-04-18, 10:11 AM, "Vincent Beck" mailto:vincb...@apache.org>> wrote: CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you can confirm the sender and know the content is safe. AVERTISSE

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

+1 binding On 2024/04/18 11:10:32 Jarek Potiuk wrote: > Hello here. > > I have not not heard a lot of feedback after my last update, so let me > start a vote, hoping that the last changes proposed addressed most of the > concerns. > > Just to recap. the proposal is here: > https://cwiki.apache.o

Re: [DISCUSS] Consider disabling self-hosted runners for commiter PRs

The change is merged, rebasing should trigger maintainers PRs using public runners. they should be able to switch to "self-hosted" by "use self hosted runners" label. The `main` and `v2-9-test` runs should still be run using self-hosted runners. I would love to hear back from the maintainers if th

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

Hello here. I have not not heard a lot of feedback after my last update, so let me start a vote, hoping that the last changes proposed addressed most of the concerns. Just to recap. the proposal is here: https://cwiki.apache.org/confluence/display/AIRFLOW/AIP-67+Multi-team+deployment+of+Airflow+c

Re: [VOTE] Airflow Providers prepared on April 16, 2024

+1 (binding): checked reproducibility, licences, signatures, checksums - all look good. On Thu, Apr 18, 2024 at 12:27 PM Pankaj Singh wrote: > +1 (non-binding) tested my changes. > > Thanks > Pankaj > > > > On Wed, Apr 17, 2024 at 12:24 PM Amogh Desai > wrote: > > > +1 non binding > > > > Teste

Re: [VOTE] Airflow Providers prepared on April 16, 2024

+1 (non-binding) tested my changes. Thanks Pankaj On Wed, Apr 17, 2024 at 12:24 PM Amogh Desai wrote: > +1 non binding > > Tested few example DAGs with cncf. Works fine. > > Thanks & Regards, > Amogh Desai > > > On Wed, 17 Apr 2024 at 12:21 PM, Pankaj Koti > wrote: > > > +1 (non-binding) Con

Re: [CALL FOR HELP] Help on Connexion 3 migration needed

Just to make it clear I marked this PR as Draft - and I would really appreciate some comments about the approach and direction (in the light of Connexion 2 being dead-end holding us from security-related upgrades and generally holding us back). Surely - there are things to be improved in this PR,

Re: [DISCUSS] Consider disabling self-hosted runners for commiter PRs

PR switching it here: https://github.com/apache/airflow/pull/39106 - sorry for the delay in following up on that one. J. On Fri, Apr 5, 2024 at 6:08 PM Wei Lee wrote: > +1 for this. I do not yet have enough chance to experience many job > failures, but it won’t harm us to test them out. Plus, i