Re: [DISCUSS] i18n maintanability policy

2025-06-01 Thread Buğra Öztürk
It is a good idea to bring procedures to maintain and keep the consistency across all translations. I am not 100% sure if it needs an AIP but we should have this well documented in the repository documentation as well, after the Wiki. Guidelines for policies and procedures after all of them agreed

Re: [DISCUSS] Deadlines default interval

2025-06-01 Thread Daniel Standish
Concur, mandatory with no default. Why set a deadline unless you know what it is? Re DeadlineAlert( reference=DeadlineReference.DAGRUN_QUEUED_AT, interval=timedelta(hours=1), callback=my_warning_callback ) I think it makes more sense model this field as an event rather than a column

Re: [DISCUSS] Apache Airflow official MCP Server

2025-06-01 Thread Amogh Desai
I agree that a use case driven approach is the way to go too. When we go full-blown, it is easy to lose track of the intention we started with. Some of the use cases related to debuggability improvements is something we already had a north star for in:https://github.com/apache/airflow/issues/4097

Re: [DISCUSS] Example dags

2025-06-01 Thread Amogh Desai
Nice! Thanks & Regards, Amogh Desai On Sat, May 31, 2025 at 4:30 PM Jarek Potiuk wrote: > And another small follow-up before we release 3.0.2 as Jed pointed out in > the previous PR, those example dags from standard provider do not really > fit the same pattern as system tests + example dags in

Re: [DISCUSS] i18n maintanability policy

2025-06-01 Thread Amogh Desai
Thanks for starting the thread Shahar! Well put up and far better than email discussions! Thanks & Regards, Amogh Desai On Sun, Jun 1, 2025 at 7:59 PM Jens Scheffler wrote: > Hi all, > > thanks @shahar for posting the discussion and the document. First hand > also added a few comments but in

Re: [DISCUSS] i18n maintanability policy

2025-06-01 Thread Jens Scheffler
Hi all, thanks @shahar for posting the discussion and the document. First hand also added a few comments but in general 99% agreeing to the definitions written there. After the text discussion is settled in a couple of days I'd propose to make it a README in the translations folder (airflow

Re: [DISCUSS] i18n maintanability policy

2025-06-01 Thread Wei Lee
Thanks Shahar! Just left a few comments. If we’re to make it part of an AIP, a standalone one would probably be better IMO. Best, Wei > On Jun 1, 2025, at 3:09 PM, Shahar Epstein wrote: > > Hello community! > > It's great to see that people from all over the world make Airflow > multilingual

Re: [DISCUSS] i18n maintanability policy

2025-06-01 Thread Aritra Basu
Thanks for this, left a comment. Overall in agreement with it! -- Regards, Aritra Basu On Sun, 1 Jun 2025, 1:39 pm Wei Lee, wrote: > Thanks Shahar! Just left a few comments. > If we’re to make it part of an AIP, a standalone one would probably be > better IMO. > > Best, > Wei > > > On Jun 1, 202

[DISCUSS] i18n maintanability policy

2025-06-01 Thread Shahar Epstein
Hello community! It's great to see that people from all over the world make Airflow multilingual, thus accessible for even more people. However, as Jarek mentioned in Slack [1], and as Jens prepares a PR that adds plenty of new terms [2] - I think that we need to make a short pause and discuss a m

Re: [DISCUSS] i18n maintanability policy

2025-06-01 Thread Jarek Potiuk
Yep. Absolutely introducing translation mechanisms and even a way to verify if translations are complete ( is a good starting point - but yes, just a starting point. Describing and agreeing the process of maintaining it is absolutely necessary, so good you started it - not sure if it needs an AIP