Re: [VOTE] Airflow Providers prepared on June 07, 2024

+1 (binding) Checked reproducibility, signatures, checksums, licences. Looks good!

Re: [DISCUSS] Restore the SQL server backend

Just for context, here were (roughly) the results from the 2023 Airflow survey: PostgreSQL: 75% MySQL: 15% MSSQL: 5% Also, there are already discussions about potentially dropping MySQL support in Airflow 3. Given all that and the points from the past vote, I don't think it makes much sense to

Re: [VOTE] May 2024 PR of the Month

Some good contenders this month, but my vote also goes to #39336.

Re: [VOTE] Proposal for adding Telemetry via Scarf

+1 binding

Re: [VOTE] Release Airflow 2.9.1 from 2.9.1rc2

+1 (binding) Checked reproducibility, signatures, checksums, licences. Used it with the helm chart with a few different configs.

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

Very exciting! Looks like we will have a busy period of time ahead of us. Overall I like the plan so far, especially using this year's Airflow Summit as an opportunity to announce and gather feedback, and the 2025 version to pitch upgrading. I left a comment in the doc, but we might want to

[ANNOUNCE] Apache Airflow Python Client 2.9.0 Released

Dear Airflow community, I'm happy to announce that Apache Airflow Python Client 2.9.0 was just released. We made this version available on PyPI for convenience: `pip install apache-airflow-client` https://pypi.org/project/apache-airflow-client/2.9.0/ The documentation is available at:

[RESULT][VOTE] Release Apache Airflow Python Client 2.9.0 from 2.9.0rc1

Hello, Apache Airflow Python Client 2.9.0 (based on RC1) has been accepted. 4 "+1" binding votes received: - Jed Cunningham - Jarek Potiuk - Kaxil Naik - Hussein Awala 2 "+1" non-binding votes received: - Pankaj Koti - Amogh Desai Vote thread: https://lis

Re: [VOTE] April 2024 PR of the Month

I'll also vote for 38674 - cool stuff!

[VOTE] Release Apache Airflow Python Client 2.9.0 from 2.9.0rc1

Hey fellow Airflowers, I have cut the first release candidate for the Apache Airflow Python Client 2.9.0. This email is calling for a vote on the release, which will last for 72 hours. Consider this my (binding) +1. Airflow Client 2.9.0rc1 is available at:

Re: [DISCUSS] Proposal for adding Telemetry via Scarf

+1, looking forward to having better data!

Re: [VOTE] Release Airflow 2.9.0 from 2.9.0rc3

+1 (binding) Checked reproducibility, signatures, checksums, licences. Used it with the helm chart with a few different configs.

Re: [VOTE] Release Airflow 2.9.0 from 2.9.0rc2

+1 (binding) Checked reproducibility, signatures, checksums, licences. Used it with the helm chart with a few different configs. All looks good!

[RESULT][VOTE] AIP-64: Keep TaskInstance try history

Hello Airflow Community, The vote for AIP-64 has completed and it has been accepted. 14 "+1" binding votes received: - Jed Cunningham - Tzu-ping Chung - Pierra Jeambrun - Kaxil Naik - Jens Scheffler - Jarek Potiuk - Vikram Koka - Amogh Desai - Phani Kumar - Niko Oliveira - Bre

[ANNOUNCE] Apache Airflow 2.8.4 Released

Dear Airflow community, I'm happy to announce that Airflow 2.8.4 was just released. The released sources and packages can be downloaded via https://airflow.apache.org/docs/apache-airflow/stable/installation/installing-from-sources.html Other installation methods are described in

[ANNOUNCE] Apache Airflow Helm Chart version 1.13.1 Released

Dear Airflow community, I am pleased to announce that we have released Apache Airflow Helm chart 1.13.1   The source release, as well as the "binary" Helm Chart release, are available:  Official Sources:

[RESULT][VOTE] Release Airflow 2.8.4 from 2.8.4rc1

Hello, Apache Airflow 2.8.4 (based on RC1) has been accepted. 4 "+1" binding votes received: - Jed Cunningham - Jarek Potiuk - Hussein Awala - Andrey Anshin 3 "+1" non-binding votes received: - Rahul Vats - Amogh Desai - Wei Lee Vote thread: https://lis

