+1 binding.
- Checked SVN
- Checked in Docker
- Checked reproducible package builds
- Checked licenses
- Checked Signatures
Installed the RC and checked if my cleanup code is present or not. It is
present and looks good!
Thanks & Regards,
Amogh Desai
On Wed, Jul 9, 2025 at 12:39 AM Jens Scheff
Hey folks,
tl;dr I’d like to get some thoughts on a proposal to use DB Manager for S3 Dag
Bundle versioning.
The initial commit for S3 Dag Bundles was recently merged [1] but it lacks
Bundle versioning (since this isn’t trivial with something like S3, like it is
with Git). The proposed solutio
Thanks Jarek for updated work,
Took a bit of time and re-read again, now it's more concise and nice to
see the update compared to initial proposal.
+1 binding.
Pavan
On Tue, Jul 8, 2025 at 8:24 PM Jens Scheffler
wrote:
> Thanks Jarek for the rework. I see added complexity for Multi-Team but
Thanks Jarek for the rework. I see added complexity for Multi-Team but
given the current state of 3.0 I think it is well thought to strip-off
complexity. Much better than the original AIP. I like the current
approach much more like the previous.
+1 binding.
Nit: Multi-Team Pluing support migh
+1 (binding) - Checked SVN, Check in Docker, Reproducible package build,
Licenses, Signatures
Unable to test amazon provider, so this is just the technical release check.
On 08.07.25 12:20, Elad Kalif wrote:
Hey all,
I have just cut amazon ad-hoc Airflow Provider package. This email is
callin
In case anyone's referring to the old PR, here is the link to the new PR
https://github.com/apache/airflow/pull/52868
Best,
Wei
On 2025/06/26 12:10:24 Wei Lee wrote:
> I agree with Ash's point. Given how other pipeline tools function, this
> appears to be a standard feature. Additionally, it se
Thanks Vikram and everyone for helping out communicating the design change of
AIP-90. The new PR is now ready. Would love to have some reviews. Thanks!
https://github.com/apache/airflow/pull/52868
Best,
Wei
On 2025/07/07 08:36:46 Eugen Kosteev wrote:
> Thank you!
>
> On Mon, Jul 7, 2025 at 10:
This vote is to update AIP-67 with clarifications. The old AIP is still
properly voted in. If we want to "unvote" AIP-67 in it's entirety - that
would be another - different vote I guess.
On Tue, Jul 8, 2025 at 2:13 PM Ash Berlin-Taylor wrote:
> Can I ask for clarification on what we are voting
Can I ask for clarification on what we are voting on here: Is it “the new
AIP-67 proposal vs the old one” or “the new AIP-67 vs nothing”?
> On 7 Jul 2025, at 19:26, Jarek Potiuk wrote:
>
> Hello Airflow community,
>
> I would like to call a vote on "reloaded" version of the AIP
> https://cwiki
Hey all,
I have just cut amazon ad-hoc Airflow Provider package. This email is
calling a vote on the release, which will last for 72 hours - which means
that it will end on July 11, 2025 10:15 AM UTC and until 3 binding +1 votes
have been received.
Consider this my (binding) +1.
Note: For amazo
> Not that I am against your idea and we can surely expand as we need but
we would not need to expand the
"core_and_task_sdk" if we put only the relevant items into it.
So if we move logging and config out, my question is what is really
relevant to "stay" in "core_and_task_sdk" ? And what we know
Yeah, I think what you are showcasing here is a step ahead of the
initial proposal from Ash.
>From the original proposal, the `core_and_task_sdk` *can* have the things
relevant to just those two
distros. Logging, Config are modules that might be needed by airflow-ctl
for example, so ideally, those
Thank you Ash and Amogh Desai for your insights and explanations.
The information you shared has been incredibly helpful and is contributing
a lot to my growth.
2025년 7월 8일 (화) 오후 2:54, Amogh Desai 님이 작성:
> Agreed, I personally also find the current way to be easier to read and in
> most
> cases
13 matches
Mail list logo
