Re: [VOTE] Release Airflow 2.9.0 from 2.9.0rc1

+1 non binding Installed the RC with pip and ran it with breeze. Tested out a few example dags from my test suite and also checked if my changes work as expected. Thanks & Regards, Amogh Desai On Wed, Apr 3, 2024 at 1:46 PM Ephraim Anierobi wrote: > Hey fellow Airflowers, > > I have cut

Re: [VOTE] AIP-62 Getting Lineage from Hook Instrumentation

+0.9 (binding) I like the idea of this AIP, but I have not followed the entire implementation of AIP-53 to understand the need for the proposed implementation and discuss it, but I look forward to seeing it in Airflow. On Sun, Mar 31, 2024 at 1:23 PM Jakub Dardziński wrote: > +1 (non-binding).

Re: [DISCUSS] Proposal for adding Telemetry via Scarf

> I'd like to propose, that we start with collecting simple data with limited access: to all the PMC members. We can always expand it to Committers and then expand further to make it invite-only or setup exporting it to a DB like Postgres and

[ANNOUNCE] Deadlines inside!  Apply for a scholarship

*Hello, Airflow Community! * We want to see you in San Francisco, apply for a scholarship and remember that the CFP deadline is close… as well as your chance to get your Early Bird tickets, visit our website to discover more details about the venue and save your spot! Early Bird tickets will be

Re: [DISCUSS] Proposal for adding Telemetry via Scarf

Yup, exactly. I believe this would definitely help us take early and informed decisions. > E.g. Had we had this earlier, I believe it would have definitely helped us > more for our past discussions like whether we should continue supporting >

Community over Code EU 2024: Start planning your trip!

[Note: You're receiving this email because you are subscribed to one or more project dev@ mailing lists at the Apache Software Foundation.] Dear community, We hope you are doing great, are you ready for Community Over Code EU? Check out the featured sessions, get your tickets with special

Participate in the ASF 25th Anniversary Campaign

Hi everyone, As part of The ASF’s 25th anniversary campaign[1], we will be celebrating projects and communities in multiple ways. We invite all projects and contributors to participate in the following ways: * Individuals - submit your first contribution:

[ANNOUNCE] Apache Airflow Providers prepared on March 25, 2024 are released

Dear Airflow community, I'm happy to announce that new versions of Airflow Providers packages prepared on March 25. 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:

[RESULT][VOTE] Airflow Providers - release of March 25, 2024

Hello, [Filling-in for Elad - as we have a few follow-up tasks after we release FAB provider for Airflow 2.9.] Apache Airflow Providers (fab provider) prepared on March 25, 2024 have been accepted. 4 "+1" binding votes received: - Elad Kalif (binding) - Jarek Potiuk (binding) - Hussein Awala

Re: [DISCUSS] Proposal for adding Telemetry via Scarf

+1 to introduce this. I believe this would definitely help us take early and informed decisions. E.g. Had we had this earlier, I believe it would have definitely helped us more for our past discussions like whether we should continue supporting

Re: [VOTE] Airflow Providers prepared on March 25, 2024

+1 binding On Wed, 3 Apr 2024 at 10:29, Hussein Awala wrote: > +1 (binding) checked signatures, checksums, licences, and source code. > > On Tue, Mar 26, 2024 at 5:31 AM Amogh Desai > wrote: > > > +1 non binding > > > > Installed airflow from main with fab rc1 and I was able to create a few >

Re: [VOTE] Airflow Providers prepared on March 25, 2024

+1 (binding) checked signatures, checksums, licences, and source code. On Tue, Mar 26, 2024 at 5:31 AM Amogh Desai wrote: > +1 non binding > > Installed airflow from main with fab rc1 and I was able to create a few > test users with various roles, > check their rights on the elements, and run a

Re: [DISCUSS] Proposal for adding Telemetry via Scarf

Yup, I had added a link to scarf docs in the original email that referenced opting out and we should even add an Airflow config that puts all config in a single place. Without it we can’t be compliant to all the policies even if we collectively ignore or are unaware of the importance of it.

[VOTE] Release Airflow 2.9.0 from 2.9.0rc1

Hey fellow Airflowers, I have cut Airflow 2.9.0rc1. This email is calling a vote on the release, which will last at least 72 hours, from Wednesday, April 3, 2024 at 8:15 am UTC until Saturday, April 6, 2024, at 8:15 am UTC