Kind request - to all PMC members - as I saw it a few times already). Can
we please state what kind of verification we have done with the release and
add (binding) ?

At the last few board meetings of ASF I attended - there were comments
about a number of projects where PMC votes did not have information
about the provenance / verification checks done by the person who gives +1.
Those kinds of statements are not really good for the Foundation records -
and there were even suggestions that just +1 without explaining what
exactly has been done should not be counted.

And just to explain - we are not doing it as a "cargo cult" or
anything like that - PMC votes on releases are a legal act of foundations
and records of it (this email thread) are kept to verify in case foundation
has been challenged and any kind of lawsuits could have happened. That's
why PMC members have to state the kind of checks they've done with a
release.

In the near future when we have ATR (Apache Trusted Releases) - it will be
simpler as those will be merely check-boxes to check and many of those
checks will be easier and more automated, but for one the approach of the
board was that such +1s are not valuable for the Foundation legal records.

J.


On Wed, Jul 30, 2025 at 1:04 PM Ash Berlin-Taylor <a...@apache.org> wrote:

> Okay I’ve tested, Cloudwatch logs make it to Cloudwatch and come back
> (comparing 9.10.0 and 9.11.0rc1), there is just a “display” bug
> https://github.com/apache/airflow/issues/53873#issuecomment-3135817385 —
> so I change my vote for that -0.5 on releasing Amazon provider right now.
> Hopefully Jason is looking in to a fix of it?
>
> +1 for everything else.
>
> -ash
>
> > On 29 Jul 2025, at 21:33, Ash Berlin-Taylor <a...@apache.org> wrote:
> >
> > I have a feeling there is a regression in the Cloudwatch log handling in
> this. I will test tomorrow, but right now -1 on releasing Amazon provider
> in the mean time.
> >
> >> On 29 Jul 2025, at 20:29, Jens Scheffler <j_scheff...@gmx.de.INVALID>
> wrote:
> >>
> >> +1 (binding) - Checked SVN, Check in Docker, Reproducible package
> build, Licenses, Signatures
> >>
> >> Tested Edge3 Package 1.1.2rc1 with Airflow 2.11.0 and 3.0.3 and all
> seems to be good after execution of the integration_test Dag.
> >>
> >> On 29.07.25 12:57, 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 August 01, 2025 10:55 AM 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-<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/53873
> >>>
> >>> 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-airbyte/5.2.2rc1/
> >>> https://pypi.org/project/apache-airflow-providers-alibaba/3.2.2rc1/
> >>> https://pypi.org/project/apache-airflow-providers-amazon/9.11.0rc1/
> >>>
> https://pypi.org/project/apache-airflow-providers-apache-beam/6.1.3rc1/
> >>>
> https://pypi.org/project/apache-airflow-providers-apache-cassandra/3.8.2rc1/
> >>>
> https://pypi.org/project/apache-airflow-providers-apache-drill/3.1.2rc1/
> >>>
> https://pypi.org/project/apache-airflow-providers-apache-druid/4.3.0rc1/
> >>>
> https://pypi.org/project/apache-airflow-providers-apache-flink/1.7.2rc1/
> >>>
> https://pypi.org/project/apache-airflow-providers-apache-hdfs/4.10.2rc1/
> >>>
> https://pypi.org/project/apache-airflow-providers-apache-hive/9.1.2rc1/
> >>>
> https://pypi.org/project/apache-airflow-providers-apache-iceberg/1.3.2rc1/
> >>>
> https://pypi.org/project/apache-airflow-providers-apache-impala/1.7.2rc1/
> >>>
> https://pypi.org/project/apache-airflow-providers-apache-kafka/1.10.1rc1/
> >>>
> https://pypi.org/project/apache-airflow-providers-apache-kylin/3.9.2rc1/
> >>>
> https://pypi.org/project/apache-airflow-providers-apache-livy/4.4.2rc1/
> >>> https://pypi.org/project/apache-airflow-providers-apache-pig/4.7.2rc1/
> >>>
> https://pypi.org/project/apache-airflow-providers-apache-pinot/4.8.2rc1/
> >>>
> https://pypi.org/project/apache-airflow-providers-apache-spark/5.3.2rc1/
> >>>
> https://pypi.org/project/apache-airflow-providers-apache-tinkerpop/1.0.2rc1/
> >>> https://pypi.org/project/apache-airflow-providers-apprise/2.1.2rc1/
> >>> https://pypi.org/project/apache-airflow-providers-arangodb/2.8.2rc1/
> >>> https://pypi.org/project/apache-airflow-providers-asana/2.10.2rc1/
> >>>
> https://pypi.org/project/apache-airflow-providers-atlassian-jira/3.1.2rc1/
> >>> https://pypi.org/project/apache-airflow-providers-celery/3.12.2rc1/
> >>> https://pypi.org/project/apache-airflow-providers-cloudant/4.2.2rc1/
> >>>
> https://pypi.org/project/apache-airflow-providers-cncf-kubernetes/10.6.2rc1/
> >>> https://pypi.org/project/apache-airflow-providers-cohere/1.5.3rc1/
> >>>
> https://pypi.org/project/apache-airflow-providers-common-compat/1.7.3rc1/
> >>> https://pypi.org/project/apache-airflow-providers-common-io/1.6.2rc1/
> >>>
> https://pypi.org/project/apache-airflow-providers-common-messaging/1.0.5rc1/
> >>>
> https://pypi.org/project/apache-airflow-providers-common-sql/1.27.4rc1/
> >>> https://pypi.org/project/apache-airflow-providers-databricks/7.7.0rc1/
> >>> https://pypi.org/project/apache-airflow-providers-datadog/3.9.2rc1/
> >>> https://pypi.org/project/apache-airflow-providers-dbt-cloud/4.4.2rc1/
> >>> https://pypi.org/project/apache-airflow-providers-dingding/3.8.2rc1/
> >>> https://pypi.org/project/apache-airflow-providers-discord/3.10.2rc1/
> >>> https://pypi.org/project/apache-airflow-providers-docker/4.4.2rc1/
> >>> https://pypi.org/project/apache-airflow-providers-edge3/1.1.2rc2/
> >>>
> https://pypi.org/project/apache-airflow-providers-elasticsearch/6.3.2rc1/
> >>> https://pypi.org/project/apache-airflow-providers-exasol/4.8.2rc1/
> >>> https://pypi.org/project/apache-airflow-providers-fab/2.3.1rc1/
> >>> https://pypi.org/project/apache-airflow-providers-facebook/3.8.2rc1/
> >>> https://pypi.org/project/apache-airflow-providers-ftp/3.13.2rc1/
> >>> https://pypi.org/project/apache-airflow-providers-git/0.0.5rc1/
> >>> https://pypi.org/project/apache-airflow-providers-github/2.9.2rc1/
> >>> https://pypi.org/project/apache-airflow-providers-google/17.0.0rc1/
> >>> https://pypi.org/project/apache-airflow-providers-grpc/3.8.2rc1/
> >>> https://pypi.org/project/apache-airflow-providers-hashicorp/4.3.2rc1/
> >>> https://pypi.org/project/apache-airflow-providers-http/5.3.3rc1/
> >>> https://pypi.org/project/apache-airflow-providers-imap/3.9.2rc1/
> >>> https://pypi.org/project/apache-airflow-providers-influxdb/2.9.3rc1/
> >>> https://pypi.org/project/apache-airflow-providers-jdbc/5.2.2rc1/
> >>> https://pypi.org/project/apache-airflow-providers-jenkins/4.1.2rc1/
> >>>
> https://pypi.org/project/apache-airflow-providers-microsoft-azure/12.6.0rc1/
> >>>
> https://pypi.org/project/apache-airflow-providers-microsoft-mssql/4.3.2rc1/
> >>>
> https://pypi.org/project/apache-airflow-providers-microsoft-psrp/3.1.2rc1/
> >>>
> https://pypi.org/project/apache-airflow-providers-microsoft-winrm/3.10.2rc1/
> >>> https://pypi.org/project/apache-airflow-providers-mongo/5.2.2rc1/
> >>> https://pypi.org/project/apache-airflow-providers-mysql/6.3.3rc1/
> >>> https://pypi.org/project/apache-airflow-providers-neo4j/3.10.0rc1/
> >>> https://pypi.org/project/apache-airflow-providers-odbc/4.10.2rc1/
> >>> https://pypi.org/project/apache-airflow-providers-openai/1.6.2rc1/
> >>> https://pypi.org/project/apache-airflow-providers-openfaas/3.8.2rc1/
> >>>
> https://pypi.org/project/apache-airflow-providers-openlineage/2.6.0rc1/
> >>> https://pypi.org/project/apache-airflow-providers-opensearch/1.7.2rc1/
> >>> https://pypi.org/project/apache-airflow-providers-opsgenie/5.9.2rc1/
> >>> https://pypi.org/project/apache-airflow-providers-oracle/4.1.3rc1/
> >>> https://pypi.org/project/apache-airflow-providers-pagerduty/5.0.2rc1/
> >>> https://pypi.org/project/apache-airflow-providers-papermill/3.11.2rc1/
> >>> https://pypi.org/project/apache-airflow-providers-pgvector/1.5.2rc1/
> >>> https://pypi.org/project/apache-airflow-providers-pinecone/2.3.3rc1/
> >>> https://pypi.org/project/apache-airflow-providers-postgres/6.2.2rc1/
> >>> https://pypi.org/project/apache-airflow-providers-presto/5.9.2rc1/
> >>> https://pypi.org/project/apache-airflow-providers-qdrant/1.4.2rc1/
> >>> https://pypi.org/project/apache-airflow-providers-redis/4.2.0rc1/
> >>>
> https://pypi.org/project/apache-airflow-providers-salesforce/5.11.2rc1/
> >>> https://pypi.org/project/apache-airflow-providers-samba/4.10.2rc1/
> >>> https://pypi.org/project/apache-airflow-providers-segment/3.8.2rc1/
> >>> https://pypi.org/project/apache-airflow-providers-sendgrid/4.1.3rc1/
> >>> https://pypi.org/project/apache-airflow-providers-sftp/5.3.3rc1/
> >>>
> https://pypi.org/project/apache-airflow-providers-singularity/3.8.2rc1/
> >>> https://pypi.org/project/apache-airflow-providers-slack/9.1.3rc1/
> >>> https://pypi.org/project/apache-airflow-providers-smtp/2.1.2rc1/
> >>> https://pypi.org/project/apache-airflow-providers-snowflake/6.5.1rc1/
> >>> https://pypi.org/project/apache-airflow-providers-sqlite/4.1.2rc1/
> >>> https://pypi.org/project/apache-airflow-providers-ssh/4.1.2rc1/
> >>> https://pypi.org/project/apache-airflow-providers-standard/1.5.0rc1/
> >>> https://pypi.org/project/apache-airflow-providers-tableau/5.2.0rc1/
> >>> https://pypi.org/project/apache-airflow-providers-telegram/4.8.2rc1/
> >>> https://pypi.org/project/apache-airflow-providers-teradata/3.2.1rc1/
> >>> https://pypi.org/project/apache-airflow-providers-trino/6.3.2rc1/
> >>> https://pypi.org/project/apache-airflow-providers-vertica/4.1.2rc1/
> >>> https://pypi.org/project/apache-airflow-providers-weaviate/3.2.2rc1/
> >>> https://pypi.org/project/apache-airflow-providers-yandex/4.2.0rc1/
> >>> https://pypi.org/project/apache-airflow-providers-ydb/2.2.2rc1/
> >>> https://pypi.org/project/apache-airflow-providers-zendesk/4.10.2rc1/
> >>>
> >>> Cheers,
> >>> Elad Kalif
> >>>
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: dev-unsubscr...@airflow.apache.org
> >> For additional commands, e-mail: dev-h...@airflow.apache.org
> >>
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscr...@airflow.apache.org
> > For additional commands, e-mail: dev-h...@airflow.apache.org
> >
>
>

Reply via email to