+1 binding.

- Checked SVN
- Checked in Docker
- Checked reproducible package builds
- Checked licenses
- Checked signatures

Only performed the PMC checks on this one because I do not use both those
providers.

Thanks & Regards,
Amogh Desai


On Wed, Nov 19, 2025 at 12:07 AM Jens Scheffler <[email protected]> wrote:

> +1 (binding) - Checked SVN, Check in Docker, Reproducible package build,
> Licenses, Signatures
>
> Note, do not have any target to check against (Slack or Apprise) so this
> is just a technical PMC package check.
>
> On 11/18/25 00:30, Jarek Potiuk wrote:
> > Hey all,
> >
> > I have just cut the new wave Airflow Providers packages with release
> > preparation date 2025-11-18. This email is calling a vote on the
> > release,
> > which will last for 24 hours - which means that it will end on
> > November 18, 2025 23:23 PM UTC and until 3 binding +1 votes have been
> > received.
> > This is a shortened (24 hours vote) as agreed by policy set it
> > https://lists.apache.org/thread/cv194w1fqqykrhswhmm54zy9gnnv6kgm
> >
> > Consider this my (binding) +1.
> >
> > Those are just `apprise` and `slack` providers with updated
> > dependencies to common.compat provider >= 1.9.0
> >
> > Airflow Providers are available at:
> > https://dist.apache.org/repos/dist/dev/airflow/providers/2025-11-18
> >
> > *apache-airflow-providers-2025-11-18-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/58414
> >
> > 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-apprise/2.2.0rc2/
> > https://pypi.org/project/apache-airflow-providers-slack/9.5.0rc2/
> >
> > The docs (due to prolonged DDos Attack our issue is still not handled):
> >
> > *
> https://d3a2du7x0n8ydr.cloudfront.net/docs/apache-airflow-providers-apprise/2.2.0
> > *
> https://d3a2du7x0n8ydr.cloudfront.net/docs/apache-airflow-providers-slack/9.5.0
> >
> > Cheers,
> > Jarek Potiuk
> >
> > ---------------------------------------------------------------------
> > 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]
>
>

Reply via email to