[RESULT][VOTE] Airflow Providers - release of August 19, 2024

Hello, Apache Airflow Providers prepared on August 19, 2024 have been accepted. Provider openlineage is excluded from this release. 4 "+1" binding votes received: - Elad Kalif - Jarek Potiuk - Ash Berlin-Taylor - Hussein Awala 3 "+1" binding votes received: - Vincent Beck - Freddy Demiane - Amo

Re: [RESULT][VOTE] Airflow Providers - release of August 19, 2024

Small typo for non binding votes. It mentions both as binding Thanks & Regards, Amogh Desai On Thu, 22 Aug 2024 at 3:44 PM, Elad Kalif wrote: > Hello, > > Apache Airflow Providers prepared on August 19, 2024 have been accepted. > Provider openlineage is excluded from this release. > > 4 "+1" b

Re: [RESULT][VOTE] Airflow Providers - release of August 19, 2024

Yes sorry here is the updated count: 4 "+1" binding votes received: - Elad Kalif - Jarek Potiuk - Ash Berlin-Taylor - Hussein Awala 4 "+1" non binding votes received: - Vincent Beck - Freddy Demiane - Amogh Desai - Rahul Vats On Thu, Aug 22, 2024 at 1:17 PM Amogh Desai wrote: > Small typo for

[ANNOUNCE] Apache Airflow Providers prepared on August 19, 2024 are released

Dear Airflow community, I'm happy to announce that new versions of Airflow Providers packages prepared on August 19, 2024 were just released. Full list of PyPI packages released is added at the end of the message. The source release, as well as the binary releases, are available here: https://ai

Discussion: new code layout for apache/airflow monorepo

Hi all: As part of the work on AIP-72 (Task Execution interface and SDK) and I’d like to propose a slight modification to the code layout inside our main repo. More details can be found in the slack thread . I will discu

[REMINDER] Airflow 3 Dev call on 22 August (Thursday) with a Proposed Agenda

Hello all, Just a reminder that we will have our dev call today (Thursday), 22 August, at 4 PM BST (3 PM GMT/UTC | 11 AM EST | 8 AM PST). *Proposed Agenda*: 1) Check in on the action items from the last call - AIP-79: Removing FAB as core dep. POC Update (Jed) - Update on development pr

Re: Discussion: new code layout for apache/airflow monorepo

That looks good as a first step of moving things. Few comments and questions: 1) I guess it should be "providers/src/airflow/providers/*" to have a similar structure (also see point 2) 2) are we (currently) ignoring the fact that we have docs, tests, and some other things also in shared director

[Airflow 3 call followup] StatsD/OTel metric naming

Following up on the discussion in the call this morning. We were running tight on time and I didn't want to derail the remaining conversation, but wanted to follow up here. There will be a separate thread on whether we intend to keep StatsD, either as a default or the secondary, or remove it