+1 non-binding.

Kind regards,
David

-----Original Message-----
From: Jarek Potiuk <ja...@potiuk.com>
Sent: Tuesday, 4 February 2025 23:03
To: dev@airflow.apache.org
Subject: [VOTE] Airflow Providers prepared on February 04, 2025

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 ab...@infrabel.be<mailto:ab...@infrabel.be>.

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 February 07,
2025 21:58 PM UTC and until 3 binding +1 votes have been received.

Consider this my (binding) +1.

This is a bugfix release of the fab provider.

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 packages.

*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_PROVIDER_PACKAGES.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_PROVIDER_PACKAGES.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/46442

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/1.5.3rc1/

Cheers,
J.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@airflow.apache.org
For additional commands, e-mail: dev-h...@airflow.apache.org

Reply via email to