+1 binding. - Checked SVN - Checked in Docker - Checked reproducible package builds - Checked licenses - Checked signatures
Didn't have any changes, so my tests are limited to the PMC checks. Thanks & Regards, Amogh Desai On Fri, Oct 3, 2025 at 1:31 AM Elad Kalif <[email protected]> wrote: > fab provider is excluded due to a bug found. it will have rc2. > vote continues for Amazon provider > > On Thu, Oct 2, 2025 at 4:06 PM Elad Kalif <[email protected]> wrote: > > > > Is it possible to include Edge3 and celery aswell as a part of this > > release? > > > > No. it will have to wait for the next wave. > > > > On Thu, Oct 2, 2025 at 1:14 AM Jens Scheffler <[email protected]> > wrote: > > > >> +1 (binding) - Checked SVN, Check in Docker, Reproducible package build, > >> Licenses, Signatures > >> > >> Tested providers (but lagging Amazon subscription so mainly Fab). Tested > >> with Airflow 3.0.6, 3.1.0 and latest main (LocalExecutor and > >> EdgeExecutor) with Integration Test, via a seondary created user. All > >> looks good. Tests executed via breeze. > >> > >> Note I saw a lot of messages like "2025-10-01T21:50:39.218718Z [warning > >> ] appbuilder.app is deprecated and will be removed in a future version. > >> Use current_app instead [flask_appbuilder.base] > >> loc=init_appbuilder.py:228" in the console while starting, I assume some > >> deprecations need to be cleaned? Non blocking to release in my view. > >> > >> On 01.10.25 11:07, 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 on October 04, 2025 09:05 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/56284 > >> > > >> > 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-amazon/9.15.0rc1/ > >> > https://pypi.org/project/apache-airflow-providers-fab/3.0.0rc1/ > >> > > >> > Cheers, > >> > Elad Kalif > >> > > >> > >> --------------------------------------------------------------------- > >> To unsubscribe, e-mail: [email protected] > >> For additional commands, e-mail: [email protected] > >> > >> >
