+1 binding

On Fri, 18 Jul 2025 at 12:38, Pavankumar Gopidesu <gopidesupa...@gmail.com>
wrote:

> +1 non binding.
>
> Tested a few examples with ShortCircuitOperator , looks good to me.
>
> Pavan
>
> On Fri, Jul 18, 2025 at 7:40 AM Jarek Potiuk <ja...@potiuk.com> wrote:
>
> > +1 (binding) - checked:
> >
> > * svn
> > * installation
> > * reproducibility
> > * licences
> > * signatures
> > * checksums
> >
> > I installed the standard provider 1.4.1rc2 with Airflow 3.0.3. Ran a few
> > Dags which are using standard provider operators - all looks good.
> >
> > J.
> >
> >
> >
> > On Thu, Jul 17, 2025 at 10:23 PM Jens Scheffler
> <j_scheff...@gmx.de.invalid
> > >
> > wrote:
> >
> > > +1 (binding) - Checked SVN, Check in Docker, Reproducible package
> build,
> > > Licenses, Signatures
> > >
> > > Tested the standard provider with Airflow 2.11 and 3.0.3 by running the
> > > integration_test Dag via EdgeExecutor, all looks good!
> > >
> > > On 17.07.25 21:23, 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 *24 hours* - which means that it will end on July
> > 18,
> > > > 2025 19:20 PM UTC and until 3 binding +1 votes have been received.
> > > >
> > > > Consider this my (binding) +1.
> > > >
> > > > *This is a shortened vote as it contains an important bugfix.*
> > > >
> > > > 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/53471
> > > >
> > > > 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-standard/1.4.1rc2/
> > > >
> > > > 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