Re: [VOTE] The daskexecutor, cncf.provider, celery providers in 2.7.0. as regular not-preinstalled providers

The vote is concluded. Unanimous decision on a) - we are not going to pre-install the daskexecutor, celery, cncf.kubernetes providers. Binding votes: 9 (a) Jarek Potiuk, Ash Berlin-Taylor, Hussein Awala, Pierre Jeambrun, Vincent Beck, Jed Cunningham, Dennis Ferruzzi, Vikram Koka, Elad Kalif Non

[ANNOUNCE] Apache Airflow Providers prepared on July 29, 2023 are released

Dear Airflow community, I'm happy to announce that new versions of Airflow Providers packages were just released. https://pypi.org/project/apache-airflow-providers-amazon/8.4.0/ https://pypi.org/project/apache-airflow-providers-apache-beam/5.2.0/ https://pypi.org/project/apache-airflow-provider

[RESULT][VOTE] Airflow Providers - release of July 29, 2023

Hello, Apache Airflow Providers (based on RC1) have been accepted. 4 "+1" binding votes received: - Elad Kalif (binding) - Jarek Potiuk (binding) - Hussein Awala (binding) - Ephraim Anierobi (binding) 8 "+1" non-binding votes received: - Pankaj Koti - Wei Lee - Rahul Vats - Phani Kumar - Utkar

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

Thank you all vote is now closed On Tue, Aug 1, 2023 at 6:32 PM Jarek Potiuk wrote: > We just got confirmation from Vinc that my hypothesis was right: > https://github.com/apache/airflow/issues/32973#issuecomment-1660540544. > > The hanging test succeeds in the "Core" group of tests for the AWS

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

We just got confirmation from Vinc that my hypothesis was right: https://github.com/apache/airflow/issues/32973#issuecomment-1660540544. The hanging test succeeds in the "Core" group of tests for the AWS environment, so it confirms the "hanging" effect results from moving the test to "Providers" s

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

Thanks Elad, Jarek, and Niko, With that context, I agree it’s not a blocker and it enables the Airflow 2.7 release as well On Tue, Aug 1, 2023 at 6:17 AM Elad Kalif wrote: > Cool. > so this does not block provider release. > The goal is to allow us to start testing Airflow 2.7 if we discover an

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

Cool. so this does not block provider release. The goal is to allow us to start testing Airflow 2.7 if we discover an issue we can always cut another provider release. On Tue, Aug 1, 2023 at 2:01 PM Jarek Potiuk wrote: > I prepared two Draft / Experiment PRs to test my hypothesis: > > * https://

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

I prepared two Draft / Experiment PRs to test my hypothesis: * https://github.com/apache/airflow/pull/33002 [EXPERIMENT] Bring back celery to core - leave tests in provider #33002 * https://github.com/apache/airflow/pull/33001 [EXPERIMENT] Tests for Celery executor moved back to core #33001 I wil

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

Thanks Vikram for raising it. I think we should indeed take a closer look at it - but it's not really a blocker for Celery provider release - and I have an idea how to better examine the root cause. Context: The celery issue is - most likely a race condition in the tests, not in the Celery provid

Re: [VOTE] The daskexecutor, cncf.provider, celery providers in 2.7.0. as regular not-preinstalled providers

I also vote for [a] On Tue, Aug 1, 2023 at 8:40 AM Vikram Koka wrote: > I am a little torn on this, but with the separation already in place, I > would also vote for option (a). > > > On Mon, Jul 31, 2023 at 1:48 PM Ferruzzi, Dennis > wrote: > > > Pretty unanimous so far, but I'll also say [a].