Re: [VOTE] Release Airflow 2.8.4 from 2.8.4rc1

ed Mar 20 19:17:26 2024 +04 > gpg:using RSA key E1A1E984F55B8F280BD9CBA20BB7163892A2E48E > gpg:issuer "jedcunning...@apache.org" > gpg: Good signature from "Jed Cunningham " > [ultimate] > gpg: Note: This key has expired! > Prim

[RESULT][VOTE] Release Apache Airflow Helm Chart 1.13.1 based on 1.13.1rc1

Hello all, The vote to release Apache Airflow Helm Chart version 1.13.1 based on 1.13.1rc1 is now closed. The vote PASSED with 3 binding "+1", 1 non-binding "+1" and 0 "-1" votes: "+1" Binding votes: - Jed Cunningham - Jarek Potiuk - Hussein A

[VOTE] AIP-64: Keep TaskInstance try history

Hello Airflow Community, I would like to start a vote on AIP-64: Keep TaskInstance try history. You can find the AIP here: https://cwiki.apache.org/confluence/display/AIRFLOW/AIP-64%3A+Keep+TaskInstance+try+history Discussion Thread:

[VOTE] Release Apache Airflow Helm Chart 1.13.1 based on 1.13.1rc1

delines. $ helm gpg verify airflow-1.13.1.tgz gpg: Signature made Thu Mar 21 12:13:02 2024 MDT gpg:using RSA key E1A1E984F55B8F280BD9CBA20BB7163892A2E48E gpg:issuer "jedcunning...@apache.org" gpg: Good signature from "Jed Cunningham " [ulti

[VOTE] Release Airflow 2.8.4 from 2.8.4rc1

Hey fellow Airflowers, I have cut Airflow 2.8.4rc1. This email is calling a vote on the release, which will last at least 72 hours, from Wednesday, March 20, 2024 at 4:00 pm UTC until Saturday, March 23, 2024 at 4:00 pm UTC, and until 3 binding +1 votes have been received.

Re: [VOTE] Remove experimental API

I forgot to add the "why" - I view this as a breaking change still.

Re: [VOTE] Remove experimental API

-1. Even though it's been deprecated for a really long time now, I don't think we should remove it in a minor 2 release. I think we should wait until the next major.

[DISCUSS] AIP-63, AIP-64, and AIP-65: DAG Versioning

Hello everyone! I'm excited to start a discussion around DAG Versioning in Airflow. It's been the most requested feature in the last 3 community surveys! AIP-63: DAG Versioning As this topic quickly becomes rather

[ANNOUNCE] Apache Airflow Helm Chart version 1.13.0 Released

Dear Airflow community, I am pleased to announce that we have released Apache Airflow Helm chart 1.13.0   The source release, as well as the "binary" Helm Chart release, are available:  Official Sources:

[RESULT][VOTE] Release Apache Airflow Helm Chart 1.13.0 based on 1.13.0rc1

Hello all, The vote to release Apache Airflow Helm Chart version 1.13.0 based on 1.13.0rc1 is now closed. The vote PASSED with 3 binding "+1", 2 non-binding "+1" and 0 "-1" votes: "+1" Binding votes: - Jed Cunningham - Jarek Potiuk - Ephraim Anie

[VOTE] Release Apache Airflow Helm Chart 1.13.0 based on 1.13.0rc1

delines. $ helm gpg verify airflow-1.13.0.tgz gpg: Signature made Fri Mar 1 21:16:51 2024 MST gpg:using RSA key E1A1E984F55B8F280BD9CBA20BB7163892A2E48E gpg:issuer "jedcunning...@apache.org" gpg: Good signature from "Jed Cunningham " [ulti

Re: [VOTE] January 2024 PR of the Month

I'm down for #37101 too, but we might consider including #37016 as well. The former is just a simpler interface for the latter.

[ANNOUNCE] Apache Airflow Helm Chart version 1.12.0 Released

Dear Airflow community, I am pleased to announce that we have released Apache Airflow Helm chart 1.12.0   The source release, as well as the "binary" Helm Chart release, are available:  Official Sources:

[RESULT][VOTE] Release Apache Airflow Helm Chart 1.12.0 based on 1.12.0rc1

Hello all, The vote to release Apache Airflow Helm Chart version 1.12.0 based on 1.12.0rc1 is now closed. The vote PASSED with 3 binding "+1" votes: "+1" Binding votes: - Jed Cunningham - Jarek Potiuk - Hussein Awala Vote thread: https://lis

[VOTE] Release Apache Airflow Helm Chart 1.12.0 based on 1.12.0rc1

delines. $ helm gpg verify airflow-1.12.0.tgz gpg: Signature made Thu Feb 8 12:21:08 2024 MST gpg:using RSA key E1A1E984F55B8F280BD9CBA20BB7163892A2E48E gpg:issuer "jedcunning...@apache.org" gpg: Good signature from "Jed Cunningham " [ulti

Re: [DISCUSS] Rename channels on slack

That's not what I'm proposing. I should have been more verbose before, sorry. Let me rephrase. Don't rename #development. Leave it where it is, restrict posting to admins only. Create a new, fresh #contributing where everyone is still welcome. One of us admins will post in #development with links

Re: [DISCUSS] Rename channels on slack

Sounds good to me. We already have much more niche channels than best practices would be. Worst case no one uses it and we can purge it down the road, no harm no foul. One thing we should consider is not renaming development, but starting with a fresh channel for contributing. There are nearly

Re: [VOTE] "Require conversation resolution" setting in PRs as permanent solution

-0.5

Re: [VOTE] Airflow Providers prepared on January 22, 2024

+1 (binding) checked binary reproduction, licences, signatures, and checksums. On my system the binary reproduction check for the source tarball did fail, but I spot verified the tarball contents are correct. I'm still investigating, but no reason to hold the release for this.

Re: [VOTE] Release Airflow 2.8.1 from 2.8.1rc1

+1 (binding) Checked signatures, checksums, licences. Used it with the helm chart with a few different configs

Re: [VOTE] October 2023 PR of the Month

I'm slightly embarrassed I forgot about 34729, but yeah changing my vote to that as well. Now (at least so far) it's unanimous :)

Re: [VOTE] October 2023 PR of the Month

The new OpenSearch provider gets my vote - 34705.

Re: [VOTE] Add Multiple PR's of the Month to the Airflow Newsletter

Just to clarify, I didn't mean we should highlight multiple PRs every month. In that month none of @eumiro's PRs were individually enough to be highlighted but in bulk they were. That was an unusual situation though. I think we should be flexible with it. I'm not opposed to having multiple per

Re: [VOTE] Add providers for Pinecone, OpenAI & Cohere to enable first-class LLMOps

+1 (binding)

Re: [VOTE] Airflow Providers prepared on October 13, 2023

1 (binding) Checked signatures, checksums, licences

Re: [VOTE] Release Airflow 2.7.2 from 2.7.2rc1

+1 (binding) Checked signatures, checksums, licences, compared sources. Used it with the helm chart with a few different configs

[ANNOUNCE] Apache Airflow Helm Chart version 1.11.0 Released

Dear Airflow community, I am pleased to announce that we have released Apache Airflow Helm chart 1.11.0   The source release, as well as the "binary" Helm Chart release, are available:  Official Sources:

[RESULT][VOTE] Release Apache Airflow Helm Chart 1.11.0 based on 1.11.0rc2

Hello all, The vote to release Apache Airflow Helm Chart version 1.11.0 based on 1.11.0rc2 is now closed. The vote PASSED with 3 binding "+1", 2 non-binding "+1" and 0 "-1" votes: "+1" Binding votes: - Jed Cunningham - Hussein Awala - Daniel Stan

Re: [VOTE] Release Apache Airflow Helm Chart 1.11.0 based on 1.11.0rc2

> the `Chart.yaml` file which does not have a license Quirk of helm ultimately. The source tarball does have the license, just the convenience package tarball is missing it - helm processes the file and removes the comment when it packages the chart. It's been this way forever unfortunately.

[VOTE] Release Apache Airflow Helm Chart 1.11.0 based on 1.11.0rc2

delines. $ helm gpg verify airflow-1.11.0.tgz gpg: Signature made Sat Sep 30 11:45:11 2023 MDT gpg:using RSA key E1A1E984F55B8F280BD9CBA20BB7163892A2E48E gpg:issuer "jedcunning...@apache.org" gpg: Good signature from "Jed Cunningham " [ulti

Re: [VOTE] Release Apache Airflow Helm Chart 1.11.0 based on 1.11.0rc1

A bug was found in rc1 that'll necessitate an rc2. I'm canceling this vote and will create 1.11.0rc2 soon.

[VOTE] Release Apache Airflow Helm Chart 1.11.0 based on 1.11.0rc1

nes. gpg: Signature made Wed Sep 27 17:24:14 2023 MDT gpg:using RSA key E1A1E984F55B8F280BD9CBA20BB7163892A2E48E gpg:issuer "jedcunning...@apache.org" gpg: Good signature from "Jed Cunningham " [ultim

Re: [DISCUSS] move from semver to a more "rolling" release cycle for core

Shubham touched on it a bit, but I want to bring providers into the fold a bit as well. I don't think there is enough focus on provider versions. Us maintainers of Airflow have greatly benefited from being able to have breaking provider changes, but I always get the impression the average user

Re: [DISCUSS] Preventing users from misusing _PIP_ADDITIONAL_REQUIREMENTS ?

I also don't like the 10 minute thing. I'd rather we remove it, or display a message like we do sequential executor (we can only do so much, this is as visible as we can make it really), I think in that order?

Re: [VOTE] August 2023 PR of the Month

My vote is for a batch of PRs, not just a single one (which would have been impossible to review if they were all combined) - the refactoring work @eumiro has been doing recently. He's done 69 this month already!

Re: [VOTE] Drop MsSQL as supported backend

+1 binding

Re: [VOTE] Release Airflow 2.7.0 from 2.7.0rc2

+1 (binding) Checked signatures, checksums, licences, compared sources. Used it with the helm chart with a few different configs

Re: [VOTE] The daskexecutor, cncf.provider, celery providers in 2.7.0. as regular not-preinstalled providers

I'm also in favor of option a.

Re: Allowing providers to load the respective default connections

I like migrate as well.

Re: Allowing providers to load the respective default connections

I'm not sure I like sync over upgrade, personally. Everything else discussed sounds good though.

[DISCUSS] Should we pre-install celery/k8s providers?

Hello everyone, After thinking through whether the dask provider should be pre-installed or not, it got me thinking about whether we should even be pre-installing the celery and k8s providers. Core Airflow so far hasn't had the dependencies required to make those executors functional either -

Re: [VOTE] Make (soon coming) dask provider preinstalled

-1 binding (btw Vincent, your vote is binding in this vote ) On Fri, Jul 21, 2023 at 7:52 AM Beck, Vincent wrote: > -1 (non-binding) > > On 2023-07-21, 5:46 AM, "Michał Modras" LID> wrote: > > > CAUTION: This email originated from outside of the

Re: [DISCUSS] Contributing "core" options by providers configuration ?

I don't necessarily mind providers adding options to existing sections, but I can see the appeal and simplicity of enforcing it at the section level. Either way, I think in the case of multiple, it should fail loudly, not just warn.

Re: [VOTE] Airflow Providers prepared on July 09, 2023

+1 (binding) Checked signatures, checksums, licences.

Re: [VOTE] Release Airflow 2.6.3 from 2.6.3rc1

+1 (binding) Checked signatures, checksums, licences, and compared code to the tag. Used it with the helm chart with a few different config.

[ANNOUNCE] Apache Airflow Helm Chart version 1.10.0 Released

Dear Airflow community, I am pleased to announce that we have released Apache Airflow Helm chart 1.10.0   The source release, as well as the "binary" Helm Chart release, are available:  Official Sources:

[RESULT][VOTE] Release Apache Airflow Helm Chart 1.10.0 based on 1.10.0rc1

Hello all, The vote to release Apache Airflow Helm Chart version 1.10.0 based on 1.10.0rc1 is now closed. The vote PASSED with 3 binding "+1", 4 non-binding "+1" and 0 "-1" votes: "+1" Binding votes: - Jed Cunningham - Jarek Potiuk - Elad Kalif

[VOTE] Release Apache Airflow Helm Chart 1.10.0 based on 1.10.0rc1

delines. $ helm gpg verify airflow-1.10.0.tgz gpg: Signature made Fri Jun 23 09:26:49 2023 EDT gpg:using RSA key E1A1E984F55B8F280BD9CBA20BB7163892A2E48E gpg:issuer "jedcunning...@apache.org" gpg: Good signature from "Jed Cunningham " [ulti

Re: AIP-56 Extensible user management

management logic would still be > "packaged" in the auth manager, and then when everything is implemented and > done we can decide whether moving this FAB auth manager to a separate > provider is feasible/a good idea. > > What do you think? > > On 2023-06-12, 11:18 AM, &

Re: [VOTE] Release Airflow 2.6.2 from 2.6.2rc2

+1 (binding) Checked signatures, checksums, licences. Used it with the helm chart with a few different configs

Re: AIP-56 Extensible user management

Overall I'm happy with the proposal. One thing that concerns me though is moving the FAB auth manager into a separate provider. That auth manager will need to be able to hook into the db migration tooling, and we don't expose that to providers or plugins today. So if we do want to move it, we have

Re: [VOTE] Airflow Providers prepared on May 19, 2023

+1 (binding) Checked signatures, checksums, licences.

Re: [VOTE] Release Airflow 2.6.0 from 2.6.0rc5

+1 (binding) Checked signatures, checksums, licences. Used it with the helm chart with a few different configs

Re: [VOTE] Release Airflow 2.6.0 from 2.6.0rc4

+1 (binding) Checked signatures, checksums, licences. Used it with the helm chart with a few different configs

Re: [VOTE] Airflow Providers prepared on April 25, 2023

+1 (binding) Checked signatures, checksums, licences.

Re: [VOTE] Airflow Providers prepared on April 21, 2023

+1 (binding) Checked signatures, checksums, licences.

[ANNOUNCE] Apache Airflow Helm Chart version 1.9.0 Released

Dear Airflow community, I am pleased to announce that we have released Apache Airflow Helm chart 1.9.0   The source release, as well as the "binary" Helm Chart release, are available:  Official Sources:

[RESULT][VOTE] Release Apache Airflow Helm Chart 1.9.0 based on 1.9.0rc1

Hello all, The vote to release Apache Airflow Helm Chart version 1.9.0 based on 1.9.0rc1 is now closed. The vote PASSED with 3 binding "+1", 2 non-binding "+1" and 0 "-1" votes: "+1" Binding votes: - Jed Cunningham - Ephraim Anierobi - Jarek Po

Re: [VOTE] Airflow Providers prepared on April 09, 2023

+1 (binding) Checked signatures, checksums, licences.

[VOTE] Release Apache Airflow Helm Chart 1.9.0 based on 1.9.0rc1

. $ helm gpg verify airflow-1.9.0.tgz gpg: Signature made Tue Apr 11 09:41:29 2023 MDT gpg:using RSA key E1A1E984F55B8F280BD9CBA20BB7163892A2E48E gpg:issuer "jedcunning...@apache.org" gpg: Good signature from "Jed Cunningham " [ulti

Re: [VOTE] March PR of the Month

Another for 29413.

Re: [DISCUSS] AIP-52 updates - setup / teardown tasks

I've been working closely with Daniel on AIP-52 for a while now, but I'll still share my thoughts here. I'm also in favor of only supporting explicit relationships. In my opinion, even if multiple setup/teardown per scope never materialize, explicit relationships are still a better choice due to

Re: [VOTE] Release Airflow 2.5.2 from 2.5.2rc2

+1 (binding) Checked signatures, checksums, licences.

Re: [VOTE] Release Airflow 2.5.2 from 2.5.2rc1

+1 (binding) Checked signatures, checksums, licences. Used it with the helm chart with a few different configs.

Re: [VOTE] Airflow Providers prepared on March 03, 2023

+1 (binding) Checked signatures, checksums, licences.

Re: Apache Airflow Newsletter | February 2023

Thanks for putting this together John. I'd just like to mention to readers here that the old Airflow docs were only taken down for about 9 hours. They are back!

Re: [VOTE] February PR of the Month

+1 to #27758

Re: [URGENT] Remove old versions of Airflow docs (<1.10.14) as stop-gap measure for doc builds

Here it is: https://github.com/apache/airflow-site/pull/742

Re: [URGENT] Remove old versions of Airflow docs (<1.10.14) as stop-gap measure for doc builds

I came up with a stopgap that'll allow us to retain those old versions until we can work out the S3 archive. GitHub runners come with some stuff we don't actually use, so a little pre-cleanup and we've gained roughly 10Gb of extra disk  https://github.com/apache/airflow-site/pull/741 If that

Re: [VOTE] AIP-53 OpenLineage in Airflow

+1 binding

Re: [VOTE] Airflow Providers prepared on February 08, 2023

+1 (binding) Checked signatures, checksums, licences. I love to see the community casting non-binding votes. Thanks for the participation folks!

[ANNOUNCE] Apache Airflow Helm Chart version 1.8.0 Released

Dear Airflow community, I am pleased to announce that we have released Apache Airflow Helm chart 1.8.0   The source release, as well as the "binary" Helm Chart release, are available:  Official Sources:

[RESULT][VOTE] Release Apache Airflow Helm Chart 1.8.0 based on 1.8.0rc1

Hello all, The vote to release Apache Airflow Helm Chart version 1.8.0 based on 1.8.0rc1 is now closed. The vote PASSED with 4 binding "+1" and 1 "-1" non-binding votes: "+1" Binding votes: - Jed Cunningham - Ephraim Anierobi - Elad Kalif - Jarek

Re: [VOTE] Release Apache Airflow Helm Chart 1.8.0 based on 1.8.0rc1

+1 (binding) I just noticed the original email doesn't cast my +1 explicitly, oops!

Re: [VOTE] Release Apache Airflow Helm Chart 1.8.0 based on 1.8.0rc1

Jules, is your vote still a -1? I just want to accurately reflect it when this vote closes  >

Re: [VOTE] Release Apache Airflow Helm Chart 1.8.0 based on 1.8.0rc1

Thanks for the participation Jules. None of those are regressions from the latest release so they will end up in the next release instead of blocking this one. In general if we cut new RCs for every non-regression bug we'd spin our wheels a lot (less of an issue for the helm chart than core

Re: [VOTE] Release Airflow Go Client 2.5.0 from 2.5.0rc1

+1 (binding) Checked signatures, checksums, licences.

Re: [VOTE] Release Airflow Python Client 2.5.1 from 2.5.1rc1

+1 (binding) Checked signatures, checksums, licences.

[VOTE] Release Apache Airflow Helm Chart 1.8.0 based on 1.8.0rc1

. $ helm gpg verify airflow-1.8.0.tgz gpg: Signature made Tue Jan 31 12:53:25 2023 MST gpg:using RSA key E1A1E984F55B8F280BD9CBA20BB7163892A2E48E gpg:issuer "jedcunning...@apache.org" gpg: Good signature from "Jed Cunningham " [ultim

Re: [VOTE] Airflow Providers prepared on January 23, 2023

+1 (binding) Checked signatures, checksums, licences.

Re: [VOTE] Release Airflow Python Client 2.5.0 based on 2.5.0rc1

+1 (binding) Checked signatures, checksums, licences.

Re: [VOTE] Release Airflow 2.5.1 from 2.5.1rc2

+1 (binding) Checked signatures, checksums, licences. Used it with the helm chart with a few different configs.

Re: [VOTE] AIP-52 Automatic setup and teardown tasks

+1 (binding)

  1   2   3   >