Hi Airflow-Devs!
Thanks for the (minimum) response of votes, with that I conclude that "Option
B" is to be made to close AIP-50. I'll raise a PR the next days for this.
Summary:
1 Binding Vote B
3 Non-Binding Votes B
No other opinions
Mit freundlichen Grüßen / Best regards
Jens Scheffler
What they said - option B for me as well
On 23 May 2023 15:49:58 BST, Collin McNulty
wrote:
>I also support Option B. +1 B, non-binding.
>
>Collin McNulty
>
>On Tue, May 23, 2023 at 9:33 AM Constance Martineau
> wrote:
>
>> Hello,
>>
>> I think Option B is reasonable. +1 for B, non-binding.
>>
I also support Option B. +1 B, non-binding.
Collin McNulty
On Tue, May 23, 2023 at 9:33 AM Constance Martineau
wrote:
> Hello,
>
> I think Option B is reasonable. +1 for B, non-binding.
>
> Constance
>
> On Mon, May 22, 2023 at 4:54 PM Scheffler Jens (XC-DX/ETV5)
> wrote:
>
> > Hi
Hello,
I think Option B is reasonable. +1 for B, non-binding.
Constance
On Mon, May 22, 2023 at 4:54 PM Scheffler Jens (XC-DX/ETV5)
wrote:
> Hi Airflow-Developers,
>
> It is not democracy if nobody makes a vote. I don't want to be a
> "dictator" but still propose Option B.
> As nobody
Well done, this is great!
I looked around on other projects for similar compatibility patches (numpy,
mypy, auto-sklearn etc...) and it seems there is no consensus on the
question. (feature, enhancement, misc etc.)
Excluding breeze image diff, the changeset is relatively small, I see no
harm in
We will start preparing the release ASAP with Elad, and we will run a
parallel vote on those released providers, so if there will be no
objections the lazy consensus will conclude 72 hours from now (Friday 10am
CEST).
On Tue, May 23, 2023 at 10:01 AM Jarek Potiuk wrote:
> Hello everyone,
>
> I
Hello everyone,
I had a short discussion with Elad and unless there is any objection, we
decided to bring back support for "min-airlfow-version" support for
pre-installed providers (common.sql, ftp, imap, http, sqlite). We will have
to release them ad-hoc now and `yank` the latest versions of
We do not have it described, but ...
Should we cherry-pick it for 2.6.2 ? Technically there is no problem doing
it, the changes for 3.11 were minimal, once dependencies have been updated,
and it opens up 3.11 for earlier spin for people who would want to use some
of its new features.
I'd be for
