Hi Airflow Devs,
Following-up on the discussions in
https://lists.apache.org/thread/6znvd5rtqnxt5r4hys7qn64j5mflr9g1 I'd
like to cast a VOTE - even if the discussion is fresh.. but my aim/call
would be to improve the problem in the core with Airflow 3.2.0 not to
have users stuck in this situation for additional multiple months (as it
would be a new feature, not a fix most probably not applicable to a fix
release)
As we discussed two options we can not have a simple +/- Vote, therefore
I call for a VOTE with options, please rate from 0 to +1 for the option
and only -1 on an option to call for veto.
* OPTION A) Integrate feature to directly queue tasks from Triggerer
as of PR https://github.com/apache/airflow/pull/63489 in Airflow 3.2.0
* OPTION B) Extend Triggerer to support XCom, change KPO to end from
Triggerer as of PR https://github.com/apache/airflow/pull/64068
(Core) with Target Airflow 3.2.0 and
https://github.com/apache/airflow/pull/64069 (KPO Adjustment)
* OPTION C) Do not immediately change this for Airflow 3.2.0, further
discuss alternatives, e.g. raise an AIP
For details of the soluitions please check the discussion thread (might
need a bit of reading!) and the linked PRs
The VOTE is open for the next 72 hours to be done before RC1, until
2026-03-29 23:59 CET - I will sum-up all vores except any potential veto
and will report the summary.
My Vote is:
* Option A: +0.8
* Option B: +1
* Option C: 0
Thanks,
Jens
