Re: Marking issues & PRs for Airflow >3.0.0

2025-04-24 Thread Pavankumar Gopidesu
Yeah cool. Another thing I would like to mention. when PR cherry-picked using label backport-to-*. The default PR state is DRAFT on a backported branch. so please set it back to Read For Review. with this way the workflows will get triggered. Pavan On Thu, Apr 24, 2025 at 11:42 AM Amogh Desai w

[VOTE] Airflow Providers prepared on April 24, 2025

2025-04-24 Thread Elad Kalif
Hey all, I have just cut the new wave Airflow Providers packages. This email is calling a vote on the release, which will last for 72 hours - which means that it will end on April 27, 2025 11:15 AM UTC and until 3 binding +1 votes have been received. Consider this my (binding) +1. Airflow Provid

Re: [LAZY CONSENSUS] New Provider for Apache TinkerPop (Gremlin)

2025-04-24 Thread Ahmad Farhan
Hello All, I am excited to announce this provider has been merged now as Version 1.0.0 and should be published in the next providers' release. Thanks, Farhan On Tue, Mar 11, 2025 at 12:31 PM Ahmad Farhan wrote: > Hi, > Following the discussion in this thread: > https://lists.apache.org/thread/

Re: AW: [ANNOUNCE] Apache Airflow 3.0.0 Released

2025-04-24 Thread Constance Martineau
Congrats everybody. What a journey!! On Thu, Apr 24, 2025 at 6:09 AM Pierre Jeambrun wrote: > Amazing! Thanks to everybody that was involved > > On Wed, Apr 23, 2025 at 10:31 PM Buğra Öztürk > wrote: > > > Amazing milestone! Great work and collaboration! Congrats everyone! > > > > On Wed, Apr 2

Re: [LAZY CONSENSUS] New Provider for Apache TinkerPop (Gremlin)

2025-04-24 Thread Stephen Mallette
It's great to see this work make it to a merge state and looking forward to trying out the release version. Thanks! On Thu, Apr 24, 2025 at 7:16 AM Ahmad Farhan wrote: > Hello All, > > I am excited to announce this provider has been merged now as Version 1.0.0 > and should be published in the ne

Re: Marking issues & PRs for Airflow >3.0.0

2025-04-24 Thread Kaxil Naik
>From time to time, I will be cherry-picking things from GitHub milestones too to v3-0-test too to reduce the workload near the release date. On Thu, 24 Apr 2025 at 14:39, Kaxil Naik wrote: > Now that Airflow 3.0.0 is officially released, I have re-enabled the > `backport-to-v3-0-test` label. If

Re: Marking issues & PRs for Airflow >3.0.0

2025-04-24 Thread Kaxil Naik
Now that Airflow 3.0.0 is officially released, I have re-enabled the `backport-to-v3-0-test` label. If you (Reviews/Committers) want to guarantee that a PR is included in the next patch release, use `backport-to-v3-0-test` label on that PR before merging. This should work if there are no conflicts.

Re: Marking issues & PRs for Airflow >3.0.0

2025-04-24 Thread Jarek Potiuk
Cool. I would also suggest and encourage those who merge fixes to do so. If we all do the backporting with the label (before merging) or Github workflow/ cherry-picker tool (after) it makes it easier to keep `v3-0-test` branch "green" - there are some external factors that influence the "greenness

Re: AW: [ANNOUNCE] Apache Airflow 3.0.0 Released

2025-04-24 Thread Pierre Jeambrun
Amazing! Thanks to everybody that was involved On Wed, Apr 23, 2025 at 10:31 PM Buğra Öztürk wrote: > Amazing milestone! Great work and collaboration! Congrats everyone! > > On Wed, Apr 23, 2025 at 10:57 AM Michał Modras > wrote: > > > This is huge, congratulations to everyone involved! > > > >

Re: Marking issues & PRs for Airflow >3.0.0

2025-04-24 Thread Amogh Desai
Great thanks for the update Kaxil! It definitely is helpful. Thanks & Regards, Amogh Desai On Thu, Apr 24, 2025 at 3:47 PM Jarek Potiuk wrote: > Cool. I would also suggest and encourage those who merge fixes to do so. > > If we all do the backporting with the label (before merging) or Github

Re: [DISCUSS] When a DAG is paused, change the dag run state from running to failed.

2025-04-24 Thread Constance Martineau
I agree with Elad. If I pause a DAG, I expect for whatever is running to continue and for the scheduler to stop scheduling dag runs and new tasks. I don't think we should change the behaviour to fix a chart. That feels backwards. Separately: In my view, choosing to to prevent or run new tasks from

Re: [DISCUSS] When a DAG is paused, change the dag run state from running to failed.

2025-04-24 Thread Brent Bovenzi
Yeah, if we do a similar endpoint we should filter it to only include unpaused Dags. We do check if the dag is paused during auto refresh in a lot of places. On Fri, Apr 18, 2025 at 3:44 PM Pedro Nunes Leal wrote: > A 2025-04-03 19:28, Brent Bovenzi escreveu: > > The issue is that duration is ba

Re: [DISCUSS] When a DAG is paused, change the dag run state from running to failed.

2025-04-24 Thread Elad Kalif
I am -1 for changing this especially just to solve duration calculation. The current behavior is key for drain use case which is very useful. I don't think I will change my -1 before https://github.com/apache/airflow/issues/22006 is resolved On Thu, Apr 24, 2025 at 7:56 PM Brent Bovenzi wrote:

Re: [VOTE] Airflow Providers prepared on April 24, 2025

2025-04-24 Thread Jens Scheffler
Had no time testing but the PMC checks resulted in: +1 (binding) - Checked SVN, Check in Docker, Reproducible package build, Licenses, Signatures On 24.04.25 13:17, Elad Kalif wrote: Hey all, I have just cut the new wave Airflow Providers packages. This email is calling a vote on the release

Re: [VOTE] Airflow Providers prepared on April 24, 2025

2025-04-24 Thread Amogh Desai
+1 non binding Tested my changes, works fine: #49492 doc only change #49500 is a move from core => standard and I checked from downloaded wheel that, well its there: (airflow) ➜ apache_airflow_providers