Hey everyone, I updated our meeting notes document in the Airflow wiki to capture the notes from our quick dev call earlier today. The link for those notes is here <https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=308153072#Airflow3Devcall:MeetingNotes-Summary.20>
Thank you all for the great communication and teamwork. It's wonderful to see everyone pulling together to deliver this release. And amazing to see the consistent progress. 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. As we are on a weekly cadence until release, our next meeting is on the 3rd of April 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-ProposedAgenda.5> . Best regards, Vikram -- Below is the summary from the call: - Follow-up on action items from last call - Cleanup of Airflow 3 open items in Github - specifically airflow3.0:candidate <https://github.com/apache/airflow/issues?q=is%3Aissue%20state%3Aopen%20label%3Aairflow3.0%3Acandidate> and airflow3.0:breaking <https://github.com/apache/airflow/issues?q=is%3Aissue%20state%3Aopen%20label%3Aairflow3.0%3Abreaking> - There was consensus already either closing the "airflow3.0:candidate" issues or tagging them to be "airflow 3.1+" as appropriate based on where we are today - The harder discussion was around "airflow3.0:breaking" issues: - Some of these were actually done and need to be just closed. Ash, Jens, and Kaxil had identified at least one each. - There was a discussion about others which could not be done in the time left because of ripple effects and migration challenges. The team decided that we would discuss a mechanism for introducing deprecations / breaking changes without having to be as ultra-strict on semantic versioning as we are today. To avoid cognitive overload, this discussion will be brought to the dev list in May. Jarek took the action item for this. - Development Updates and Presentations - Test Plan Update Rahul Vats <https://cwiki.apache.org/confluence/display/~rahul.vats> - Rahul walked through the Airflow 3 Test plan <https://cwiki.apache.org/confluence/display/AIRFLOW/Airflow+3.0+Test+Plan> and showed how it was now updated to also reflect the status of AIPs 81 and 82, thanks for Bugra and Vincent. - He also spoke about the integration testing with Providers under way. - For AWS providers, Rahul mentioned that he had been working with Dennis and that the AWS providers were mostly working, with only a couple of issues to be resolved. - For Google Providers, he mentioned that the Google Provider dashboard was broken and that the Google team was working on fixing the dashboard. Eugene from the Google team confirmed the same. - Open issues to be resolved - With respect to the Branch Python Operator raised by Shahar last week, Pavan said that he had fixed that issue. There was some discussion if there were any other issues regarding the BranchPythonOperator, but there was nothing on the board at this time. - Kaxil mentioned that there is a high priority issue with BaseSensor, which he was working on fixing right now. - There is also a critical issue with Triggerer , which Pierre is fixing and close to merging at this time. Pavan to fix the Deferrable Operator issues based on this. - A high priority DAG Versioning UI / Grid View issue was also discussed and Jed said that he had a fix for that on his dev branch based on work with Brent, which he would be merging shortly. - Rahul mentioned that he and the team were also looking at UX issues between Airflow 3 and Airflow 2.x, and would raise them as appropriate. Vikram Koka Chief Strategy Officer Email: vik...@astronomer.io <https://www.astronomer.io/>
