+1 (binding)

1. Download looks good.
2. LICENSE/NOTICE looks good.
3. Compile looks good.
4. Checkstyle and gpg look good.
5. PyPaimon works well.

Best,
Jingsong

On Wed, Nov 5, 2025 at 2:18 PM JUNHAO YE <[email protected]> wrote:
>
> +1 for the release.
>
> I've checked
>
> [√] Download links are valid.
> [√ ] Checksums and signatures.
> [√ ] LICENSE/NOTICE files exist
> [√ ] No unexpected binary files
> [√] All source files have ASF headers
> [√ ] Can compile from source
>
> > 2025年10月31日 15:53,yu zelin <[email protected]> 写道:
> >
> > Hello Paimon devs,
> >
> > Kindly request the devs to review and vote for releasing Paimon 1.3.0 and
> > Pypaimon 1.3.0 which is an SDK for Python.
> >
> > The official Apache source release to be deployed:
> > https://dist.apache.org/repos/dist/dev/paimon/paimon-1.3.0-rc3/
> > https://dist.apache.org/repos/dist/dev/paimon/pypaimon-1.3.0-rc3/
> >
> > This source release has been signed with a PGP available here:
> > https://downloads.apache.org/paimon/KEYS
> >
> > All artifacts to be deployed to the Maven Central Repository:
> > https://repository.apache.org/content/repositories/orgapachepaimon-1127/ 
> > (for
> > all modules that compiled with JDK8)
> > https://repository.apache.org/content/repositories/orgapachepaimon-1129/
> > (for spark4 with JDK17)
> > https://repository.apache.org/content/repositories/orgapachepaimon-1128/ 
> > (for
> > paimon-flink2 and paimon-iceberg with JDK11)
> >
> > Git branch for the release:
> > https://github.com/apache/paimon/tree/release-1.3.0-rc3
> >
> > Please download, verify, and test.
> >
> > The VOTE will pass after 3 binding approve.
> >
> > [ ] +1 approve
> > [ ] +0 no opinion
> > [ ] -1 disapprove with the reason
> >
> > To learn more about apache paimon, please see https://paimon.apache.org/
> >
> > Checklist for reference:
> >
> > [ ] Download links are valid.
> > [ ] Checksums and signatures.
> > [ ] LICENSE/NOTICE files exist
> > [ ] No unexpected binary files
> > [ ] All source files have ASF headers
> > [ ] Can compile from source
>

Reply via email to