+1 (binding), checked:

- SVN
- in Docker installation
- Reproducible package builds
- Licence
- Signature
- Checksums

Best regards,
Wei Lee



Jens Scheffler <[email protected]> 於 2026年5月7日週四 上午6:22寫道:

> +1 (binding) - Checked SVN, Check in Docker, Reproducible package build,
> Licenses, Signatures
>
> Did a usual test round with EdgeExecutor and Airflow 3.0.6, 3.1.8, 3.2.1
> and latest main via Integration test Dag - all looking good!
>
> On 06.05.26 17:16, Beck, Vincent wrote:
> > Hey all,
> >
> > I have just cut the new wave Airflow Providers packages with release
> preparation date 2026-05-05. This email is calling a vote on the release,
> > which will last for 72 hours - which means that it will end on
> 2026-05-09 15:23 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/2026-05-05
> >
> > *apache-airflow-providers-2026-05-05-source.tar.gz* is the full source
> tarball of airflow repo - snapshot taken at the moment of provider's
> release.
> >
> > *apache-airflow-providers-<PROVIDER>-*.tar.gz* are the convenience
> python "sdist" distributions that we publish in PyPI
> >
> > *apache_airflow_providers_<PROVIDER>-*.whl are the convenience Python
> "wheel" distributions that we publish in PyPI.
> >
> > 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 it.
> >
> > The status of testing the providers by the community is kept here:
> > https://github.com/apache/airflow/issues/66480
> >
> > 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-airbyte/5.4.2rc1/
> > https://pypi.org/project/apache-airflow-providers-amazon/9.28.0rc1/
> >
> https://pypi.org/project/apache-airflow-providers-cncf-kubernetes/10.17.0rc1/
> > https://pypi.org/project/apache-airflow-providers-common-ai/0.2.0rc1/
> > https://pypi.org/project/apache-airflow-providers-common-sql/1.36.0rc1/
> > https://pypi.org/project/apache-airflow-providers-databricks/7.14.0rc1/
> > https://pypi.org/project/apache-airflow-providers-dbt-cloud/4.8.2rc1/
> > https://pypi.org/project/apache-airflow-providers-discord/3.12.3rc1/
> > https://pypi.org/project/apache-airflow-providers-edge3/3.6.0rc1/
> > https://pypi.org/project/apache-airflow-providers-fab/3.6.3rc1/
> > https://pypi.org/project/apache-airflow-providers-git/0.3.2rc1/
> > https://pypi.org/project/apache-airflow-providers-google/21.3.0rc1/
> >
> https://pypi.org/project/apache-airflow-providers-microsoft-azure/13.2.0rc1/
> > https://pypi.org/project/apache-airflow-providers-mysql/6.5.3rc1/
> > https://pypi.org/project/apache-airflow-providers-openlineage/2.16.0rc1/
> > https://pypi.org/project/apache-airflow-providers-standard/1.13.0rc1/
> > https://pypi.org/project/apache-airflow-providers-yandex/4.5.0rc1/
> >
> > Cheers,
> > Vincent Beck
> >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
>
>

Reply via email to