Re: [VOTE] Airflow Providers prepared on April 10, 2025
+1 (binding) - checked reproducibility (edge provider is not reproducible but we are not releasing it yet), checksums,signatures, licences. Checked my code. Installed providers, on the 2.10.5 version of airflow (except fab/git/edge/common.messaging). Specifically I tested that the new 3.10.6 celery executor works with Airflow 2.10.5 On Sat, Apr 12, 2025 at 8:08 PM Vishnu Chilukoori wrote: > +1 (non-binding) > > Tested selected providers with example DAGs and verified expected behavior. > > > -- > > Regards, > > Vishnu Chilukoori > > On Sat, Apr 12, 2025 at 4:28 AM Amogh Desai > wrote: > > > +1 non binding > > > > Installed the bits and tested out some example dags and my changes to > work > > as expected. > > > > All good! > > > > Thanks & Regards, > > Amogh Desai > > > > > > On Sat, Apr 12, 2025 at 9:33 AM Elad Kalif wrote: > > > > > During release I manually mark edge as not ready so it won't create > docs > > > for it. The fact that we can't push it to PyPi doesnt mean we don't > test > > it > > > hence I pushed it to SVN. > > > > > > We vote only on the providers rc listed in this email > > > > > > בתאריך שבת, 12 באפר׳ 2025, 00:35, מאת Jens Scheffler > > > : > > > > > > > +1 (binding) - Checked SVN, Check in Docker, Reproducible package > > build, > > > > Licenses, Signatures (All except edge) > > > > > > > > Note: I was surprised that I found edge provider in the delivered > > > > package though I assume (again, but no explicit list given) that edge > > is > > > > not voted on. Reproducibility check with edge failed, the DIFF was > that > > > > the SVN package in provider.yaml was marked "not-ready" but in git is > > is > > > > marked "ready". > > > > > > > > Maybe it would be good if providers are released and VOTE is > requested > > > > to explicitly list which packages it is voted about. > > > > > > > > Thanks for makign it happen! Also FAB is now correct! And due to the > > > > exclusion of node_modules the package is much smaller. > > > > > > > > On 11.04.25 17:18, Vincent Beck wrote: > > > > > +1 non binding for apache-airflow-providers-amazon==9.6.0rc1. All > AWS > > > > system tests are passing against > > > apache-airflow-providers-amazon==9.6.0rc1. > > > > You can see the results here: > > > > > > > > > > https://aws-mwaa.github.io/#/open-source/system-tests/version/6bd535471819074f74b0c3a3251a823be24c61b0_9.6.0rc1.html > > > > . > > > > > > > > > > > > > > > > > > > > On 2025/04/10 14:49:17 Elad Kalif 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 > April > > > 13, > > > > >> 2025 14:45 PM 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/ > > > > >> > > > > >> *apache-airflow-providers--*.tar.gz* are the binary > > > > >> Python "sdist" release - they are also official "sources" for > the > > > > Provider > > > > >> distributions. > > > > >> > > > > >> *apache_airflow_providers_-*.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/49066 > > > > >> > > > > >> 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
Re: [VOTE] Airflow Providers prepared on April 10, 2025
+1 (non-binding) Tested selected providers with example DAGs and verified expected behavior. -- Regards, Vishnu Chilukoori On Sat, Apr 12, 2025 at 4:28 AM Amogh Desai wrote: > +1 non binding > > Installed the bits and tested out some example dags and my changes to work > as expected. > > All good! > > Thanks & Regards, > Amogh Desai > > > On Sat, Apr 12, 2025 at 9:33 AM Elad Kalif wrote: > > > During release I manually mark edge as not ready so it won't create docs > > for it. The fact that we can't push it to PyPi doesnt mean we don't test > it > > hence I pushed it to SVN. > > > > We vote only on the providers rc listed in this email > > > > בתאריך שבת, 12 באפר׳ 2025, 00:35, מאת Jens Scheffler > > : > > > > > +1 (binding) - Checked SVN, Check in Docker, Reproducible package > build, > > > Licenses, Signatures (All except edge) > > > > > > Note: I was surprised that I found edge provider in the delivered > > > package though I assume (again, but no explicit list given) that edge > is > > > not voted on. Reproducibility check with edge failed, the DIFF was that > > > the SVN package in provider.yaml was marked "not-ready" but in git is > is > > > marked "ready". > > > > > > Maybe it would be good if providers are released and VOTE is requested > > > to explicitly list which packages it is voted about. > > > > > > Thanks for makign it happen! Also FAB is now correct! And due to the > > > exclusion of node_modules the package is much smaller. > > > > > > On 11.04.25 17:18, Vincent Beck wrote: > > > > +1 non binding for apache-airflow-providers-amazon==9.6.0rc1. All AWS > > > system tests are passing against > > apache-airflow-providers-amazon==9.6.0rc1. > > > You can see the results here: > > > > > > https://aws-mwaa.github.io/#/open-source/system-tests/version/6bd535471819074f74b0c3a3251a823be24c61b0_9.6.0rc1.html > > > . > > > > > > > > > > > > > > > > On 2025/04/10 14:49:17 Elad Kalif 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 April > > 13, > > > >> 2025 14:45 PM 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/ > > > >> > > > >> *apache-airflow-providers--*.tar.gz* are the binary > > > >> Python "sdist" release - they are also official "sources" for the > > > Provider > > > >> distributions. > > > >> > > > >> *apache_airflow_providers_-*.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/49066 > > > >> > > > >> 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.6.0rc1/ > > > >> > > https://pypi.org/project/apache-airflow-providers-apache-hdfs/4.8.0rc1/ > > > >> > > https://pypi.org/project/apache-airflow-providers-apache-livy/4.3.1rc1/ > > > >> > > > > https://pypi.org/project/apache-airflow-providers-apache-spark/5.2.0rc1/ > > > >> https://pypi.org/project/apache-airflow-providers-celery/3.10.6rc1/ > > > >> > > > > > > https://pypi.org/project/apache-airflow-providers-cncf-kubernetes/10.4.2rc1/ > > > >> > https://pypi.org/project/apache-airflow-providers-common-io/1.5.3rc1/ > > > >> > > > > > > https://pypi.org/project/apache-airflow-providers-common-messagi
Re: [VOTE] Airflow Providers prepared on April 10, 2025
+1 non binding Installed the bits and tested out some example dags and my changes to work as expected. All good! Thanks & Regards, Amogh Desai On Sat, Apr 12, 2025 at 9:33 AM Elad Kalif wrote: > During release I manually mark edge as not ready so it won't create docs > for it. The fact that we can't push it to PyPi doesnt mean we don't test it > hence I pushed it to SVN. > > We vote only on the providers rc listed in this email > > בתאריך שבת, 12 באפר׳ 2025, 00:35, מאת Jens Scheffler > : > > > +1 (binding) - Checked SVN, Check in Docker, Reproducible package build, > > Licenses, Signatures (All except edge) > > > > Note: I was surprised that I found edge provider in the delivered > > package though I assume (again, but no explicit list given) that edge is > > not voted on. Reproducibility check with edge failed, the DIFF was that > > the SVN package in provider.yaml was marked "not-ready" but in git is is > > marked "ready". > > > > Maybe it would be good if providers are released and VOTE is requested > > to explicitly list which packages it is voted about. > > > > Thanks for makign it happen! Also FAB is now correct! And due to the > > exclusion of node_modules the package is much smaller. > > > > On 11.04.25 17:18, Vincent Beck wrote: > > > +1 non binding for apache-airflow-providers-amazon==9.6.0rc1. All AWS > > system tests are passing against > apache-airflow-providers-amazon==9.6.0rc1. > > You can see the results here: > > > https://aws-mwaa.github.io/#/open-source/system-tests/version/6bd535471819074f74b0c3a3251a823be24c61b0_9.6.0rc1.html > > . > > > > > > > > > > > > On 2025/04/10 14:49:17 Elad Kalif 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 April > 13, > > >> 2025 14:45 PM 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/ > > >> > > >> *apache-airflow-providers--*.tar.gz* are the binary > > >> Python "sdist" release - they are also official "sources" for the > > Provider > > >> distributions. > > >> > > >> *apache_airflow_providers_-*.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/49066 > > >> > > >> 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.6.0rc1/ > > >> > https://pypi.org/project/apache-airflow-providers-apache-hdfs/4.8.0rc1/ > > >> > https://pypi.org/project/apache-airflow-providers-apache-livy/4.3.1rc1/ > > >> > > https://pypi.org/project/apache-airflow-providers-apache-spark/5.2.0rc1/ > > >> https://pypi.org/project/apache-airflow-providers-celery/3.10.6rc1/ > > >> > > > https://pypi.org/project/apache-airflow-providers-cncf-kubernetes/10.4.2rc1/ > > >> https://pypi.org/project/apache-airflow-providers-common-io/1.5.3rc1/ > > >> > > > https://pypi.org/project/apache-airflow-providers-common-messaging/1.0.0rc2/ > > >> > https://pypi.org/project/apache-airflow-providers-databricks/7.3.1rc1/ > > >> https://pypi.org/project/apache-airflow-providers-discord/3.9.5rc1/ > > >> https://pypi.org/project/apache-airflow-providers-docker/4.3.1rc1/ > > >> https://pypi.org/project/apache-airflow-providers-fab/2.0.0rc4/ > > >> https://pypi.org/project/apache-airflow-providers-git/0.0.1rc1/ > > >> https://pypi.org/project/apache-airflow-providers-google/15.0.1rc1/ > >
Re: [VOTE] Airflow Providers prepared on April 10, 2025
During release I manually mark edge as not ready so it won't create docs for it. The fact that we can't push it to PyPi doesnt mean we don't test it hence I pushed it to SVN. We vote only on the providers rc listed in this email בתאריך שבת, 12 באפר׳ 2025, 00:35, מאת Jens Scheffler : > +1 (binding) - Checked SVN, Check in Docker, Reproducible package build, > Licenses, Signatures (All except edge) > > Note: I was surprised that I found edge provider in the delivered > package though I assume (again, but no explicit list given) that edge is > not voted on. Reproducibility check with edge failed, the DIFF was that > the SVN package in provider.yaml was marked "not-ready" but in git is is > marked "ready". > > Maybe it would be good if providers are released and VOTE is requested > to explicitly list which packages it is voted about. > > Thanks for makign it happen! Also FAB is now correct! And due to the > exclusion of node_modules the package is much smaller. > > On 11.04.25 17:18, Vincent Beck wrote: > > +1 non binding for apache-airflow-providers-amazon==9.6.0rc1. All AWS > system tests are passing against apache-airflow-providers-amazon==9.6.0rc1. > You can see the results here: > https://aws-mwaa.github.io/#/open-source/system-tests/version/6bd535471819074f74b0c3a3251a823be24c61b0_9.6.0rc1.html > . > > > > > > > > On 2025/04/10 14:49:17 Elad Kalif 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 April 13, > >> 2025 14:45 PM 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/ > >> > >> *apache-airflow-providers--*.tar.gz* are the binary > >> Python "sdist" release - they are also official "sources" for the > Provider > >> distributions. > >> > >> *apache_airflow_providers_-*.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/49066 > >> > >> 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.6.0rc1/ > >> https://pypi.org/project/apache-airflow-providers-apache-hdfs/4.8.0rc1/ > >> https://pypi.org/project/apache-airflow-providers-apache-livy/4.3.1rc1/ > >> > https://pypi.org/project/apache-airflow-providers-apache-spark/5.2.0rc1/ > >> https://pypi.org/project/apache-airflow-providers-celery/3.10.6rc1/ > >> > https://pypi.org/project/apache-airflow-providers-cncf-kubernetes/10.4.2rc1/ > >> https://pypi.org/project/apache-airflow-providers-common-io/1.5.3rc1/ > >> > https://pypi.org/project/apache-airflow-providers-common-messaging/1.0.0rc2/ > >> https://pypi.org/project/apache-airflow-providers-databricks/7.3.1rc1/ > >> https://pypi.org/project/apache-airflow-providers-discord/3.9.5rc1/ > >> https://pypi.org/project/apache-airflow-providers-docker/4.3.1rc1/ > >> https://pypi.org/project/apache-airflow-providers-fab/2.0.0rc4/ > >> https://pypi.org/project/apache-airflow-providers-git/0.0.1rc1/ > >> https://pypi.org/project/apache-airflow-providers-google/15.0.1rc1/ > >> https://pypi.org/project/apache-airflow-providers-mysql/6.2.1rc1/ > >> https://pypi.org/project/apache-airflow-providers-openlineage/2.1.3rc1/ > >> https://pypi.org/project/apache-airflow-providers-sftp/5.2.0rc1/ > >> https://pypi.org/project/apache-airflow-providers-slack/9.0.4rc1/ > >> https://pypi.org/project/apache-airflow-providers-snowflake/6.2.1rc1/ > >> https://pypi.org/project/apache-airflow-providers-sqlite/4.0.2rc1/ > >> htt
Re: [VOTE] Airflow Providers prepared on April 10, 2025
+1 (binding) - Checked SVN, Check in Docker, Reproducible package build, Licenses, Signatures (All except edge) Note: I was surprised that I found edge provider in the delivered package though I assume (again, but no explicit list given) that edge is not voted on. Reproducibility check with edge failed, the DIFF was that the SVN package in provider.yaml was marked "not-ready" but in git is is marked "ready". Maybe it would be good if providers are released and VOTE is requested to explicitly list which packages it is voted about. Thanks for makign it happen! Also FAB is now correct! And due to the exclusion of node_modules the package is much smaller. On 11.04.25 17:18, Vincent Beck wrote: +1 non binding for apache-airflow-providers-amazon==9.6.0rc1. All AWS system tests are passing against apache-airflow-providers-amazon==9.6.0rc1. You can see the results here: https://aws-mwaa.github.io/#/open-source/system-tests/version/6bd535471819074f74b0c3a3251a823be24c61b0_9.6.0rc1.html. On 2025/04/10 14:49:17 Elad Kalif 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 April 13, 2025 14:45 PM 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/ *apache-airflow-providers--*.tar.gz* are the binary Python "sdist" release - they are also official "sources" for the Provider distributions. *apache_airflow_providers_-*.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/49066 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.6.0rc1/ https://pypi.org/project/apache-airflow-providers-apache-hdfs/4.8.0rc1/ https://pypi.org/project/apache-airflow-providers-apache-livy/4.3.1rc1/ https://pypi.org/project/apache-airflow-providers-apache-spark/5.2.0rc1/ https://pypi.org/project/apache-airflow-providers-celery/3.10.6rc1/ https://pypi.org/project/apache-airflow-providers-cncf-kubernetes/10.4.2rc1/ https://pypi.org/project/apache-airflow-providers-common-io/1.5.3rc1/ https://pypi.org/project/apache-airflow-providers-common-messaging/1.0.0rc2/ https://pypi.org/project/apache-airflow-providers-databricks/7.3.1rc1/ https://pypi.org/project/apache-airflow-providers-discord/3.9.5rc1/ https://pypi.org/project/apache-airflow-providers-docker/4.3.1rc1/ https://pypi.org/project/apache-airflow-providers-fab/2.0.0rc4/ https://pypi.org/project/apache-airflow-providers-git/0.0.1rc1/ https://pypi.org/project/apache-airflow-providers-google/15.0.1rc1/ https://pypi.org/project/apache-airflow-providers-mysql/6.2.1rc1/ https://pypi.org/project/apache-airflow-providers-openlineage/2.1.3rc1/ https://pypi.org/project/apache-airflow-providers-sftp/5.2.0rc1/ https://pypi.org/project/apache-airflow-providers-slack/9.0.4rc1/ https://pypi.org/project/apache-airflow-providers-snowflake/6.2.1rc1/ https://pypi.org/project/apache-airflow-providers-sqlite/4.0.2rc1/ https://pypi.org/project/apache-airflow-providers-standard/0.4.0rc1/ Cheers, Elad Kalif - 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]
Re: [VOTE] Airflow Providers prepared on April 10, 2025
+1 non binding for apache-airflow-providers-amazon==9.6.0rc1. All AWS system tests are passing against apache-airflow-providers-amazon==9.6.0rc1. You can see the results here: https://aws-mwaa.github.io/#/open-source/system-tests/version/6bd535471819074f74b0c3a3251a823be24c61b0_9.6.0rc1.html. On 2025/04/10 14:49:17 Elad Kalif 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 April 13, > 2025 14:45 PM 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/ > > *apache-airflow-providers--*.tar.gz* are the binary > Python "sdist" release - they are also official "sources" for the Provider > distributions. > > *apache_airflow_providers_-*.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/49066 > > 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.6.0rc1/ > https://pypi.org/project/apache-airflow-providers-apache-hdfs/4.8.0rc1/ > https://pypi.org/project/apache-airflow-providers-apache-livy/4.3.1rc1/ > https://pypi.org/project/apache-airflow-providers-apache-spark/5.2.0rc1/ > https://pypi.org/project/apache-airflow-providers-celery/3.10.6rc1/ > https://pypi.org/project/apache-airflow-providers-cncf-kubernetes/10.4.2rc1/ > https://pypi.org/project/apache-airflow-providers-common-io/1.5.3rc1/ > https://pypi.org/project/apache-airflow-providers-common-messaging/1.0.0rc2/ > https://pypi.org/project/apache-airflow-providers-databricks/7.3.1rc1/ > https://pypi.org/project/apache-airflow-providers-discord/3.9.5rc1/ > https://pypi.org/project/apache-airflow-providers-docker/4.3.1rc1/ > https://pypi.org/project/apache-airflow-providers-fab/2.0.0rc4/ > https://pypi.org/project/apache-airflow-providers-git/0.0.1rc1/ > https://pypi.org/project/apache-airflow-providers-google/15.0.1rc1/ > https://pypi.org/project/apache-airflow-providers-mysql/6.2.1rc1/ > https://pypi.org/project/apache-airflow-providers-openlineage/2.1.3rc1/ > https://pypi.org/project/apache-airflow-providers-sftp/5.2.0rc1/ > https://pypi.org/project/apache-airflow-providers-slack/9.0.4rc1/ > https://pypi.org/project/apache-airflow-providers-snowflake/6.2.1rc1/ > https://pypi.org/project/apache-airflow-providers-sqlite/4.0.2rc1/ > https://pypi.org/project/apache-airflow-providers-standard/0.4.0rc1/ > > > Cheers, > Elad Kalif > - To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
