+1 (non-binding)

[x] Checksums and PGP signatures are valid
[x] LICENSE and NOTICE files are correct
[x] All files have ASF license headers where appropriate
[x] Source tarball matches the Git tag
[x] Docker Compose deploys successfully

What I checked:
- SHA-512 checksums match for both tarballs. Both signatures are good. They
are made by subkey 36B1DAC3286B3199B4CEFC2BB49658187ADCD1BD of key
FF178695C2B38EC0BB8F4C4933CC8C5B60E46FA4.
- Every third-party path listed in LICENSE exists. The source tarball has
no jar, class or native library files.
- skywalking-eyes 0.6.0 header check: 2309 files checked, 0 invalid.
- The source tarball contents are identical to the tag at
c4460dbb54e39e1d8b666b1843d0445489bebfa0. I also rebuilt the tarball byte
for byte with GNU tar 1.35. This needed the release tarball's file order
and umask 022.
- Docker Compose with the examples profile on macOS (arm64): all services
became healthy. I logged in and ran the Iris example workflow to completion.

Two non-blocking notes:
- The source tarball step in create-release-candidate.yml uses plain "tar
-czf". The tar output then depends on the file system's file order and the
umask, so a reviewer cannot reproduce the checksum without extra steps.
Adding "--sort=name --owner=0 --group=0 --numeric-owner --mode=go-w" made
the tar output identical across the two setups I tried.
- The Docker images have no label with the Texera commit.
build-and-push-images.yml sets only the title, description and vendor
labels. The other labels come from the base images. For example, the Java
images show version 22.04 from Ubuntu. agent-service shows revision
a7733435, which is a commit in oven-sh/bun. So I could not confirm from the
images which commit they were built from. Adding
org.opencontainers.image.revision to the workflow labels would fix this.

Thanks for preparing RC2!

Kary

On Sat, Nov 21, 2026 at 3:36 PM Kun Woo Park <[email protected]> wrote:

