+1 (binding), Checked SVN, Docker, reproducibility, licence, signature,
checksums -> all good.

On Wed, Jul 9, 2025 at 1:42 PM Ankit Chaurasia <sunank...@gmail.com> wrote:

> +1 non-binding to release 9.10.0rc1.
>
> I ran the example DAGs for S3 along with deferrable modes.
>
> Regards,
> *Ankit Chaurasia*
>
>
>
>
>
>
>
> On Wed, Jul 9, 2025 at 12:09 PM Amogh Desai <amoghdesai....@gmail.com>
> wrote:
>
> > +1 binding.
> >
> > - Checked SVN
> > - Checked in Docker
> > - Checked reproducible package builds
> > - Checked licenses
> > - Checked Signatures
> >
> > Installed the RC and checked if my cleanup code is present or not. It is
> > present and looks good!
> >
> > Thanks & Regards,
> > Amogh Desai
> >
> >
> > On Wed, Jul 9, 2025 at 12:39 AM Jens Scheffler
> <j_scheff...@gmx.de.invalid
> > >
> > wrote:
> >
> > > +1 (binding) - Checked SVN, Check in Docker, Reproducible package
> build,
> > > Licenses, Signatures
> > >
> > > Unable to test amazon provider, so this is just the technical release
> > > check.
> > >
> > > On 08.07.25 12:20, Elad Kalif wrote:
> > > > Hey all,
> > > >
> > > > I have just cut amazon ad-hoc Airflow Provider package. This email is
> > > > calling a vote on the release, which will last for 72 hours - which
> > means
> > > > that it will end on July 11, 2025 10:15 AM UTC and until 3 binding +1
> > > votes
> > > > have been received.
> > > >
> > > >
> > > > Consider this my (binding) +1.
> > > >
> > > > Note: For amazon provider we are not having 9.9.1rc2 but we are
> voting
> > on
> > > > 9.10.0rc1
> > > > This is because we merged a feature change that is included in the
> > > release.
> > > > That is also why this vote is a regular 72 hours vote rather than 24
> > > hours
> > > > expedited vote.
> > > >
> > > > 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/53016
> > > >
> > > > 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.10.0rc1/
> > > >
> > > > Cheers,
> > > > Elad Kalif
> > > >
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: dev-unsubscr...@airflow.apache.org
> > > For additional commands, e-mail: dev-h...@airflow.apache.org
> > >
> > >
> >
>

Reply via email to