And for others checking KEYS - they are in the "release" part and should also be `svn updated` (after some back-forth with Jens ;) )
On Wed, Jun 4, 2025 at 10:16 PM Jens Scheffler <j_scheff...@gmx.de.invalid> wrote: > +1 (binding) - Checked SVN, Check in Docker, Reproducible package build, > Licenses, Signatures > > On 03.06.25 19:45, Jarek Potiuk wrote: > > BTW. I have new key added so PMC members might need to pull the KEYS from > > SVN to verify signatures > > > > > > On Tue, Jun 3, 2025 at 7:41 PM Jarek Potiuk <ja...@potiuk.com> 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 June 03, > >> 2025 05:40pm UTC and until 3 binding +1 votes have been received. > >> > >> Consider this my (binding) +1. > >> > >> This is an ad-hoc release of FAB provider 2.2.2 necessary to release > >> Airflow 3.0.2 > >> > >> 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/51378 > >> > >> 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-fab/2.2.0rc1/ > >> > >> Cheers, > >> J. > >> > >> > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@airflow.apache.org > For additional commands, e-mail: dev-h...@airflow.apache.org > >
