+1 binding.

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

Installed the RC with breeze and ran a few of my example dags in general,
along with targeted testing for my changes as described on the issue, all
good.

Thanks & Regards,
Amogh Desai


On Thu, Jan 15, 2026 at 8:25 AM Dheeraj Turaga <[email protected]>
wrote:

> +1 (non binding)
>
> was able to scale test and stress test edge3 since its a major release! my
> analysis posted on the PR
>
> On Wed, Jan 14, 2026 at 1:09 PM Vincent Beck <[email protected]> wrote:
>
> > +1 binding. Checked:
> >
> > * SVN
> > * Reproducible package builds
> > * Licence
> > * Signature
> > * SHA512
> >
> > On 2026/01/14 15:10:52 Jarek Potiuk wrote:
> > > + 1 (binding). Checked:
> > >
> > > * SVN
> > > * installation in Docker
> > > * reproducibility
> > > * checksums
> > > * signatures
> > > * licences
> > >
> > > Also:
> > >
> > > Checked all dependency changes that were implemented in providers for
> > > sqlalchemy optional dependencies. Deltalake limit changes were dev-only
> > > without impact on wheels.
> > > Checked (with Copilot /Claude Sonnet :) ) that all NOTICE files in all
> > the
> > > packages contain correct year:
> > >
> > >  ● Perfect! All packages have been extracted and verified. Here's the
> > > summary:
> > >
> > >    ✅ All 202 NOTICE files contain "2026"
> > >
> > >    The NOTICE files in all extracted packages correctly include the
> > > copyright year 2026 in the format:
> > >
> > >      Copyright 2016-2026 The Apache Software Foundation
> > >
> > >    Every package in the dist directory has been verified successfully.
> > >
> > > I found a small issue in PMC verification process, where we skipped the
> > > source tarball in reproducibility check (!) instead of checking it -
> fix
> > in
> > > https://github.com/apache/airflow/pull/60525
> > >
> > > J.
> > >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: [email protected]
> > For additional commands, e-mail: [email protected]
> >
> >
>

Reply via email to