+1 (binding)

Thank you Meng for preparing this release candidate!

[x] Checksums and PGP signatures are valid
[x] LICENSE and NOTICE files are correct
[x] All files have ASF license headers where appropriate
[x] No unexpected binary files
[x] Source tarball matches the Git tag
[x] Rebuilt tarballs match the staged SHA512 checksums
[x] Can compile from source successfully
[x] Docker Compose bundle deploys successfully with the published images

Best,
Xiaozhen Liu



> On Nov 12, 2026, at 15:37, Kary Zheng <[email protected]> wrote:
> 
> +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] No unexpected binary files
> [x] Source tarball matches the Git tag
> [x] Rebuilt tarballs match the staged SHA512 checksums
> [x] Can compile from source successfully
> [x] Docker Compose bundle deploys successfully with the published images
> 
> One non-blocking note: the rebuilt tarballs match with GNU tar 1.35.
> With tar 1.34 (Debian 12, Ubuntu 22.04) every differing byte is in the
> devmajor/devminor header fields and the header checksums, so the
> SHA512 does not match. It may help to name the tar version or a
> container image (e.g. debian:trixie) in the reproduce steps.
> 
> Tested on macOS (arm64) with Docker Desktop.
> 
> Thanks Meng for driving the release!
> 
> Best Regards,
> Kary
> 
> On Thu, Nov 12, 2026 at 3:12 PM Kun Woo Park <[email protected]> wrote:
> 
>> +1 (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] No unexpected binary files
>> [x] Source tarball matches the Git tag
>> [x] Rebuilt tarballs match the staged SHA512 checksums
>> [x] Can compile from source successfully
>> [x] Docker Compose bundle deploys successfully with the published images
>> 
>> What I checked (macOS arm64, Docker 28.0.1):
>> - SHA-512 OK for both tarballs; good signature from
>> D4F761FF20CF28580A5A9D1D80BBC55290D0C350 (KEYS).
>> - The tag resolves to 177ed201; git archive of the tag is identical to the
>> extracted source tarball, including file modes.
>> - skywalking-eyes header check with the shipped .licenserc.yaml: 3038
>> files, 0 invalid.
>> - Binary files: only images, plus the self-created sample-audio.wav and
>> sample-video.mp4; no jars, classes or archives.
>> - Rebuilt both tarballs in ubuntu:24.04 (GNU tar 1.35, gzip 1.12):
>> byte-identical to the staged ones.
>> - Built with JDK 17: sbt clean plus the AccessControlService,
>> ComputingUnitManagingService, ConfigService, FileService,
>> NotebookMigrationService, WorkflowCompilingService and
>> WorkflowExecutionService dist targets (jOOQ codegen against a scratch
>> Postgres loaded from sql/). Frontend in node:24: yarn install --immutable
>> && yarn run build.
>> - docker compose --profile examples up: every service with a health check
>> is healthy, init jobs exit 0, examples load. Logged in, created a local
>> computing unit, and ran "[Example] Machine Learning on Iris Dataset" to
>> completion; results and the dataset preview render.
>> - arm64 coordinator and runner images: torch 2.13.0+cpu, no nvidia
>> packages.
>> 
>> Non-blocking notes:
>> 1. Reproducing needs GNU tar >= 1.35. With tar 1.34 (debian:bookworm) both
>> tarballs differ: 1.34 writes "0000000" into devmajor/devminor for regular
>> files, where 1.35 leaves them empty. Contents and other metadata are
>> identical. Worth saying "GNU tar 1.35+, e.g. ubuntu:24.04" in the
>> instructions.
>> 2. Bundle README nits: it says it pre-creates "two example workflows and
>> datasets" but ships one of each; the Docker-daemon error example contains a
>> contributor's local socket path (/Users/<name>/.docker/run/docker.sock);
>> the volume name in the data-location example
>> (texera-single-node-release-1-1-0_...) is out of date.
>> 
>> --
>> 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 12, 2026 at 9:03 AM -0800, Jiadong Bai via dev <
>> [email protected]>, wrote:
>>> +1 (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] No unexpected binary files
>>> 
>>> [x] Source tarball matches the Git tag
>>> 
>>> [x] Rebuilt tarballs match the staged SHA512 checksums
>>> 
>>> [x] Can compile from source successfully
>>> 
>>> [x] Docker Compose bundle deploys successfully with the published images
>>> 
>>> Best,
>>> Jiadong
>>> 
>>> On Tue, Nov 10, 2026 at 8:41 PM Suryaa Charan <[email protected]>
>>> wrote:
>>> 
>>>> Thank you Meng for your efforts!
>>>> 
>>>> +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
>>>> - skywalking-eyes 0.7.0 with .licenserc.yaml: 0 invalid. I can
>>>> confirm Ryan's RAT observation; the three files are intentionally
>>>> excluded. Totally checked 3038 files, valid: 2869, invalid: 0,
>>>> ignored: 169, fixed: 0
>>>> [X] No unexpected binary files
>>>> - All of these are images and media files. No .jar, .class, .so or
>>>> .whl files appear
>>>> [X] Source tarball matches the Git tag
>>>> [X] Rebuilt tarballs match the staged SHA512 checksums
>>>> - As Ryan pointed out, byte-identical in debian:trixie-slim (GNU tar
>>>> 1.35).
>>>> Confirm tar 1.34 differs only in devmajor/devminor;
>>>> [X] Can compile from source successfully
>>>> - sbt compile + all service dists, frontend prod build lists a
>>>> bunch of warnings but no errors
>>>> [X] Docker Compose bundle deploys successfully with the published
>> images
>>>> - Tested on macOS arm64. All 11 images multi-arch; verified the
>>>> RC2 fix (torch +cpu, no NVIDIA/CUDA packages) on arm64 and amd64 of
>>>> the coordinator/runner images. Ran the example workflows.
>>>> 
>>>> 
>>>> On Tue, 10 Nov 2026 at 12:21, Ryan Zhang <[email protected]> wrote:
>>>>>> 
>>>>>> +1 (non-binding)
>>>>>> 
>>>>>> Everything passed on my local checks, but I ran into some things
>> that
>>>> I've
>>>>>> noted below the appropriate check (all are non-blocking). I
>> couldn't
>>>> find a
>>>>>> guide for this RC, so I followed the procedure from previous RC
>>>>>> verifications. It would be good if other people can verify if this
>>>> happened
>>>>>> to them too, or if it was only caused by something in my local
>>>> environment.
>>>>>> 
>>>>>> [X] Checksums and PGP signatures are valid
>>>>>> [X] LICENSE and NOTICE files are correct
>>>>>> [X] All files have ASF license headers where appropriate
>>>>>> 
>>>>>> - RAT with the .rat-excludes from the 1.2.x verification guide
>> flags 3
>>>>>> files (bin/k8s/.helmignore, amber/.../customized_queue/inner.py,
>>>>>> frontend/.../icon/model-icon.ts). All are excluded in
>>>> .licenserc.yaml, so
>>>>>> that exclude list needs updating for 1.3.0.
>>>>>> 
>>>>>> [X] No unexpected binary files
>>>>>> 
>>>>>> - frontend/src/assets/Tutor_*.gif/.jpeg (8 files, ~3.8 MB) are
>>>>>> not referenced anywhere and could be removed.
>>>>>> 
>>>>>> [X] Source tarball matches the Git tag
>>>>>> [X] Rebuilt tarballs match the staged SHA512 checksums
>>>>>> 
>>>>>> - Requires GNU tar >= 1.35. With tar 1.34 (e.g. Debian 12 / Ubuntu
>>>>>> 22.04) the checksums differ only in the tar headers'
>> devmajor/devminor
>>>>>> fields. It may be worth stating the required version in the
>>>> instructions. I
>>>>>> was able to reproduce exactly with debian:trixie-slim.
>>>>>> 
>>>>>> [X] Can compile from source successfully
>>>>>> [X] Docker Compose bundle deploys successfully with the published
>> images
>>>>>> 
>>>>>> I also tested the notebook migration tool on the single-node
>> deployment,
>>>>>> and it works with no issues. For others who want to test it,
>> you’ll need
>>>> to
>>>>>> export an API key for the LLM (Claude Haiku 4.5 by default) before
>>>> starting
>>>>>> the Docker Compose bundle.
>>>>>> 
>>>>>> Thanks,
>>>>>> Ryan
>>>>>> 
>>>>>> 
>>>>>> On Tue, Nov 10, 2026 at 5:08 AM Meng Wang via dev <
>> [email protected]
>>>>>> 
>>>>>> wrote:
>>>>>> 
>>>>>>>> Hi Texera Community,
>>>>>>>> 
>>>>>>>> This is a call for a vote on releasing Apache Texera
>> (incubating)
>>>>>>>> 
>>>>>>>> 1.3.0-incubating RC2.
>>>>>>>> 
>>>>>>>> == Changes Since RC1 ==
>>>>>>>> 
>>>>>>>> RC1 was withdrawn before a vote. RC2 incorporates a fix for a
>>>>>>>> 
>>>>>>>> third-party licensing issue in two arm64 container images.
>>>>>>>> 
>>>>>>>> Full diff:
>>>>>>>> 
>>>>>>>> 
>>>>>>>> 
>>>> 
>> https://urldefense.com/v3/__https://github.com/apache/texera/compare/v1.3.0-incubating-rc1...v1.3.0-incubating-rc2__;!!CzAuKJ42GuquVTTmVmPViYEvSg!Of8h1eiGp6icfGhqwhaBonTj4KEH7tcbBHdQnYTvfoQwuCw1w9frBiVHhuzyweZEP8ZgwWJub0iw5M4$
>>>>>>>> 
>>>>>>>> == Release Candidate Artifacts ==
>>>>>>>> 
>>>>>>>> 
>>>>>>>> 
>>>> 
>> https://urldefense.com/v3/__https://dist.apache.org/repos/dist/dev/incubator/texera/1.3.0-incubating-RC2/__;!!CzAuKJ42GuquVTTmVmPViYEvSg!Of8h1eiGp6icfGhqwhaBonTj4KEH7tcbBHdQnYTvfoQwuCw1w9frBiVHhuzyweZEP8ZgwWJu6V7CXuQ$
>>>>>>>> 
>>>>>>>> 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.3.0-incubating-rc2
>>>>>>>> 
>>>>>>>> 
>> apache/texera-workflow-execution-coordinator:1.3.0-incubating-rc2
>>>>>>>> 
>>>>>>>> apache/texera-workflow-execution-runner:1.3.0-incubating-rc2
>>>>>>>> 
>>>>>>>> apache/texera-workflow-compiling-service:1.3.0-incubating-rc2
>>>>>>>> 
>>>>>>>> apache/texera-file-service:1.3.0-incubating-rc2
>>>>>>>> 
>>>>>>>> apache/texera-config-service:1.3.0-incubating-rc2
>>>>>>>> 
>>>>>>>> apache/texera-access-control-service:1.3.0-incubating-rc2
>>>>>>>> 
>>>>>>>> apache/texera-agent-service:1.3.0-incubating-rc2
>>>>>>>> 
>>>>>>>> 
>>>> 
>> apache/texera-workflow-computing-unit-managing-service:1.3.0-incubating-rc2
>>>>>>>> 
>>>>>>>> apache/texera-notebook-migration-service:1.3.0-incubating-rc2
>>>>>>>> 
>>>>>>>> apache/texera-jupyter:1.3.0-incubating-rc2
>>>>>>>> 
>>>>>>>> These images are built from the source tarball included in this
>>>> release.
>>>>>>>> 
>>>>>>>> The Dockerfiles are included in the source for audit and
>> verification.
>>>>>>>> 
>>>>>>>> == Git Tag ==
>>>>>>>> 
>>>>>>>> 
>>>>>>>> 
>>>> 
>> https://urldefense.com/v3/__https://github.com/apache/texera/releases/tag/v1.3.0-incubating-rc2__;!!CzAuKJ42GuquVTTmVmPViYEvSg!Of8h1eiGp6icfGhqwhaBonTj4KEH7tcbBHdQnYTvfoQwuCw1w9frBiVHhuzyweZEP8ZgwWJuLFLC7CE$
>>>>>>>> 
>>>>>>>> Commit: 177ed20102d42813bc9a15bb1781d6370ddc822f
>>>>>>>> 
>>>>>>>> == Reproducing the Artifacts ==
>>>>>>>> 
>>>>>>>> Both tarballs are reproducible. To rebuild them from the tag
>> (needs
>>>> GNU tar
>>>>>>>> 
>>>>>>>> and GNU gzip; macOS's built-in gzip produces different bytes,
>> so on
>>>> macOS
>>>>>>>> 
>>>>>>>> run this in a Linux container) and compare against the staged
>>>> checksums:
>>>>>>>> 
>>>>>>>> git clone
>>>>>>>> 
>>>> 
>> https://urldefense.com/v3/__https://github.com/apache/texera.git__;!!CzAuKJ42GuquVTTmVmPViYEvSg!Of8h1eiGp6icfGhqwhaBonTj4KEH7tcbBHdQnYTvfoQwuCw1w9frBiVHhuzyweZEP8ZgwWJujf_PLug$
>>>>>>>> && cd texera
>>>>>>>> 
>>>>>>>> git checkout v1.3.0-incubating-rc2
>>>>>>>> 
>>>>>>>> ./.github/scripts/create-release-tarballs.sh
>> v1.3.0-incubating-rc2
>>>>>>>> 1.3.0-incubating docker.io/apache 1.3.0-incubating-rc2
>> /tmp/texera-rc
>>>>>>>> 
>>>>>>>> sha512sum /tmp/texera-rc/*.tar.gz
>>>>>>>> 
>>>>>>>> == Keys ==
>>>>>>>> 
>>>>>>>> The release was signed with GPG key
>>>>>>>> [D4F761FF20CF28580A5A9D1D80BBC55290D0C350] ([email protected]
>> )
>>>>>>>> 
>>>>>>>> KEYS file:
>>>>>>>> 
>>>> 
>> https://urldefense.com/v3/__https://downloads.apache.org/incubator/texera/KEYS__;!!CzAuKJ42GuquVTTmVmPViYEvSg!Of8h1eiGp6icfGhqwhaBonTj4KEH7tcbBHdQnYTvfoQwuCw1w9frBiVHhuzyweZEP8ZgwWJusunbYlw$
>>>>>>>> 
>>>>>>>> == 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
>>>>>>>> 
>>>>>>>> [ ] No unexpected binary files
>>>>>>>> 
>>>>>>>> [ ] Source tarball matches the Git tag
>>>>>>>> 
>>>>>>>> [ ] Rebuilt tarballs match the staged SHA512 checksums
>>>>>>>> 
>>>>>>>> [ ] Can compile from source successfully
>>>>>>>> 
>>>>>>>> [ ] Docker Compose bundle deploys successfully with the
>> published
>>>> images
>>>>>>>> 
>>>>>>>> Thank you for reviewing and voting on this release candidate.
>>>>>>>> 
>>>>>>>> Best,
>>>>>>>> 
>>>>>>>> Meng Wang
>>>>>>>> 
>>>>>>>> Release Manager for Apache Texera v1.3
>>>>>>>> 
>>>> 
>> 

Reply via email to