Re: [DISCUSS] Turn "tests_common" into separate distribution for development

devel-common sounds reasonable - ferruzzi From: Jarek Potiuk Sent: Tuesday, March 4, 2025 10:53 AM To: dev@airflow.apache.org Subject: RE: [EXT] [DISCUSS] Turn "tests_common" into separate distribution for development CAUTION: This email originated from out

Re: [DISCUSS] Turn "tests_common" into separate distribution for development

Seems like the PR is getting to "green" zone - so one last push - and I am changing it to "devel-common" unless I hear strong NOOO! On Tue, Mar 4, 2025 at 10:36 PM Vincent Beck wrote: > devel-common makes sense to me > > On 2025/03/04 21:13:47 "Oliveira, Niko" wrote: > > +1 to devel-common f

Re: [DISCUSS] Auth backends

I think this is a great way to move forward considering airflow 3 deadline. Also given that this is already implemented and merged in main I’m not sure if an AIP makes sense at this point, I’ll let others weigh in on this. On Tue 4 Mar 2025 at 23:05, Vincent Beck wrote: > Option 1 seems to be th

Re: [DISCUSSION] Changing catchup_by_default from True to False

I strongly disagree with the proposal of changing the default for all DAGs. This requires every user that does not specify catchup to modify their DAGs. As pointed out in other similar threads about changes requiring DAG code changes: >I am concerned simply because it is a physical code change, an

[DISCUSSION] Changing catchup_by_default from True to False

Hey there, long time reader, first time poster here :) *tl;dr:* *As part of the 3.0 release, I would like to propose changing the default for `catchup_by_default` from True to False. * *This discussion asks for input and whether this can be a lazy consensus or should be a vote.* Timethings are

Re: [DISCUSSION] Changing catchup_by_default from True to False

> I strongly disagree with the proposal of changing the default for all DAGs. This requires every user that does not specify catchup to modify their DAGs. I don't think that's accurate. Tamara's proposal is just to change the default value of the global configuration that controls this

Re: [DISCUSSION] Changing catchup_by_default from True to False

I think Michał - you might have not entirely understood / realised the impact. It's not as bad as you described it, I think. As I understand it - the idea here is to set "catchup_by_default" to False, but you can still keep 100% compatibility by setting it to True manually for the whole installati

Re: [DISCUSSION] Changing catchup_by_default from True to False

+1 - I would also favor this proposal. On 05.03.25 21:25, Akash Sharma wrote: +1 We should change it from both global and DAG level. Best regards, Akash On Thu, 6 Mar, 2025, 01:01 Jed Cunningham, wrote: +1, this is one of the few configs that I change from the default immediately. --

Re: [DISCUSSION] Changing catchup_by_default from True to False

Looks like `[LAZY CONSENSUS]` candidate to me :) On Wed, Mar 5, 2025 at 11:23 PM Oliveira, Niko wrote: > +1 as well,l I've never liked the default on behaviour for this config. > > > From: Jens Scheffler > Sent: Wednesday, March 5, 2025 12:54:05 PM > To: dev@air

[REMINDER]: Airflow 3 Dev call on 6th March - agenda

Hi everyone, Here is a quick reminder that we have our Airflow 3 dev call tomorrow Thursday, the 6th of March at 8AM PST (11 am EST | 4 pm UTC / GMT). Proposed agenda: 1. Check in on action items from the last call - Airflow 3.0 minimum version to be Python 3.10 (Ash Berlin-Taylor) 2. Developmen

Re: [DISCUSSION] Changing catchup_by_default from True to False

+1, this is one of the few configs that I change from the default immediately.

Re: [DISCUSSION] Changing catchup_by_default from True to False

If we can control the behaviour globally instead of specifying it on the DAG level, I take back my concerns. Thanks for clarifying! On Wed, Mar 5, 2025 at 8:26 PM Jarek Potiuk wrote: > I think Michał - you might have not entirely understood / realised the > impact. It's not as bad as you describ

Re: [DISCUSSION] Changing catchup_by_default from True to False

+1 We should change it from both global and DAG level. Best regards, Akash On Thu, 6 Mar, 2025, 01:01 Jed Cunningham, wrote: > +1, this is one of the few configs that I change from the default > immediately. >

Re: [DISCUSS] Turn "tests_common" into separate distribution for development

The PR is now merged,,, we have 'devel-common` now. The important bit now for everyone... It's easier than ever to have dev-env running for airflow... 1) uv sync -> and your .venv env allows you to run all tests for airflow/task-sdk 2) uv sync --all-packages -> and your .venv allows you to also r

Re: [DISCUSSION] Changing catchup_by_default from True to False

+1 as well,l I've never liked the default on behaviour for this config. From: Jens Scheffler Sent: Wednesday, March 5, 2025 12:54:05 PM To: dev@airflow.apache.org Subject: RE: [EXT] [DISCUSSION] Changing catchup_by_default from True to False CAUTION: This email o