Yes it is
Yaweha
> On 28 Jan 2025, at 7:17 PM, Nick Johnson wrote:
>
>
> Yaweha
-
To unsubscribe, e-mail: dev-unsubscr...@airflow.apache.org
For additional commands, e-mail: dev-h...@airflow.apache.org
Yaweha
-
To unsubscribe, e-mail: dev-unsubscr...@airflow.apache.org
For additional commands, e-mail: dev-h...@airflow.apache.org
+1 for #45563
Tough choice indeed, but I’d also like to cast my vote for *#45563 (Sphinx
Upgrade)*. Huge thanks to Shahar for driving this forward and to Jens and
Jarek for the support. As Jarek mentioned, groundwork like this often flies
under the radar but is critical to long-term project sustai
+1 for #45563
THANKS to Shahar for taking the lead! Agree wit Jarek. Hope somebody has
capacity and energy to fix other Docs problems upcoming.
But in general a tough choice this month with sooo many great
contributions. Also want to explicity thank Wei for the newsfragment
cleanup and *vatsrahu
I agree with Michał - it's not how simple it is, but that you do it at all.
Chance is that if you have 1000s of DAGs in your company and some of them
use email notification, it means that vast majority of them will. And I
already know of companies where there are 20+ teams working on those and
havi
I am concerned simply because it is a physical code change, and one that
would affect a good percentage of DAGs out there. No matter how complex the
change is, it forces the users to modify their code, which is huge
operational overhead in bigger organizations. Imagine - there could be a
central pl
+1 for #45563 (Sphinx). A very good first step forward!
On 2025/01/28 08:34:31 Jarek Potiuk wrote:
> Yeah, I am also for Sphinx #45563.
>
> I think we have plenty of "new feature" PRs that a lot of busy folks are
> working on so this is really a tough one, but I think those PR will be
> praised a
I'd like to provide example:
with DAG(
default_args={
"email": ["airf...@airflow.com"],
"email_on_failure": True,
"email_on_retry": True,
},
...
) as dag:
becomes:
from airflow.providers.smtp.notifications.smtp import SmtpNotifier
with DAG(
default_args={
+1 to what Jarek proposes.
IMO, for Airflow to become not only a leading solution in its market, but
also a de facto standard, we need to be super conscious about the effort
required for users to maintain it and keep it up to date. It's a super
common concern raised by the users, especially those,
Yeah, I am also for Sphinx #45563.
I think we have plenty of "new feature" PRs that a lot of busy folks are
working on so this is really a tough one, but I think those PR will be
praised and touted (and people working on them collectively and
individually) when we go to release announcements, and
10 matches
Mail list logo
