Hey everyone,

I updated our meeting notes document in the Airflow wiki to capture the
notes from our dev call earlier today. The link for those notes is here
<https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=308153072#Airflow3Devcall:MeetingNotes-Summary.18>

Thank you all for the hard work in getting to the 3.0.0 alpha release. It
is so energizing to see it finally come together after we have been working
on it for the last several months.

It is wonderful to see all the great features and the new UI coming
together. Today, it was wonderful to see the new DAG Trigger form
demonstrated by Shubham and Jens.

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 on the 20th of February 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.2>
.

Best regards,
Vikram

--
Below is the summary from the call on Thursday:

   - Follow-up on action items from the last call
      - "Feature freeze" guidelines (Ash Berlin-Taylor)
         - Ash confirmed that he had sent out the email to the dev list
         with his thoughts around how we as committers and PMC members
need to be
         very risk-aware as we merge changes into main until the 3.0 release is
         shipped as GA. He also mentioned how fundamental the 3.0
changes were to
         the code and that they were much larger than even the 2.0
changes. Jarek
         and Vikram agreed with the risk-aware sentiment.
      - AIP-81 CLI changes (Bugra Ozturk)
         - Bugra quickly walked through the doc already shared with the dev
         list (Doc link
         
<https://docs.google.com/document/d/1BSEQxKEOArPRCclfCrAjAN5hjC56vG0R5nZPc3pxF9Y/edit?usp=sharing>
         ).
         - Bugra walked through how local vs. remote commands now needed to
         be separated because of the TaskSDK changes in 3.0. There was general
         agreement about this.
         - There wasn't much discussion in the call around the detailed
         architecture and sequence diagrams in the document, and "the
ask" was for
         the team to review the document and leave comments async.
      - Development updates
      - Update on AIP-38 Modern Web Application
      
<https://cwiki.apache.org/confluence/display/AIRFLOW/AIP-38+Modern+Web+Application>:
      New Trigger Form UI (Shubham Raj and Jens Scheffler)
         - Shubham walked through a demonstration of the new trigger form
         developed in the Airflow 3 UI.
         - The demo went through flawlessly and there was general
         admiration for the work done.
         - Shubham also confirmed that this work had been merged into main
         already.
      - Test plan update (Rahul Vats)
         - Rahul walked through the Airflow 3.0 Test plan
         
<https://cwiki.apache.org/confluence/display/AIRFLOW/Airflow+3.0+Test+Plan>
         which now includes the status of the formal testing effort in
addition to
         the plan itself.
         - Rahul described how the team was tracking development and test
         progress, while testing and reporting issues on the alpha builds.
         - There was general appreciation of the work being done. Vikram
         urged Rahul to ask for help from the broader team as and when needed.
      - Discussion topics
      - Milestone / workstream update (Vikram Koka)
         - Vikram thanked the whole team for all the great work which had
         been done towards getting to the alpha builds. He mentioned how hard
         cutting the first alpha had been and appreciated Jed among
others, who had
         almost a 24 hour day in order to make it happen.
         - In order to be more predictable, Vikram asked the team to cut
         alphas (and betas in the future), at least every Thursday, so
that we could
         have predictability.
         - Jarek agreed, citing the heuristic "If it hurts, do it more
         often". Jed agreed, saying that the alpha2 being cut right
then has been
         significantly smoother than alpha1. Jed also asked everyone
on the team to
         be aware that the alpha builds would start roughly around
noon India time
         every Thursday.
         - By the time of writing, Airflow 3.0.0alpha2 had been shipped
         out.


<https://www.astronomer.io/>

Reply via email to