Hey everyone, Apologies for the delay in posting the meeting notes. I just updated our meeting notes document in the Airflow wiki to capture the notes from our last dev call. The link for those notes is here <https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=308153072#Airflow3Devcall:MeetingNotes-Summary.28>
Thank you all for attending the meeting. The discussion was very good, as evidenced by the long summary :) I hope I captured them all. To everyone who attended the meeting, please check the summary and add anything that I may have missed. For those who could not join, please let us know if you disagree with anything discussed and agreed upon in the meeting. Also, please do ask questions if something is unclear. Our next meeting is the day after tomorrow, the 5th of June at the same time. Please let me know if you would like to add anything to the agenda <https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=308153072#Airflow3Devcall:MeetingNotes-5June2025> . Best regards, Vikram -- Below is the summary from the call: - Catch-up on action items from last call: - Docs site update (Elad, Jarek) - Elad said that they could not make much progress on the Docs site update over the last couple of weeks, but would have an update by the next dev call. - Jarek added that there has been significant improvements to the Doc publishing process, led by Pavan. - The team agreed with that and gave a shout out to Pavan, Jarek, and everyone who had contributed to these improvements. - Example Dags update (Jens, Jarek) - Jens talked about the small team who have gathered together to start working on improvements to the Example DAGs. - Jens shared the wiki page <https://cwiki.apache.org/confluence/display/AIRFLOW/Examples+Refurbis> which was being used to track these ideas. - There was a discussion around whether "testing DAGs" are useful to end users and if they should be tagged as "dual use" to reflect that they can be used as an example. - Development Updates: - Deadline alerts AIP-85 (Dennis Ferruzzi, Rajesh B) - Dennis and Ramit gave an update on Deadline alerts which included a long, in-depth technical discussion around the implementation options. - There was significant discussion around where the loop to check for alerts should be run as well as where the dag-level callbacks should be run. - The view from the team was that system monitoring i.e. if the scheduler is down is out of scope for this effort and should be done outside of Airflow, i.e. if Schedulers (or Workers) are down, no SLAs would be fired. - After the extended discussion, the summary was that we aligned on a variation of option 1 from the email, with the following elements: - Scheduler loop would be used for checking SLA misses - If an async notifier is specified, the callback would be run in the triggerer - If a sync notifier is specified, the callback would be run on a worker - We recommend async callbacks using the builtin Airflow async notifiers - Update on the 3.0.x and 2.11 releases (Kaxil) - Kaxil mentioned that we released 3.0.1 and 2.11 already and that we would be cutting 3.0.2 in about two weeks. - Discussion Topics: - UI Internationalization - Brent shared that we had just merged a PR to support internationalization in the UI. - There was a lot of excitement around this. - There was an early discussion on what terms should NOT be translated such as "DAG" or "Xcom". - This was to be followed up offline. - Golang SDK - Ash shared that he had raised a PR <https://github.com/apache/airflow/pull/50964> for an early incarnation of the Golang Task SDK and requested feedback. - Airflow 3 feedback: - Pavan shared that he was at the Astronomer roadshow in London the day before and the feedback from people was very positive. - Quote: "People are amazed with Airflow 3 features, dag versioning, Event driven scheduling. everyone looking to upgrade AF3, that's what i hear at least from the people i met :)" Vikram Koka Chief Strategy Officer Email: vik...@astronomer.io <https://www.astronomer.io/>
