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-17April2025>
Thank you all for attending today, especially just before the Easter break.
The teamwork, energy, and sheer work from this team has been consistently
amazing and key in getting us to this release candidate.
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.
Best regards,
Vikram
--
Below is the summary from the call:
-
- Edge Provider naming (Elad Kalif and Jarek Potiuk):
- Elad explained that the Edge provider will be called "edge3"
for many reasons.
- It's ready to be used and tested.
- Once the current Provider vote is closed, Elad will cut a new
wave including Git and Edge3 for an extra 24 hours voting
period and then
these would be released.
- Development Updates
- Test plan and Issue statistics update (Rahul Vats and Vikram
Koka):
- Rahul shared the current state of testing based on RC3 and
said the regression testing on RC3 is ongoing.
- Rahul felt that the current confidence level is high.
- Rahul also shared the issue statistics for Airflow 3 with:
- Alpha releases: 40 issues reported and closed.
- Beta releases: 129 issues reported and closed.
- Release candidates: 102 issues reported, with 64 of them
already closed.
- Rahul also said that there are no currently open blocking
issues with the release.
- He also expressed how many issues were fixed directly in PRs
without the issues even being reported.
- Vikram added that he had a target of at least 200 issues to
be reported in the combination of Alpha, Beta, and RCs.
- He said that seeing a total of 271 issues reported was great
to see and gave confidence in testing of the release.
- Discussion Topics
- Dev workflow for 3.0+ (Kaxil Naik)
- Kaxil explained that we now have project milestones for
3.0.1, Airflow 3.1.0, and Airflow 3.1+.
- He articulated how these should be used for new work going
forward with issue resolutions for 3.0.1, vs. new feature
work being
targeted for 3.1.0 and 3.1+
- Docs approach towards AF 3 users (Elad Kalif)
- Elad reminded everyone that our docs are versioned and asked
everyone to write docs assuming that the users coming are
using Airflow
3.0.
- Elad asked doc writers to avoid "if Airflow 2, do this" and
"if Airflow 3, do this" within the docs, since that would
be confusing to
the reader.
- Ongoing support for Airflow 2 (Kaxil Naik)
- Kaxil brought up the topic of "maintenance support for
Airflow 2", once Airflow 3 is released.
- Kaxil showed that we had supported Core Airflow 1.10.x
maintenance releases for 6 months after the release of Airflow 2.
- There was significant discussion around this including the
separation of maintenance of bug fixes vs. security fixes.
- Elad also brought up the separation of maintenance updates
for Core Airflow OSS vs. Providers
- The decision from the team was to take this discussion to the
devlist. Kaxil to start a mailing list thread.
Vikram Koka
Chief Strategy Officer
Email: vik...@astronomer.io
<https://www.astronomer.io/>
