Re: [DISCUSS] What should we cherry-pick ?

Might be a good idea, yes. On Tue, Jun 24, 2025 at 9:09 PM Jens Scheffler wrote: > Hi Jarek, > > one thought came into my mind... as you said it is a lot of trouble to > find which "dev" PR might be missing on a mainteance branch... should we > cherry-pick dev tooling PRs by default as well to a

Re: [DISCUSS] What should we cherry-pick ?

PR here to add backport label automatically for dev tools changes (and to maintain it with minor version upgrades) https://github.com/apache/airflow/pull/52189 On Tue, Jun 24, 2025 at 9:14 PM Jarek Potiuk wrote: > Might be a good idea, yes. > > On Tue, Jun 24, 2025 at 9:09 PM Jens Scheffler > w

🎟️ Check out the full program- Early Bird ends in 1 week!

[image: Airflow Summit 2025] *Dear Airflow Community, * Airflow Summit 2025 program is live — and Early Bird tickets are still available for *just one more week!* This is the perfect time to explore our newly announced sessions and secure your spot with a 25% price.

[REMINDER]: Airflow 3 Dev call on 26th June - agenda

Hi everyone, Here is a quick reminder that we have our Airflow 3 dev call the day after tomorrow at Thursday, 26th June 2025 at 8AM PST (11 am EST | 4 pm UTC / GMT). Proposed agenda: 1. Catch-up on action items from last call - Docs site update (Jarek or Elad) - Update regarding internationalizat

Re: [DISCUSS] What should we cherry-pick ?

Hi Jarek, one thought came into my mind... as you said it is a lot of trouble to find which "dev" PR might be missing on a mainteance branch... should we cherry-pick dev tooling PRs by default as well to active maintenance branches? I mean... automating this in the CI like if `backport to`labe

Re: [DISCUSS] What should we cherry-pick ?

It looks like everyone is mostly on the same page based on all the emails - so no comments :) . On Tue, 24 Jun 2025 at 07:45, Wei Lee wrote: > I’m +1 for 1-3 (assuming the doc changes relate to the backported version). > +0.5 for 4. I hope that changes not related to new features will be > backp

[ANNOUNCE] Apache Airflow Helm Chart version 1.17.0 Released

Dear Airflow community, I am pleased to announce that we have released Apache Airflow Helm chart 1.17.0 🎉 🎊 The source release, as well as the "binary" Helm Chart release, are available: 📦 Official Sources: https://airflow.apache.org/docs/helm-chart/1.17.0/installing-helm-chart-from-sources.ht

Re: [DISCUSS] What should we cherry-pick ?

https://github.com/apache/airflow/pull/52148 -> Proposed PR. Let's iterate there if there are comments. On Tue, Jun 24, 2025 at 11:25 AM Jarek Potiuk wrote: > Yeah. I think what I am really after is expressed by Wei: +0.5 vote - > i.e. we should be fine with **some** selected cherry-picks that

Re: [DISCUSS] What should we cherry-pick ?

Yeah. I think what I am really after is expressed by Wei: +0.5 vote - i.e. we should be fine with **some** selected cherry-picks that are not bug-fixes that we proactively cherry-pick and do not "complain" that this is wrong because technically it's not a bugfix. I think It would be great if in ev

Re: [HELP NEEDED] Cleanup pytest.mark.db_tests

Hello, Yeah I realised that there could probably be some places that require more attention and the pattern that I see is that those tests are mostly playing around or accessing the *default* connections. I am working on a task that can separate out the DB dependency while creating *default* con

Re: [Discussion] AIP-90: Should It Be Implemented in the Standard Provider or as a standalone provider?

I like HITL as an acronym as well - it's well recognized. Just to add a bit of stir this is an interesting article when someone tried to also distinct: * HITL (Human In the Loop) * with HOTL (Human On the Loop) * and HATL (Human Above the Loop) * and HBTL (Human Behind the Loop) Interesting conc

Re: [Discussion] AIP-90: Should It Be Implemented in the Standard Provider or as a standalone provider?

Thanks Wei. 1) "Human in the Loop": +1 on the naming. Standard names. HITL acronym is also pretty standard (https://en.wikipedia.org/wiki/Human-in-the-loop | https://cloud.google.com/discover/human-in-the-loop). "interactive" is a loaded term and be pretty vague. 2) re: Standard vs Separate Provid