1. I'd rather wait for the next wave, as I cannot release IBM in
accelerated mode (it didn't exist in the last wave).
2. In release votes only PMC's votes are binding :)


Shahar

On Fri, Oct 2, 2026 at 11:08 PM Blain David <[email protected]> wrote:

> +1 approve (binding)
>
> How about the ibm ones that are ready now?
>
> General (Internal Property)
> ________________________________
> From: Shahar Epstein <[email protected]>
> Sent: Friday, October 2, 2026 20:25
> To: [email protected] <[email protected]>
> Subject: [ACCELERATED VOTE] Airflow Providers, release preparation date
> 2026-10-02 (ad-hoc)
>
> EXTERNAL MAIL: Indien je de afzender van deze e-mail niet kent en deze
> niet vertrouwt, klik niet op een link of open geen bijlages. Bij twijfel,
> stuur deze e-mail als bijlage naar [email protected]<mailto:
> [email protected]>.
>
> Hey all,
>
> I have just cut the new wave Airflow Providers packages with release
> preparation date 2026-10-02. This email is calling a vote on the release,
> which will last for 24 hours - which means that it will end on 2026-10-03
> 18:25 UTC and until 3 binding +1 votes have been received.
> This is a shortened (24 hours vote) as agreed by policy set it
>
> https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.apache.org%2Fthread%2Fcv194w1fqqykrhswhmm54zy9gnnv6kgm&data=05%7C02%7Cdavid.blain%40infrabel.be%7C5afe7507872a4a3c569a08df20b29827%7Cb82bc314ab8e4d6fb18946f02e1f27f2%7C0%7C0%7C639265623568931956%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=OrV9%2BrMRDoDOTgAvS4Z8k1h62%2B8e0HHZfiZSBZEk%2FH0%3D&reserved=0
> <https://lists.apache.org/thread/cv194w1fqqykrhswhmm54zy9gnnv6kgm>
>
> Consider this my (binding) +1.
>
> This is an ad-hoc release for the following providers:
> - cncf.kubernetes - excluded from last wave due to a regression, fixed in
> rc2
> - edge3 - excluded from last wave due to a regression, fixed in rc2
> - duckdb - excluded from last wave due to a a technical issue releasing as
> v0.1.0 in PyPi. The initial version as part of the official releases would
> be v0.2.0, once an RC is approved.
>
>
> Airflow Providers are available at:
>
> https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdist.apache.org%2Frepos%2Fdist%2Fdev%2Fairflow%2Fproviders%2F2026-10-02&data=05%7C02%7Cdavid.blain%40infrabel.be%7C5afe7507872a4a3c569a08df20b29827%7Cb82bc314ab8e4d6fb18946f02e1f27f2%7C0%7C0%7C639265623568953047%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=WfdZrVvGaMiIJcqVwArFInzlHAzL4oGk9xQYy83LxjA%3D&reserved=0
> <https://dist.apache.org/repos/dist/dev/airflow/providers/2026-10-02>
>
> *apache-airflow-providers-2026-10-02-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://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Fairflow%2Fblob%2Fmain%2Fdev%2FREADME_RELEASE_PROVIDERS.md%23verify-the-release-candidate-by-pmc-members&data=05%7C02%7Cdavid.blain%40infrabel.be%7C5afe7507872a4a3c569a08df20b29827%7Cb82bc314ab8e4d6fb18946f02e1f27f2%7C0%7C0%7C639265623568967358%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=PQTdWhpUt1GvJsvJveUFcAO84cGu0KSBY11LqLFYfcI%3D&reserved=0
> <
> 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://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Fairflow%2Fblob%2Fmain%2Fdev%2FREADME_RELEASE_PROVIDERS.md%23verify-the-release-candidate-by-contributors&data=05%7C02%7Cdavid.blain%40infrabel.be%7C5afe7507872a4a3c569a08df20b29827%7Cb82bc314ab8e4d6fb18946f02e1f27f2%7C0%7C0%7C639265623568981805%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=7ZaGcUR%2F2NAcCAaj6JRSgSGszRFY0Lz3fF07opuiSCM%3D&reserved=0
> <
> https://github.com/apache/airflow/blob/main/dev/README_RELEASE_PROVIDERS.md#verify-the-release-candidate-by-contributors
> >
>
>
> Public keys are available at:
>
> https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdist.apache.org%2Frepos%2Fdist%2Frelease%2Fairflow%2FKEYS&data=05%7C02%7Cdavid.blain%40infrabel.be%7C5afe7507872a4a3c569a08df20b29827%7Cb82bc314ab8e4d6fb18946f02e1f27f2%7C0%7C0%7C639265623568997897%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=oFh7ldI9THpwNeNd0HRODuYoTAfcWmBAJkE9WQDP78Q%3D&reserved=0
> <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://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Fairflow%2Fissues%2F74118&data=05%7C02%7Cdavid.blain%40infrabel.be%7C5afe7507872a4a3c569a08df20b29827%7Cb82bc314ab8e4d6fb18946f02e1f27f2%7C0%7C0%7C639265623569014054%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=0hvNZLUKy%2BVqdM7d1RKjsa4BJInNxkKb16zeVZh5G80%3D&reserved=0
> <https://github.com/apache/airflow/issues/74118>
>
> 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://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpypi.org%2Fproject%2Fapache-airflow-providers-cncf-kubernetes%2F10.23.0rc2%2F&data=05%7C02%7Cdavid.blain%40infrabel.be%7C5afe7507872a4a3c569a08df20b29827%7Cb82bc314ab8e4d6fb18946f02e1f27f2%7C0%7C0%7C639265623569031669%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=M0DAZLDiWYkwFLlMyrvar99rsk2dYkI0kIuESnPU0EA%3D&reserved=0
> <
> https://pypi.org/project/apache-airflow-providers-cncf-kubernetes/10.23.0rc2/
> >
>
> https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpypi.org%2Fproject%2Fapache-airflow-providers-duckdb%2F0.2.0rc1%2F&data=05%7C02%7Cdavid.blain%40infrabel.be%7C5afe7507872a4a3c569a08df20b29827%7Cb82bc314ab8e4d6fb18946f02e1f27f2%7C0%7C0%7C639265623569046384%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=Y29EPVWLB6uO4M7NsEWmHN8tvGQP23%2BhHAz%2FCs3psYw%3D&reserved=0
> <https://pypi.org/project/apache-airflow-providers-duckdb/0.2.0rc1/>
>
> https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpypi.org%2Fproject%2Fapache-airflow-providers-edge3%2F5.0.0rc2%2F&data=05%7C02%7Cdavid.blain%40infrabel.be%7C5afe7507872a4a3c569a08df20b29827%7Cb82bc314ab8e4d6fb18946f02e1f27f2%7C0%7C0%7C639265623569060367%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=Tk073YvC%2FNI7a31xVseUyKzXI226TLLV3OtniTqNPzo%3D&reserved=0
> <https://pypi.org/project/apache-airflow-providers-edge3/5.0.0rc2/>
>
>
> Sincerely,
>
>
> Shahar Epstein
>

Reply via email to