Hi all,
I was alerted to this rundown of Airflow 3.0 features (
https://thedatacanal.substack.com/p/airflow-30-dag-versioning-multi-language).
And I noticed that some of the notes on logical date changes were
outdated. Perhaps because chat gpt does not follow the dev list?
Anyway, so I realized
+1 — coupled with the ability to do backfills in the UI now, if there is also
want the old behaviour back on an ad-hoc basis it’s easy to get the missing
runs created too.
-ash
> On 5 Mar 2025, at 22:26, Jarek Potiuk wrote:
>
> Looks like `[LAZY CONSENSUS]` candidate to me :)
>
> On Wed, Mar
Thank you all!
Yes, it is starting to look like a lazy consensus candidate. :)
Unless there are any objections today or tomorrow, I'll start that on
Saturday (so Monday is in the window).
And sorry about the initial confusion I should have specified that I am
only talking about a config default ch
Hi Ahmad, thanks for the updates! I've spent some time looking at the
changes and have added some comments and questions. I've pointed out a
couple things for future work that I think will be important, but nothing
that needs to be changed for this PR in my mind. Looking forward to seeing
your resp
