You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@airflow.apache.org by Jarek Potiuk <ja...@potiuk.com> on 2023/11/24 17:51:57 UTC
[LAZY CONSENSUS] Remove 'daskexecutor' provider
Hello everyone,
This is a formal call for consensus to remove the daskexecutor provider.
All the details and proposal here
https://lists.apache.org/thread/ptwjf5g87lyl5476krt91bzfrm96pnb1
I believe we can remove it straight away - my announcement in
https://github.com/dask/community/issues/355 shows that a) dask community
is ok with it b) they appreciate our efforts to communicate it.
Just to remind - removal means "no further maintenance overhead/releases
unless there are security fixes needed". The sources for it will be removed
from main.
Users will be able to continue to use the released version of the provider
for future Airflow releases for as long as there are no conflicts that will
make installation of it impossible.
No need to respond to the email. If there are no objections, the lazy
consensus will be reached on Tuesday 28th, 7PM CET (6PM GMt).
Re: [LAZY CONSENSUS] Remove 'daskexecutor' provider
Posted by Jarek Potiuk <ja...@potiuk.com>.
Lazy consensus has been reached. I am proceeding with the removal of
daskexecutor provider.
On Fri, Nov 24, 2023 at 6:51 PM Jarek Potiuk <ja...@potiuk.com> wrote:
> Hello everyone,
>
> This is a formal call for consensus to remove the daskexecutor provider.
>
> All the details and proposal here
> https://lists.apache.org/thread/ptwjf5g87lyl5476krt91bzfrm96pnb1
>
> I believe we can remove it straight away - my announcement in
> https://github.com/dask/community/issues/355 shows that a) dask community
> is ok with it b) they appreciate our efforts to communicate it.
>
> Just to remind - removal means "no further maintenance overhead/releases
> unless there are security fixes needed". The sources for it will be removed
> from main.
>
> Users will be able to continue to use the released version of the provider
> for future Airflow releases for as long as there are no conflicts that will
> make installation of it impossible.
>
> No need to respond to the email. If there are no objections, the lazy
> consensus will be reached on Tuesday 28th, 7PM CET (6PM GMt).
>
>
>