Hi Ian, Good catch on the Docker image tags — I shouldn't have used 1.1.0-incubating for those. I'll contact the infrastructure to get them removed.
Regarding the source-only release: Texera is a multi-service application (backend, frontend, multiple workers, etc.) and we don't expect users to launch each service individually. The intended deployment method is via Docker/Kubernetes with orchestration scripts. Because of that, I think standalone binary artifacts wouldn't be very useful to end users. That said, if there's an ASF expectation or recommendation to include convenience binaries alongside the source release, we're happy to add them. Thanks, Jiadong On Tue, Feb 10, 2026 at 1:09 PM Ian Maxon <[email protected]> wrote: > Hey Jiadong, > Cool, thanks for addressing that issue with the tag so quickly. > I'm a little surprised about the release being source-only. I noticed > some github workflows relating to docker image creation and some > images here: https://hub.docker.com/u/apache?page=1&search=texera > I would also apply my comment about the tag here- I noticed some with > v1.10-incubating as a version. I think that's misleading when it's an > RC (or perhaps not even, in those cases). > What is the reasoning behind making the release source-only? > > > - Ian > > On Tue, Feb 10, 2026 at 12:03 PM Jiadong Bai <[email protected]> wrote: > > > > Hi Ian, > > > > The tag is changed to v1.1.0-incubating-rc2: > > https://github.com/apache/texera/tree/v1.1.0-incubating-rc2. > > > > The RC is a source-code-only tarball built via an automated GitHub > Actions > > workflow > > < > https://github.com/apache/texera/blob/v1.1.0-incubating-rc2/.github/workflows/create-release-candidate.yml > >. > > It currently contains no binaries. > > > > For automated checks, the RC workflow itself verifies tag format, tarball > > integrity, and GPG signatures. Separately, our CI pipeline runs Apache > RAT > > license header checks, backend and frontend unit tests, and build > > verification on every PR merge. > > > > Thanks, > > Jiadong > > > > On Tue, Feb 10, 2026 at 11:40 AM Ian Maxon <[email protected]> wrote: > > > > > I would change the tag name to reflect the fact it's an RC, and not > > > the accepted release. Otherwise I don't see how someone would > > > reasonably know. > > > Furthermore, how was the release built? What does it contain? What > > > automated checks were already done on it? Those are all important > > > things to know when evaluating an RC. > > > > > > On Tue, Feb 10, 2026 at 11:19 AM Jiadong Bai <[email protected]> > wrote: > > > > > > > > Hi Texera Community, > > > > > > > > The Apache Texera (incubating) PMCs are preparing to release version > > > > 1.1.0-incubating. We would appreciate any feedback from the community > > > > before we proceed to a formal [VOTE] thread. > > > > > > > > == Release Candidate Artifacts == > > > > > > > > https://dist.apache.org/repos/dist/dev/incubator/texera/1.1.0-incubating-RC2/ > > > > > > > > == Git Tag == > > > > https://github.com/apache/texera/releases/tag/v1.1.0-incubating > > > > Commit: 7048ce340a2557ff3810206c8583c3e775972746 > > > > > > > > == Keys == > > > > KEYS file: https://downloads.apache.org/incubator/texera/KEYS > > > > > > > > This is a discussion thread to gather feedback before calling a > formal > > > > release vote. Any comments or concerns are appreciated. > > > > > > > > Thanks, > > > > Jiadong Bai > > > > Apache Texera (incubating) PMC > > > >