> +1
>
> [x] Checksums and PGP signatures are valid
> [x] LICENSE and NOTICE files are correct
> [x] All files have ASF license headers where appropriate
> [x] Source tarball matches the Git tag
> [x] Docker Compose deploys successfully
>
> What I checked (macOS arm64, Docker 28.0.1):
> - SHA-512 checksums match for the source and Docker Compose tarballs. Both
> GPG signatures are good, made by subkey
> 36B1DAC3286B3199B4CEFC2BB49658187ADCD1BD
> of FF178695C2B38EC0BB8F4C4933CC8C5B60E46FA4 from the KEYS file.
> - The source tarball is identical to `git archive` of tag
> v1.2.1-incubating-rc2 (c4460dbb54e39e1d8b666b1843d0445489bebfa0).
> - skywalking-eyes 0.7.0 with the repo's .licenserc.yaml: 2147 valid, 0
> invalid,
> 162 ignored. No compiled binaries in the source release; the bundled
> yarn-4.14.1.cjs is listed in LICENSE.
> - NOTICE and DISCLAIMER are present and correct. Every third-party file
> named
> in LICENSE exists, and its license text is in licenses/ or
> licenses-3rd-party-code/. The compose bundle's LICENSE covers its Iris
> dataset.
> - Docker Compose: `docker compose --profile examples up` with the rc2
> images
> brought every service up healthy, and the example loader created the
> iris-species dataset and the example workflow. I logged in, created a local
> computing unit and ran "[Example] Machine Learning on Iris Dataset". It
> finished with every operator completed (150 rows in; both sklearn branches
> trained and predicted).
>
> Minor, not blocking: the Texera images have no
> org.opencontainers.image.revision label. The only revision label, on
> agent-service, comes from the oven/bun base image. Adding the source commit
> as a label would let voters check the "same commit" claim directly.
>
> --
> Best Regards,
> Kunwoo (Chris) Park
>
>
> ----------------------------------------------------------------------------
> Kunwoo (Chris) Park
> He/Him/His
> Ph.D. Student
> Donald Bren School of Information & Computer Sciences
> 2059 Bren Hall
> (949) 413-5324
>
> ----------------------------------------------------------------------------
> On Nov 21, 2026 at 1:55 PM -0800, Xuan Gu via dev <[email protected]>,
> wrote:
> > Hi Texera Community,
> >
> > This is a call for a vote on the second release candidate (RC2) of
> > Apache Texera (incubating) 1.2.1-incubating, cut from the release/v1.2
> > branch.
> >
> > == Changes Since RC1 ==
> > RC2 addresses the licensing issues raised during the RC1 vote, updates
> > the binary license metadata, removes the deprecated project feature,
> > and includes bug fixes.
> >
> > Full diff:
> >
> https://urldefense.com/v3/__https://github.com/apache/texera/compare/v1.2.1-incubating-rc1...v1.2.1-incubating-rc2__;!!CzAuKJ42GuquVTTmVmPViYEvSg!Mif50DQlWOo0BzLQTlT_dxQrwmZbxF1VV5nEutL1-ARlJGK3YocL3YHC6U116-V3G0arkbf7aTnsHTLw$
> >
> > == Release Candidate Artifacts ==
> >
> https://urldefense.com/v3/__https://dist.apache.org/repos/dist/dev/incubator/texera/1.2.1-incubating-RC2/__;!!CzAuKJ42GuquVTTmVmPViYEvSg!Mif50DQlWOo0BzLQTlT_dxQrwmZbxF1VV5nEutL1-ARlJGK3YocL3YHC6U116-V3G0arkbf7aWnSrHh4$
> >
> > The directory contains:
> > - Source tarball (.tar.gz) with a GPG signature (.asc) and SHA-512
> > checksum (.sha512)
> > - Docker Compose deployment bundle with a GPG signature and SHA-512
> checksum
> >
> > == Container Images ==
> > The following images are available on Docker Hub:
> >
> > apache/texera-dashboard-service:1.2.1-incubating-rc2
> > apache/texera-workflow-execution-coordinator:1.2.1-incubating-rc2
> > apache/texera-workflow-execution-runner:1.2.1-incubating-rc2
> > apache/texera-workflow-compiling-service:1.2.1-incubating-rc2
> > apache/texera-file-service:1.2.1-incubating-rc2
> > apache/texera-config-service:1.2.1-incubating-rc2
> > apache/texera-access-control-service:1.2.1-incubating-rc2
> > apache/texera-agent-service:1.2.1-incubating-rc2
> >
> apache/texera-workflow-computing-unit-managing-service:1.2.1-incubating-rc2
> >
> > These images were built from the same commit as the source tarball
> > included in this release candidate.
> >
> > == Git Tag ==
> >
> https://urldefense.com/v3/__https://github.com/apache/texera/releases/tag/v1.2.1-incubating-rc2__;!!CzAuKJ42GuquVTTmVmPViYEvSg!Mif50DQlWOo0BzLQTlT_dxQrwmZbxF1VV5nEutL1-ARlJGK3YocL3YHC6U116-V3G0arkbf7aTop3QjD$
> > Commit: c4460dbb54e39e1d8b666b1843d0445489bebfa0
> >
> > == Keys ==
> > KEYS file:
> https://urldefense.com/v3/__https://downloads.apache.org/incubator/texera/KEYS__;!!CzAuKJ42GuquVTTmVmPViYEvSg!Mif50DQlWOo0BzLQTlT_dxQrwmZbxF1VV5nEutL1-ARlJGK3YocL3YHC6U116-V3G0arkbf7aQNc80fl$
> > Signing key fingerprint: FF178695C2B38EC0BB8F4C4933CC8C5B60E46FA4
> > ([email protected])
> >
> > == Verification Guide ==
> > A verification guide is available here:
> >
> https://urldefense.com/v3/__https://docs.google.com/document/d/1SIQoOwHmSjpm-GIij2-tlM3ArIKlnO_dyVs5qcbIsNA/edit?usp=sharing__;!!CzAuKJ42GuquVTTmVmPViYEvSg!Mif50DQlWOo0BzLQTlT_dxQrwmZbxF1VV5nEutL1-ARlJGK3YocL3YHC6U116-V3G0arkbf7aR45tTUT$
> >
> > == Vote ==
> > The vote will remain open for at least 72 hours.
> > The vote passes with at least three binding +1 votes and more +1 than -1
> votes.
> >
> > [ ] +1 Approve the release
> > [ ] 0 No opinion
> > [ ] -1 Disapprove the release (please provide a reason)
> >
> > == Checklist ==
> > Please include the checklist below in your reply and mark the checks
> > you performed with an x.
> >
> > [ ] Checksums and PGP signatures are valid
> > [ ] LICENSE and NOTICE files are correct
> > [ ] All files have ASF license headers where appropriate
> > [ ] Source tarball matches the Git tag
> > [ ] Docker Compose deploys successfully
> >
> > Thank you for reviewing and voting on this release candidate.
> >
> > Best,
> > Xuan Gu
>

Reply via email to