Re: [VOTE] Airflow Providers prepared on July 12, 2023

2023-07-12 Thread Ephraim Anierobi
+1 (binding) Checked expected files, licenses, signatures & SHA512 On 2023/07/12 19:36:33 Elad Kalif wrote: > 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 o

[VOTE] Airflow Providers prepared on July 12, 2023

2023-07-12 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 July 15, 2023 07:35 PM UTC and until 3 binding +1 votes have been received. Consider this my (binding) +1. Airflow Pr

Re: [DISCUSS] Moving Dask Executor to a separate (optional?) dask provider

2023-07-12 Thread Oliveira, Niko
I think in a perfect world we'd only have the completely vendor neutral executors pre-installed (Local, Sequential, Debug) and anything else would need to be specifically installed by admins/users. I think if we were starting from scratch this would make the most sense, but clearly Kubernetes an

[DISCUSS] Moving Dask Executor to a separate (optional?) dask provider

2023-07-12 Thread Jarek Potiuk
Hello Everyone, A small follow up after K8S/Celery executors being moved: https://lists.apache.org/thread/7gyw7ty9vm0pokjxq7y3b1zw6mrlxfm8 We are in the process of moving Celery / Kubernetes executor (Celery almost complete and I am working on K8S next + some common discovery and config moving)