> Isn't this a follow-up release, meaning the voting period should only be 24 hours?
Normally yes but Jarek added Clickhouse which was not part of rc1 so it has to be 72 hours. On Mon, Jun 8, 2026 at 8:15 PM Niko Oliveira <[email protected]> wrote: > Thanks for the follow up release Jarek! > > > which will last for 72 hours - which means that it will end on 2026-06-11 > 15:45 UTC and until 3 binding +1 votes have been received. > > Isn't this a follow-up release, meaning the voting period should only be 24 > hours? > > I will work on testing today. > > Cheers, > Niko > > On Mon, Jun 8, 2026 at 10:11 AM Shahar Epstein <[email protected]> wrote: > > > +1 (binding), checked: > > > > - SVN > > - Checksums > > - Signatures > > - Licenses > > - Reproducible build > > > > > > Shahar > > > > On Mon, Jun 8, 2026 at 6:45 PM Jarek Potiuk <[email protected]> wrote: > > > > > Hey all, > > > > > > I have just cut the new wave Airflow Providers packages with release > > > preparation date 2026-06-08. This email is calling a vote on the > > > release, which will last for 72 hours - which means that it will end > > > on 2026-06-11 15:45 UTC and until 3 binding +1 votes have been > > > received. > > > > > > Consider this my (binding) +1. > > > > > > This is a follow-up to the 2026-06-02 wave. It releases the four > > > providers that were held back from that wave - amazon (9.30.0), > > > cncf.kubernetes (10.18.0), edge3 (3.8.0) and apache.spark (6.1.0), now > > > re-cut as rc2 with the fixes they were waiting for - plus the > > > brand-new ClickHouse provider (clickhousedb 1.0.0, rc1). > > > > > > Airflow Providers are available at: > > > https://dist.apache.org/repos/dist/dev/airflow/providers/2026-06-08 > > > > > > *apache-airflow-providers-2026-06-08-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/68225 > > > > > > 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.30.0rc2/ > > > > https://pypi.org/project/apache-airflow-providers-apache-spark/6.1.0rc2/ > > > > https://pypi.org/project/apache-airflow-providers-clickhousedb/1.0.0rc1/ > > > > > > > > > https://pypi.org/project/apache-airflow-providers-cncf-kubernetes/10.18.0rc2/ > > > https://pypi.org/project/apache-airflow-providers-edge3/3.8.0rc2/ > > > > > > Cheers, > > > Jarek Potiuk > > > > > > --------------------------------------------------------------------- > > > To unsubscribe, e-mail: [email protected] > > > For additional commands, e-mail: [email protected] > > > > > > > > >
