mmunity: Contribute to UI filters work and upgrade blocking
issues
--
Vikram Koka
Chief Strategy Officer
Email: vik...@astronomer.io
<https://www.astronomer.io/>
Definite +1 from me as well, for the reasons already outlined above. I was
twitchy about this for a while.
Vikram
On Tue, Jul 29, 2025 at 10:20 AM Jed Cunningham
wrote:
> Big +1 to this. Our postgres-out-of-the-box default has always made me
> slightly uncomfortable anyways.
>
Hi everyone,
Here is a quick reminder that we have our Airflow 3 dev call on Thursday,
31st July 2025 at 8AM PST (11 am EST | 4 pm UTC / GMT).
Proposed agenda:
1. Catch-up on action items from last call
- Cleanup the Airflow 3.1 wiki structure (Vikram)
2. Development Updates and Presentations:
-
add Augusto
Hidalgo to discuss Benchmark updates to next dev call.
- Community: Create, tag, and self-assign (if possible) Airflow 3
adoption issues before next dev call
Vikram Koka
Chief Strategy Officer
Email: vik...@astronomer.io
<https://www.astronomer.io/>
ion?pageId=308153072#Airflow3Devcall:MeetingNotes-ProposedAgenda.12>
or
send me an email.
The summary of the call will also be sent to the mailing list and posted on
the same wiki page.
Looking forward to seeing you all soon,
Vikram
--
Vikram Koka
Chief Strategy Officer
Email: vik...@astrono
3.1 release. It
> is not mentioned in the summary, and I can't find it on wiki.
>
> Thank you
>
> - Eugene
>
> On Mon, Jul 7, 2025 at 3:04 AM Vikram Koka
> wrote:
>
> > Hey everyone,
> >
> > Thank you to everyone who made the dev call last week. I up
ow, following the thread
brought up by Ash
in the dev list.
- This was a great discussion with a lot of participation from
everyone on the call.
- Ash to summarize this.
--[image: Screenshot 2025-07-01 at 7.41.50 PM.png]
Vikram Koka
Chief Strategy Of
concluded by asking people to comment back in the AIP
soon, so that feedback could be addressed in writing.
- Call for actions ...ah.. review! Example Dags! (Jens)
- Jens raised a "call for action", asking people to help review
the work on the Example
This is awesome!
I love the detailed instructions on how to use AI for this specific coding
situation.
Would love to hear feedback regarding how this worked for people.
Vikram
On Sat, Jun 28, 2025 at 6:12 AM Jarek Potiuk wrote:
> > I would love to try it out once too :D
>
> Just do it!
>
> On
Congratulations Amogh, very well deserved!
On Thu, Jun 26, 2025 at 7:02 AM Hemkumar Chheda
wrote:
> Fantastic news. Congrats, Amogh!
>
> Regards,
> Hemkumar
>
> > On 26 Jun 2025, at 6:56 PM, Ambika Garg
> wrote:
> >
> > Congratulations Amogh!
> >
> > On Thu, Jun 26, 2025 at 9:15 AM Constance M
l will also be sent to the mailing list and posted on
the same wiki page.
Looking forward to seeing you all soon,
Vikram
--
Vikram Koka
Chief Strategy Officer
Email: vik...@astronomer.io
<https://www.astronomer.io/>
This is a very difficult thread to catch up on.
I will take a detailed look at the AIP update to try to figure out the
changes in the proposal.
>From a quick glance, the updated AIP didn't seem to have any reference to
AIP-82, which surprised me, but will take a more detailed read through.
Vikram
I agree with the standard provider approach.
On Sun, Jun 22, 2025 at 7:26 PM Vikram Koka wrote:
> Thanks Wei, I really appreciate the work, and will review it as soon as
> possible.
>
> With respect to the naming, I believe the Human-in-the-loop is the right
> phrase,
Thanks Wei, I really appreciate the work, and will review it as soon as
possible.
With respect to the naming, I believe the Human-in-the-loop is the right
phrase, because that is recognized as such both in older "legacy" systems,
as well as the new AI solutions. I agree that it may be less than id
ook the action item to follow up with potential
refinements to reduce release friction.
Vikram Koka
Chief Strategy Officer
Email: vik...@astronomer.io
<https://www.astronomer.io/>
.
Everyone is encouraged to vote, although only PMC members and Committer's
votes are considered binding.
Since Jens and I are co-authoring this, please consider this our +2 :)
Best regards,
Vikram
--
Vikram Koka
Chief Strategy Officer
Email: vik...@astronomer.io
<https://www.astronomer.io/>
grade 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/>
iation
of the "deferred task state". TBD as we get closer to implementation.
For flow (3), the input data will be passed using XCom to subsequent tasks.
As detailed above, the technical changes are fairly small. Any feedback is
welcome.
Best regards,
Vikram
--
Vikram Koka
Chief Str
nce/pages/viewpage.action?pageId=308153072#Airflow3Devcall:MeetingNotes-ProposedAgenda.8>
or
send me an email.
The summary of the call will also be sent to the mailing list and posted on
the same wiki page.
Looking forward to seeing you all soon,
Vikram
--
Vikram Koka
Chief Strategy Officer
Pavan,
>From a concept perspective and strategic direction, I am in 100% agreement.
I have also been thinking about this and submitted a talk for the Airflow
Summit on this topic.
I am unsure of this particular package, but will look into it to understand
more.
The place where I do have concerns
Great job Pavan and team!
3 minutes sounds amazing. Wonderful work!
Vikram
On Fri, May 9, 2025 at 9:19 AM Aritra Basu wrote:
> Great job Pavan and team!
> --
> Regards,
> Aritra Basu
>
> On Fri, 9 May 2025, 9:33 pm Buğra Öztürk, wrote:
>
> > Excellent work! The process is now significantly st
Oh, excellent work!
Excited to see this working.
Thank you,
Vikram
On Fri, May 9, 2025 at 2:24 PM Jarek Potiuk wrote:
> Wooh
>
> On Fri, May 9, 2025 at 10:42 PM Daniel Standish
> wrote:
>
> > great!
> >
> > On Fri, May 9, 2025 at 12:54 PM Kaxil Naik wrote:
> >
> > > Hey all,
> > >
> > > I
s here was the UX around doc versions on the website, being too
subtle and not obvious to users about the differences between
2.x and 3.0
syntax. The action item for Jarek and Elad was to look at the
docs UX to
see if this could be made more obvious.
- 3.1 release scope
That's awesome.
Docs are critically important and shoutout to Constance for all the hard
work on those!
Vikram
On Fri, May 9, 2025 at 10:57 AM Briana Okyere
wrote:
> Hey All,
>
> The results are in! There were a ton of incredible PR's up for nomination
> this month- congrats to all who were nom
org/confluence/pages/viewpage.action?pageId=308153072#Airflow3Devcall:MeetingNotes-8May2025>
or
send me an email.
The summary of the call will also be sent to the mailing list and posted on
the same wiki page.
Looking forward to seeing you all soon,
Vikram
--
Vikram Koka
Chief Strategy Officer
Thanks Kaxil, 242 issues closed in this patch release!
That's amazing!
Vikram
On Tue, May 6, 2025 at 2:49 PM Kaxil Naik wrote:
> Docker images are now available
>
> docker pull apache/airflow:3.0.1.rc1
> docker pull apache/airflow:3.0.1.rc1-python3.12
> docker pull apache/airflow:3.0.1.rc1-py
Kaxil,
That's excellent!
Thank you for the update.
Vikram
On Tue, Apr 29, 2025 at 12:22 PM Jens Scheffler
wrote:
> Cool!
>
> This means also the "backport-to-2-10-test" is removed (or should not be
> used anymore)?
>
> On 29.04.25 20:02, Amogh Desai wrote:
> > Awesome. Thanks for the update
>
regroup the week after.
Our next dev call will take place the following week, on Thursday, May 8th,
at the same time.
Best regards,
Vikram
--
Vikram Koka
Chief Strategy Officer
Email: vik...@astronomer.io
<https://www.astronomer.io/>
working hard
towards the release, so there is no agenda, but purely an opportunity to
get together virtually as a team.
We can get back to more cognitively challenging conversations such as 3.0+
releases after a week.
Looking forward to seeing you all soon,
Vikram
--
Vikram Koka
Chief Strategy Officer
Awesome!
On Tue, Apr 22, 2025 at 8:53 AM Jarek Potiuk wrote:
> cool!
>
> On Tue, Apr 22, 2025 at 5:52 PM Kaxil Naik wrote:
>
> > fyi: Docker images coming soon :)
> >
> > On Tue, 22 Apr 2025 at 21:18, Kaxil Naik wrote:
> >
> > > Dear Airflow community,
> > >
> > > I'm happy to announce that A
Here's my belated +1 (binding)
Vikram
On Tue, Apr 22, 2025 at 5:57 AM Kaxil Naik wrote:
> Hello Airflow Community,
>
> The vote to release Apache Airflow version 3.0.0 based on 3.0.0rc4 &Task
> SDK 1.0.0 from 1.0.0rc4 is now closed.
>
> The vote PASSED with 8 binding "+1", 14 non-binding "+1"
Awesome!
Thank you, Elad and Jens!
Vikram
On Mon, Apr 21, 2025 at 3:42 PM Kaxil Naik wrote:
> 🎉
>
> On Tue, 22 Apr 2025 at 00:26, Jens Scheffler
> wrote:
>
> > Thanks Elad for releasing!
> >
> > Wow, I am proud that almost exactly 12 month after starting AIP-69
> > (
> >
> https://cwiki.apache
Thank you Kaxil, and to everyone who contributed to this release.
Amazing teamwork and grit!
Vikram
On Sat, Apr 19, 2025 at 5:17 AM Kaxil Naik wrote:
> Docker images are now available:
>
> apache/airflow:slim-3.0.0rc4-python3.9
> apache/airflow:slim-3.0.0rc4-python3.10
> apache/airflow:slim-3.
Thanks Ash.
On Sat, Apr 19, 2025 at 12:27 AM Ash Berlin-Taylor wrote:
> -1 I’m afraid. We’ve noticed a fairly major issue where due to the removal
> of FAB from core the Connections add or edit forms would 500.
>
> We’ve merged a fix to main, cherry picked it to v3-0-test and will aim to
> get a
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 regress
call
- Edge provider naming discussion
2. Development updates and presentations
- Test plan / Issue statistics update (Rahul Vats and Vikram Koka)
3. Discussions
- TBD
For additions to the agenda, please feel free to add a comment to the wiki
page
<https://cwiki.apache.org/confluen
Awesome! It's wonderful to see this.
Thank you Kaxil, Ash, Elad, Jarek, Rahul and everyone else who contributed
to this and made this happen!
115 commits in the last couple of days! Wow!
Vikram
On Wed, Apr 16, 2025 at 8:49 AM Kaxil Naik wrote:
> Hey fellow Airflowers,
>
> I am thrilled to ann
+1 to what Ash, Jarek, and Kaxil said above.
Let's chat in late May or June on this topic.
On Tue, Apr 15, 2025 at 7:05 AM Kaxil Naik wrote:
> Yeah, no strength or bandwidth right now for a discussion. And would very
> much prefer we focus on getting 3.0.0 out and any bug fixes after that
>
> O
Shyam,
First off, I'm really glad to hear that Couchbase is interested in a deeper
integration with Airflow and that Couchbase users are already finding value
in it.
Just to follow up with a couple of specific questions around your request:
Could you share more about what's missing today with the
python3.9
>
> Enjoy!
> -ash
>
> > On 10 Apr 2025, at 18:16, Jarek Potiuk wrote:
> >
> > Fantastic!
> >
> > On Thu, Apr 10, 2025 at 1:16 PM Vikram Koka >
> > wrote:
> >
> >> Awesome!
> >>
> >> Thank y
Awesome!
Thank you Kaxil and everyone who contributed to this release.
Looking forward to testing this out and responding with my vote :)
Vikram
On Thu, Apr 10, 2025 at 9:53 AM Kaxil Naik wrote:
> Like last time, docker images are still building! I will email here once
> they are published.
>
me.
Thank you all for the great teamwork!
Vikram
--
Vikram Koka
Chief Strategy Officer
Email: vik...@astronomer.io
<https://www.astronomer.io/>
; Regards,
> > >> Amogh Desai
> > >>
> > >>
> > >> On Fri, Apr 4, 2025 at 5:18 AM Kaxil Naik
> wrote:
> > >>
> > >>> Couldn’t sleep so there you go!
> > >>>
> > >>> Following imag
Brian,
Adding to Jarek's response above, I am happy to engage with them and help
answer the questions.
Please let me know.
Vikram
On Tue, Apr 8, 2025 at 6:43 AM Jarek Potiuk wrote:
> Hey Brian,
>
> I believe the devlist has not been copied in your previous email which was
> apparently address
Very cool!
Great work here! Love the "FAB-light" state.
On Mon, Apr 7, 2025 at 12:22 PM Jarek Potiuk wrote:
> Cool. We are now FAB-light (not yet FAB-less, but that's still a win).
>
> On Mon, Apr 7, 2025 at 3:11 PM Bishundeo, Rajeshwar
> wrote:
>
> > Wow. Major milestone in the history of Air
Awesome!
Thank you Kaxil and everyone who contributed to this release!
Vikram
On Thu, Mar 20, 2025 at 12:55 PM Jarek Potiuk wrote:
> Wowowowowwowow
>
> On Thu, Mar 20, 2025 at 8:54 PM Kaxil Naik wrote:
>
> > Dear Airflow Community,
> >
> > I am thrilled to announce the availability of Apache
Awesome, Thank you Jed!
On Tue, Apr 1, 2025 at 8:17 PM Jed Cunningham
wrote:
> Dear Airflow community,
>
> I am pleased to announce that we have released Apache Airflow Helm chart
> 1.16.0 🎉 🎊
>
> The source release, as well as the "binary" Helm Chart release, are
> available:
>
> 📦 Official S
core==3.0.0.rc1
>
> It’s a quirk of the RC naming, we’ll fix it and get the docker images
> build.
>
> -ash
>
> > On 3 Apr 2025, at 22:12, Vikram Koka
> wrote:
> >
> > Awesome!
> > Thank you Kaxil for all your work and also thank you to all the
> &
Awesome!
Thank you Kaxil for all your work and also thank you to all the
contributors whose hard work and dedication made this release a reality.
Best regards,
Vikram
On Thu, Apr 3, 2025 at 2:08 PM Kaxil Naik wrote:
> Docker images will be out soon too.
>
> On Fri, 4 Apr 2025 at 02:35, Kaxil N
Wei,
Really appreciate the update.
Thank you for the follow through,
Vikram
On Wed, Apr 2, 2025 at 8:37 PM Wei Lee wrote:
> Yep, just want to make sure my understanding is correct.
>
> ---
>
> Follow up on the discussion of the required/suggested changes.
>
> I list down what we have in ruff
rk!
Vikram
--
Vikram Koka
Chief Strategy Officer
Email: vik...@astronomer.io
<https://www.astronomer.io/>
A little stronger than Jed actually and for very similar reasons.
My view is that Airflow 3 is a new foundation and I very much believe that
there will be multiple, different bundling mechanisms.
I don't think we should include the "git-provider" as a required
dependency.
Vikram
On Mon, Mar 31,
uld 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/>
eeing you all soon,
Vikram
--
Vikram Koka
Chief Strategy Officer
Email: vik...@astronomer.io
<https://www.astronomer.io/>
are very close to release.
- Vikram to update the calendar invite to be weekly and to send
out a reminder if a meeting is required that week.
Vikram Koka
Chief Strategy Officer
Email: vik...@astronomer.io
<https://www.astronomer.io/>
I completely agree regarding transparency, having options expressed in
writing, and tracking decisions.
I also support the ASF philosophy that voting should only happen on the dev
list.
However, treating the dev list as the only acceptable mechanism for
discussion feels overly burdensome, in my h
Excellent, good work Vincent!
Thank you for taking care of this and sharing all the details here.
Vikram
On Fri, Mar 21, 2025 at 1:58 PM Buğra Öztürk
wrote:
> Great work Vincent! Thanks for the details!
>
> On Fri, Mar 21, 2025 at 2:49 PM Bishundeo, Rajeshwar
> wrote:
>
> > Awesome job Vince
nt to the wiki
> page
> <https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=308153072#Airflow3Devcall:MeetingNotes-ProposedAgenda.4>
> or
> send me an email or slack message.
> The summary of the call will also be sent to the mailing list and posted
> on the same wi
072#Airflow3Devcall:MeetingNotes-ProposedAgenda.4>
or
send me an email or slack message.
The summary of the call will also be sent to the mailing list and posted on
the same wiki page.
Looking forward to seeing you all soon,
Vikram
--
Vikram Koka
Chief Strategy Officer
Email: vik...@astronomer.io
Congratulations Shubham, Bugra, Liu Zhe You, and Kalyan!
Very well deserved!
Vikram
On Fri, Mar 14, 2025 at 6:23 PM Vincent Beck wrote:
> Congrats everyone, well deserved! A lot of hard work!
>
> On 2025/03/14 12:48:46 Hemkumar Chheda wrote:
> > Fantastic News! Congratulations Everyone 🎉
> >
>
+1 on getting rid of the Sequential Executor for sure.
On Mon, Dec 23, 2024 at 11:32 AM Amogh Desai
wrote:
> Hi All,
>
> To share some insights from a persona who just wants to evaluate "airflow"
> as a potential option
> for their use cases, they shouldn't need to have to set up `uv`, `breez
ause it was
changing every
day.
- The team was very appreciative of Rahul's update.
- Milestone update (Vikram Koka)
- Feature completeness and road to RCs
- Vikram shared the updated Airflow 3 dev milestones
<https://cwiki.apache.org/confluence/dis
Awesome!
Thank you Kaxil, Jed, and all the contributors to this release. It is great
to see this coming together and weekly cadence is super helpful.
Vikram
On Thu, Mar 13, 2025 at 11:36 PM Kaxil Naik wrote:
> Dear Airflow Community,
>
> I am thrilled to announce the availability of Apache Air
Awesome!
Thank you Jed and everyone who contributed to the release.
Love the regular cadence and great to see this come together!
Vikram
On Thu, Mar 6, 2025 at 11:33 AM Jed Cunningham
wrote:
> Dear Airflow Community,
>
> I am thrilled to announce the availability of Apache Airflow 3.0.0.beta2
. Development updates and presentations
- Update on AIP-72 Task Execution Interface aka Task SDK
Short circuit and Branch operators (Shahar Epstein)
- Test plan update (Rahul Vats)
- Milestone update (Vikram Koka)
- TBD
3. Discussions
- Packaging update - open items (Ash Berlin-Taylor, Jed Cunningham
Awesome!
Thank you Jed for pulling this together.
As Jed said, a huge thank you to all the contributors who made this release
happen. I am consistently energized by the amazing Airflow Community.
Best regards,
Vikram
On Thu, Feb 27, 2025 at 6:20 PM Jed Cunningham
wrote:
> Dear Airflow Communi
+1 for 46939
Thought it was a great UX jump.
On Tue, Feb 25, 2025 at 12:56 PM Jarek Potiuk wrote:
> Can we proactively vote on https://github.com/apache/airflow/pull/46942 ?
> I hope we will merge it before the end of the month :)
>
> [image: image.png]
>
>
> On Tue, Feb 25, 2025 at 9:53 PM Je
#2 for me as well
On Tue, Feb 25, 2025 at 1:49 PM Ferruzzi, Dennis
wrote:
> #2 seems like the right answer to me as well
>
>
> - ferruzzi
>
>
>
> From: Constance Martineau
> Sent: Tuesday, February 25, 2025 7:45 AM
> To: dev@airflow.apache.org
> Subject: RE: [E
low 2.x vs. 3.x including the implications for Provider
releases going
forward.
- The decision was to take this to the mailing list.
Vikram Koka
Chief Strategy Officer
Email: vik...@astronomer.io
<https://www.astronomer.io/>
Awesome!
Thank you Jed and everyone who contributed to making this happen!
Vikram
On Thu, Feb 20, 2025 at 2:40 PM Jed Cunningham
wrote:
> Dear Airflow Community,
>
> I am thrilled to announce the availability of *Apache Airflow 3.0.0.alpha4*
> for testing! Airflow 3.0 marks a significant milest
.
Looking forward to seeing you all soon,
Vikram
--
Vikram Koka
Chief Strategy Officer
Email: vik...@astronomer.io
<https://www.astronomer.io/>
I stayed out of this discussion for the longest time, but I really try to
avoid "naming" discussions.
However, the extensions needed to Airflow for enhanced AI capabilities such
as cyclic operations and "human in the loop" workflows is something I have
been thinking a fair bit about. I also agree
Thanks for starting this thread, Jed.
Around September last year, I was pessimistic about when this would happen.
I have been very impressed by our rate of progress on this set of AIPs over
the last few months.
I see the visible progress even across the alpha releases and am really
pleased by wher
; >>> +1 yay! event driven scheduling soon
> >>>
> >>> Regards,
> >>> Avi
> >>>
> >>> On Thu, Feb 13, 2025 at 2:02 AM Wei Lee wrote:
> >>>
> >>>> +1 to this idea!
> >>>>
> >>>>
Utkarsh and Jed,
Thank you for publishing this as scheduled.
Great way to follow through on the "If it hurts, do it more often"
principle.
It is great to see the list of "open items" reduced in each alpha.
Thank you to all the contributors, great job!
Best regards,
Vikram
On Thu, Feb 13, 2025
Amazing work team!
Kudos to everyone who contributed to this effort.
It was wonderful to see this coming together and I was amazed how quickly
all of you made this happen.
Vikram
On Tue, Feb 11, 2025 at 9:10 AM Shahar Epstein wrote:
> Thanks Jarek and everyone involved, great step!
>
>
> Shah
much a work in progress draft and is intended
to solicit feedback, rather than in any way a completed incarnation.
Please feel free to comment on the PR directly or reach out to me over
email or slack.
Best regards,
Vikram
--
Vikram Koka
Chief Strategy Officer
Email: vik...@astronomer.io
<https://www.astronomer.io/>
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
Thanks for sending this out, Ash.
On Thu, Feb 6, 2025 at 6:10 AM Ash Berlin-Taylor wrote:
> Hi all,
>
> A reminder and notice to all committers: now that we have cut the first
> alpha version of Airflow 3.0 please be extra careful about what you merge
> to main. Please don’t merge any new featur
Awesome!
Great to see the consistent progress week over week.
Thank you all for the wonderful teamwork,
Vikram
On Thu, Feb 6, 2025 at 11:28 AM Jarek Potiuk wrote:
> wooohooo. !
>
> On Thu, Feb 6, 2025 at 8:20 PM Utkarsh Sharma
> wrote:
>
> > Dear Airflow Community,
> >
> > I am thrilled
pache.org/confluence/display/AIRFLOW/AIP-38+Modern+Web+Application>
-
- New Trigger Form UI by Shubham Raj and Jens Scheffler
- Test plan update (Rahul Vats)
- TBD
3. Discussions
- Milestone and workstream update (Vikram Koka)
- TBD
For additions to the agenda, please feel free to add a co
Thanks Shubham, Amogh and the rest of the team for the kind words and the
outstanding teamwork!
With respect to bug tracking, I request everyone to report issues with the
version tag of "3.0.0alpha1".
We don't have a separate template for this, but can add one if the need
becomes apparent over the
This is fantastic! Congratulations to everyone on this huge milestone.
Thank you all for your hard work in getting us to this point. I am truly
proud to be a part of this team.
Best regards,
Vikram
On Fri, Jan 31, 2025 at 5:17 PM Jed Cunningham
wrote:
> Dear Airflow Community,
>
> I am thrille
Vincent,
Thank you for taking the feedback and the quick update.
Vikram
On 2025/01/29 19:12:17 "Beck, Vincent" wrote:
> Hello everyone,
>
> During my AIP-82 demo at the last Airflow 3 dev call, I highlighted potential
> issues if users select an incorrect trigger when scheduling DAGs using
automated 90+% of the work, but needed human intervention
for the last
little bit. He walked the team through a quick run of this script to
illustrate.
- Discussion Topics
- Milestone update and progress Vikram Koka
<https://cwiki.apache.org/confluence/displ
Task Commands Remote vs. Local? (Bugra Ozturk)
(document link
<https://docs.google.com/document/d/1BSEQxKEOArPRCclfCrAjAN5hjC56vG0R5nZPc3pxF9Y/edit?usp=sharing>
)
- Airflow 2.11 followup (Jens Scheffler and Kaxil Naik)
- Milestone and scope update (Vikram Koka)
For additions to the agenda, plea
Agreed.
Thanks for flagging these Jarek!
On Tue, Jan 21, 2025 at 2:34 PM Jarek Potiuk wrote:
> Seems that we have a flood of AI generated feature requests for Airflow,
> The issues look somewhat legitimate, with somewhat related content, but
> they are wordy and make no sense when you read the
+1 binding.
Thank you Daniel Standish and TP for all the detailed work on this!
On Tue, Jan 21, 2025 at 11:45 AM Jarek Potiuk wrote:
> Just to clarify - both +1s from me and TP are binding - committer votes are
> binding on that one ->
> https://www.apache.org/foundation/voting.html#votes-on-
Thanks Kaxil, I agree with that conclusion.
Thanks everyone for participating in the discussion.
On Tue, Jan 14, 2025 at 11:46 AM Kaxil Naik wrote:
> Thanks everyone for the discussion. The concerns raised about deferrable
> are valid and given the time and scope we already have for 3.0, let's
ng to have something available for Jan - not sure if
> this is still the same plan?
>
> -- Rajesh
>
>
>
>
>
>
> On 2025-01-09, 11:44 PM, "Vikram Koka" <mailto:vik...@astronomer.io.inva>LID> wrote:
>
>
> CAUTION: This email originated from
Wonderful job!
Great to see progress here, so quickly after the discussion last week.
Vikram
On Mon, Jan 13, 2025 at 10:47 AM Elad Kalif wrote:
> Great work!
>
> On Mon, Jan 13, 2025 at 7:05 PM Kaxil Naik wrote:
>
> > Kudos Shahar and all who helped 🎉
> >
> > On Mon, 13 Jan 2025 at 22:29, Ja
I agree this makes sense.
I was originally concerned that this would make it more difficult to ensure
compatibility across providers for capabilities such as common.sql,
objectstore, and so on.
However, seeing that the "common" pattern would remain the same and it's
only the code layout that is ch
+1 on this
For many reasons, which have already been brought up in the thread.
On Fri, Jan 10, 2025 at 7:30 AM Igor Kholopov
wrote:
> +1, there are a lot of old code paths that exist only because of the
> embedding in the scheduler support. Focusing on a single supported mode of
> operation wi
Jarek to start an async discussion around the doc build issues
- Jens / Kaxil to start an async discussion around the pros/cons for
the 2.11 release.
---
Vikram Koka
Chief Strategy Officer
Email: vik...@astronomer.io
<https://www.astronomer.io/>
Hi everyone,
Here is a quick reminder that we have our Airflow 3 dev call the day after
tomorrow at Thursday, 9th January 2025 at 8AM PST (11 am EST | 4 pm UTC /
GMT).
Proposed agenda:
1. Check in on action items from the last call
- AIP-83 amendment aka Data completeness discussion follow-up (Da
he next dev call
will be on the 9th of January, 2025 instead of the 2nd of January.
--
Vikram Koka
Chief Strategy Officer
Email: vik...@astronomer.io
<https://www.astronomer.io/>
Daniel,
Thank you for writing this up. I commented on the wiki page.
Vikram
On Fri, Dec 20, 2024 at 3:26 PM Daniel Standish
wrote:
> OK folks, let's get into it.
>
> AIP-83 fundamentally alters Airflow's dag run semantics in a way that I
> think no one fully appreciated when it was proposed a
ageId=308153072#Airflow3Devcall:MeetingNotes-(Proposed)Agenda.4>
or
send me an email.
The summary of the call will also be sent to the mailing list and posted on
the same wiki page.
Looking forward to seeing you all soon,
Vikram
--
Vikram Koka
Chief Strategy Officer
Email: vik...@astr
implements plug-in backwards compatibility.
- Vikram Koka expressed appreciation for the progress and asked
about the expected timing of the remainder of the items to be done and
their response was outside of the New UI completeness
blocker, the other
items c
Sure TP, sounds good!
On Tue, Dec 3, 2024 at 9:13 PM Tzu-ping Chung
wrote:
> Hi,
>
> Since the dev call is quite late in my timezone, I’ll share a recording
> for the update before the meeting. Same as last time for AIP-74.
>
> TP
>
> > On 4 Dec 2024, at 08:13, Vikra
1 - 100 of 333 matches
Mail list logo
