+1 binding

On Mon, 19 Oct 2026 at 09:55, Jarek Potiuk <[email protected]> wrote:

> One more vote is needed :)
>
> On Sun, Oct 18, 2026 at 7:18 PM Jarek Potiuk <[email protected]> wrote:
>
> > > = byte-identical. Only repro-archive check layout rules fail (unsorted
> > members, root:root, 0700/0600). Breeze repack convention, deterministic,
> > not blocking
> >
> > Yeah. We tested a new reproducibility "archive packing" approach (non
> > Python)
> > that is likely going to be shared across ASF archives and we will likely
> use
> > it
> > in the future - already implemented in Magpie, so we should be able to
> > merge
> > Magpie's release SKILLS with ours.
> >
> >
> > On Sun, Oct 18, 2026 at 7:11 PM Shahar Epstein <[email protected]>
> wrote:
> >
> >> +1 (binding) with warnings, checked:
> >> - SVN
> >> - Checksums
> >> - Licenses
> >> - Signatures
> >> - Reproducibility - Source tarball, sdist, wheel rebuilt at tag with
> >> Breeze
> >> = byte-identical. Only repro-archive check layout rules fail (unsorted
> >> members, root:root, 0700/0600). Breeze repack convention, deterministic,
> >> not blocking
> >>
> >>
> >> Shahar
> >>
> >> On Sun, Oct 18, 2026 at 2:06 AM Jarek Potiuk <[email protected]> wrote:
> >>
> >> > Hey all,
> >> >
> >> > I have just cut the new wave Airflow Providers packages with release
> >> > preparation date 2026-10-17. This email is calling a vote on the
> >> > release, which will last for 24 hours - which means that it will end
> >> > on 2026-10-19 00:00 UTC and until 3 binding +1 votes have been
> >> > received.
> >> >
> >> > This is an ad-hoc wave with a single provider, common.ai 1.0.0rc3,
> the
> >> > first stable release of the provider. It was excluded from the
> >> > 2026-10-14 wave so that it could ship with the pydantic-ai-skills cap
> >> > (#74899): the "skills" extra allowed pydantic-ai-skills 2.x, which
> >> > breaks a fresh "[skills]" install at run time. Since rc1 it also
> >> > gained the changes merged in the meantime (OpenAI Agents SDK adapter,
> >> > durable replay and tracing, retry-policy reschedule, and several
> >> > fixes) and the docs fixes found while testing rc1 (#74904, #74939).
> >> > rc2 was cut but never put to a vote and is superseded by rc3.
> >> >
> >> > I am running it on an accelerated timeline because it is a re-cut of a
> >> > provider that was already tested in the 2026-10-14 wave (#74741), and
> >> > most of its changes were verified there. If, for any reason, there is
> >> > a binding objection to running in accelerated mode, or if there are
> >> > not enough binding votes during that time, this vote will be converted
> >> > into a regular vote ending 72 hours from now, on 2026-10-21 00:00 UTC.
> >> >
> >> > Consider this my (binding) +1.
> >> >
> >> > Airflow Providers are available at:
> >> > https://dist.apache.org/repos/dist/dev/airflow/providers/2026-10-17
> >> >
> >> > *apache-airflow-providers-2026-10-17-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.
> >> >
> >> > There is no separate testing issue for this wave; the testing status
> >> > of the changes carried over from rc1 is in
> >> > https://github.com/apache/airflow/issues/74741.
> >> >
> >> > You can find the RC packages in PyPI following these links:
> >> >
> >> > https://pypi.org/project/apache-airflow-providers-common-ai/1.0.0rc3/
> >> >
> >> > Cheers,
> >> > Jarek Potiuk
> >> >
> >> > ---------------------------------------------------------------------
> >> > To unsubscribe, e-mail: [email protected]
> >> > For additional commands, e-mail: [email protected]
> >> >
> >> >
> >>
> >
>

Reply via email to