-1 (binding) to standard provider +1 (binding) to the others On Sun, Sep 28, 2025 at 10:54 AM Elad Kalif <[email protected]> wrote:
> need 1 more binding vote > > On Sat, Sep 27, 2025 at 7:08 PM Elad Kalif <[email protected]> wrote: > > > standard provider will be excluded from this wave > > > > On Fri, Sep 26, 2025 at 1:59 AM Kaxil Naik <[email protected]> wrote: > > > >> Jed took care of it: https://github.com/apache/airflow/pull/56109 first > >> > >> On Thu, 25 Sept 2025 at 23:52, Kaxil Naik <[email protected]> wrote: > >> > >> > @j_scheffler <[email protected]> Yeah I noticed similar failure on > >> > different things too. https://github.com/apache/airflow/pull/56118 > >> fixes > >> > it & adds compat layer test now that 3.1.0 is released > >> > > >> > On Thu, 25 Sept 2025 at 23:01, Jens Scheffler <[email protected]> > >> wrote: > >> > > >> >> +1 (binding) - Checked SVN, Check in Docker, Reproducible package > >> build, > >> >> Licenses, Signatures > >> >> > >> >> Tested providers (especially Edge) in Breeze with latest main, and > >> 3.0.6 > >> >> - These look good. > >> >> > >> >> But testing with brand new released 3.1.0 fail in all examples being > >> >> parsed - assume it is related to standard provider: > >> >> > >> >> Therefore I'd -1 to standard provider release. > >> >> > >> >> Traceback (most recent call last): > >> >> File > >> >> > >> > "/usr/python/lib/python3.12/site-packages/airflow/serialization/serialized_objects.py", > >> >> line 1135, in detect_task_dependencies > >> >> from airflow.providers.standard.sensors.external_task import > >> >> ExternalTaskSensor > >> >> File > >> >> > >> > "/usr/python/lib/python3.12/site-packages/airflow/providers/standard/sensors/external_task.py", > >> >> line 55, in <module> > >> >> from airflow.dag_processing.dagbag import DagBag > >> >> ModuleNotFoundError: No module named 'airflow.dag_processing.dagbag' > >> >> > >> >> On 25.09.25 13:13, Blain David wrote: > >> >> > +1 approve for me > >> >> > > >> >> > -----Original Message----- > >> >> > From: Elad Kalif<[email protected]> > >> >> > Sent: 25 September 2025 10:24 > >> >> > To:[email protected] > >> >> > Subject: [VOTE] Airflow Providers prepared on September 25, 2025 > >> >> > > >> >> > EXTERNAL MAIL: Indien je de afzender van deze e-mail niet kent en > >> deze > >> >> niet vertrouwt, klik niet op een link of open geen bijlages. Bij > >> twijfel, > >> >> stuur deze e-mail als bijlage [email protected]<mailto: > >> >> [email protected]>. > >> >> > > >> >> > 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 September 28, 2025 08:20 AM UTC and until 3 > >> binding +1 > >> >> votes have been received. > >> >> > > >> >> > Consider this my (binding) +1. > >> >> > > >> >> > Airflow Providers are available at: > >> >> > https://dist.apache.org/repos/dist/dev/airflow/providers/ > >> >> > > >> >> > *apache-airflow-providers-<PROVIDER>-*.tar.gz* are the binary > Python > >> >> "sdist" release - they are also official "sources" for the Provider > >> >> distributions. > >> >> > > >> >> > *apache_airflow_providers_<PROVIDER>-*.whl are the binary Python > >> >> "wheel" release. > >> >> > > >> >> > The test procedure for PMC members is described in > >> >> > > >> >> > >> > https://github.com/apache/airflow/blob/main/dev/README_RELEASE_PROVIDERS.md#verify-the-release-candidate-by-pmc-members > >> >> > > >> >> > The test procedure for and Contributors who would like to test this > >> RC > >> >> is described in: > >> >> > > >> >> > >> > https://github.com/apache/airflow/blob/main/dev/README_RELEASE_PROVIDERS.md#verify-the-release-candidate-by-contributors > >> >> > > >> >> > > >> >> > Public keys are available at: > >> >> > https://dist.apache.org/repos/dist/release/airflow/KEYS > >> >> > > >> >> > Please vote accordingly: > >> >> > > >> >> > [ ] +1 approve > >> >> > [ ] +0 no opinion > >> >> > [ ] -1 disapprove with the reason > >> >> > > >> >> > Only votes from PMC members are binding, but members of the > community > >> >> are encouraged to test the release and vote with "(non-binding)". > >> >> > > >> >> > Please note that the version number excludes the 'rcX' string. > >> >> > This will allow us to rename the artifact without modifying the > >> >> artifact checksums when we actually release. > >> >> > > >> >> > The status of testing the providers by the community is kept here: > >> >> > https://github.com/apache/airflow/issues/56091 > >> >> > > >> >> > The issue is also the easiest way to see important PRs included in > >> the > >> >> RC candidates. > >> >> > Detailed changelog for the providers will be published in the > >> >> documentation after the RC candidates are released. > >> >> > > >> >> > You can find the RC packages in PyPI following these links: > >> >> > > >> >> > > https://pypi.org/project/apache-airflow-providers-celery/3.12.4rc1/ > >> >> > > >> >> > >> > https://pypi.org/project/apache-airflow-providers-cncf-kubernetes/10.8.2rc1/ > >> >> > https://pypi.org/project/apache-airflow-providers-edge3/1.3.1rc1/ > >> >> > https://pypi.org/project/apache-airflow-providers-fab/2.4.4rc1/ > >> >> > > >> >> > >> > https://pypi.org/project/apache-airflow-providers-microsoft-psrp/3.1.4rc1/ > >> >> > > >> https://pypi.org/project/apache-airflow-providers-openlineage/2.7.2rc1/ > >> >> > https://pypi.org/project/apache-airflow-providers-smtp/2.3.1rc1/ > >> >> > > https://pypi.org/project/apache-airflow-providers-standard/1.9.0rc1/ > >> >> > > >> >> > Cheers, > >> >> > Elad Kalif > >> >> > > >> >> > > --------------------------------------------------------------------- > >> >> > To unsubscribe, e-mail:[email protected] > >> >> > For additional commands, e-mail:[email protected] > >> >> > > >> > > >> > > >> > > >
