Re: [LAZY CONSENSUS] deprecate "dependency detector" pluggability

This vote has officially passed. On Thu, Jul 21, 2022 at 3:59 PM Jarek Potiuk wrote: > Was it really *puggable* ? I would have never guessed. Not so lazy > consensus here > > On Thu, Jul 21, 2022 at 11:44 PM Daniel Standish > wrote: > > > > Sorry --- sunday july 24 >

Re: Remove from email list

1. here's how to do 2. The preferred channel for discussion is using the official Apache Airflow mailing lists. To subscribe, send an email to: - Users list (archive ): users-subscr...@airflow.apache.org

Remove from email list

Hi, I would like to unsubscribe from this email list. -- Forwarded message - From: Sarwat Fatima Date: Thu, Jul 28, 2022, 1:20 AM Subject: Unsubscribe To: Hi, I would like to unsubscribe from this email list. Thankyou.

[DISCUSS] consolidate dag scheduling params

As of airflow 2.3, we have two mutually-exclusive scheduling params, `schedule_interval` and `timetable`. As it stands now, AIP-48 will be adding a *third* such param, `schedule_on`. I think it would probably be best to consolidate these into one single scheduling param. What do you think?

[VOTE] Release Airflow Python Client 2.3.0 based on 2.3.0rc1

Hello everyone, I have cut the first release candidate for the Airflow Python Client 2.3.0. The client consists of APIs corresponding to REST APIs available in *Apache Airflow 2.3.3* release. This email is calling for a vote on the release, which will last for 72 hours. Consider this my (binding)

Re: [DISCUSS] Trimming down Airlfow Versions in issues

Other ideas/opinions here? On Thu, Jul 21, 2022 at 2:05 PM Jarek Potiuk wrote: > Just to comment. I do not think everyone will be able to upgrade (and > if they don't the "discussion" route is still possible). > > This is more of a "psychological barrier" that I am talking about > here. I've