+1 (binding). I have checked, - SVN - in Docker installation - Reproducible package builds - Licence - Signature - Checksums
Pure PMC checks. Kind regards, Bugra Ozturk Op ma 13 apr 2026, 21:48 schreef Pavankumar Gopidesu < [email protected]>: > Verified common.ai LGTM all working as expected. Thanks Jarek :) > > > Regards, > Pavan > > On Mon, Apr 13, 2026 at 8:14 PM Jens Scheffler <[email protected]> > wrote: > > > +1 (binding) - Checked SVN, Check in Docker, Reproducible package build, > > Licenses, Signatures > > > > Had nothing to test against, so the vote is the "pure" PMC validation. > > > > On 13.04.26 20:25, Vincent Beck wrote: > > > +1 binding. Checked: > > > > > > * SVN > > > * Reproducible package builds > > > * Licence > > > * Signature > > > * SHA512 > > > > > > On 2026/04/12 22:34:11 Jarek Potiuk wrote: > > >> Hey all, > > >> > > >> I have just cut the new wave Airflow Providers packages with release > > >> preparation date 2026-04-12. This email is calling a vote on the > > release, > > >> which will last for 24 hours - which means that it will end on > > 2026-04-13 > > >> 22:41 UTC and until 3 binding +1 votes have been received. > > >> This is a shortened (24 hours vote) as agreed by policy set it > > >> https://lists.apache.org/thread/cv194w1fqqykrhswhmm54zy9gnnv6kgm > > >> > > >> Consider this my (binding) +1. > > >> > > >> Those are the rc2s of the common.compat and common.ai - derived > > providers > > >> re-released due to compatibility bugs found in rc1. > > >> > > >> Airflow Providers are available at: > > >> https://dist.apache.org/repos/dist/dev/airflow/providers/2026-04-12 > > >> > > >> *apache-airflow-providers-2026-04-12-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/65110 > > >> > > >> 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.25.0rc2/ > > >> https://pypi.org/project/apache-airflow-providers-common-ai/0.1.0rc2/ > > >> > > > https://pypi.org/project/apache-airflow-providers-common-compat/1.14.3rc2/ > > >> > > https://pypi.org/project/apache-airflow-providers-openlineage/2.14.0rc2/ > > >> > > >> > > >> Cheers, > > >> Jarek Potiuk > > >> > > > --------------------------------------------------------------------- > > > To unsubscribe, e-mail: [email protected] > > > For additional commands, e-mail: [email protected] > > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [email protected] > > For additional commands, e-mail: [email protected] > > > > >
