+1 (binding) - checked reproducibility, licences, signatures, checksum and
tested my changes
On Tue, 10 Jun 2025 at 03:49, Wei Lee wrote:
> +1 non-binding, tested my changes and a few dags
>
> Best,
> Wei
>
> > On Jun 10, 2025, at 3:27 AM, Rahul Vats wrote:
> >
> > +1 non binding. Tried runnin
+1 (binding) - Checked SVN, Checksums, Reproducible package build,
Licenses, Signatures
On 10.06.25 22:27, Kaxil Naik wrote:
Hey fellow Airflowers,
I have cut the first release candidate for the Apache Airflow Python Client
3.0.2.
This email is calling for a vote on the release,
which will las
Hi Devs,
alongside and after VOTE of the new i18 policy and aiming to follow the
new policy as beta tester I'd like to suggest and invite
- @TJaniF
- @m1racoli
... as additional German Native speakers (I account swiss as being
almost exactly like German :-D ). Both are working professionall
This release looked small but has tons of bug fixes and CI stability fixes.
Good work as usual to everyone
who helped in contributing to the release! 👏
Thanks & Regards,
Amogh Desai
On Tue, Jun 10, 2025 at 8:39 PM Kaxil Naik wrote:
> Dear Airflow community,
>
> I'm happy to announce that Airfl
Dear Airflow community,
I'm happy to announce that Airflow 3.0.2 was just released.
The released sources and packages can be downloaded via
https://airflow.apache.org/docs/apache-airflow/3.0.2
/installation/installing-from-sources.html
Other installation methods are described in
https://airflow.
Based on the feedback so far, deadline_time got more votes. So, renaming the
column to deadline_time.
On 2025/05/28 07:01:55 Buğra Öztürk wrote:
> I agree deadline.time could be a naming problems in the future. deadline_at
> looks more intuitive to me
>
> On Wed, 28 May 2025, 08:01 Amogh Desai
Hey fellow Airflowers,
I have cut the first release candidate for the Apache Airflow Python Client
3.0.2.
This email is calling for a vote on the release,
which will last for 72 hours. Consider this my (binding) +1.
Airflow Client 3.0.2rc1 is available at:
https://dist.apache.org/repos/dist/dev/a
Hey All,
Here is the recording from our June 2025 Airflow Town Hall! <
https://youtu.be/8orWFgvymow>
A big thanks to our speakers; Tati Martins, Pankaj Singh, Mihir Samant,
Brent Bovenzi, Mara Ruvalcaba- and to our host Kenten Danas!
Reminder: Airflow Summit 2025 Early Bird Ticket sale ends June
For backward compatibility purposes I also think the default team is a good
idea. On the API side, if a team is not provided, then the default team is
assigned.
> For newer versions, we should probably start adding `team_id__dag_id` in
> the dag_id column.
> Fallback to "default" if not specifie
Oh I think you meant as an alternative solution.
I still do not like this solution because I feel like on the long run it will
bite us. Yes on the short term we would avoid massive migration on most of the
tables and we would not need to update a lot of requests but on the long run
this will ca
Like... XComs it makes sense to ship to object storage since it can be
necessary to share large amounts of data between tasks. But something to
track trigger state for event-driven scheduling should consistently be
small?
On Tue, Jun 10, 2025 at 1:58 PM Ryan Hatter
wrote:
> I don't think we shou
I don't think we should try to take on Kafka, but better supporting
event-driven scheduling is one of the oft-repeated highlights of Airflow 3.
IMO, it doesn't make sense to manage state using object storage. A simple
model in Airflow would be suitable.
On Mon, Jun 9, 2025 at 8:54 AM Jarek Potiuk
Hello Airflow Community,
The vote to release Apache Airflow version 3.0.2 based on 3.0.2rc2 &Task
SDK 1.0.2 from 1.0.2rc2 is now closed.
The vote PASSED with 4 binding "+1", 3 non-binding "+1" and 0 "-1" votes:
*"+1" Binding votes*:
- Kaxil Naik
- Jens Scheffler
- Jarek Potiuk
- Ephraim Anierobi
13 matches
Mail list logo
