Dear community, RC3 has been created. Please see: - https://github.com/apache/texera/releases/tag/v1.1.0-incubating-rc3 for the pre-release on the Github - https://dist.apache.org/repos/dist/dev/incubator/texera/1.1.0-incubating-RC3/ for the artifacts
Compared to RC2, the release artifacts now include the tarball of docker compose and helm chart, enabling users to deploy Texera using docker or kubernetes in just a few commands. Please let me know if you have any comments and questions. Best regards, Jiadong On Mon, Feb 16, 2026 at 9:41 AM Jiadong Bai <[email protected]> wrote: > Dear Ian, > > I created this PR: https://github.com/apache/texera/pull/4219 to address > your comment. Can you review it? In short, it followed the flink's paradigm > to include the docker compose tarball and helm chart tarball for users to > instantly setup texera using the release. Images will be host on ghcr.io. > > Best regards, > Jiadong > > On Wed, Feb 11, 2026 at 2:25 PM Ian Maxon <[email protected]> wrote: > >> They would need container images though to use any of those charts or >> compose files. The release cannot be source only and then add images >> that are somehow part of the release, but not part of what is voted >> on. That would defeat a primary function of the release: to audit and >> verify what users will actually receive. The release should contain >> everything a new user of Texera would use to get started. >> >> Take a look at this Flink operator release candidate for an example of >> an Apache release that contains a container as a binary artifact: >> https://lists.apache.org/thread/r21rdl7x8bdfxn59f5tgbbqhf3cks60s >> >> On Wed, Feb 11, 2026 at 12:44 AM Jiadong Bai <[email protected]> wrote: >> > >> > Thanks for the clarification. The current source tarball already >> includes >> > all the orchestration files (docker-compose, Kubernetes Helm charts, >> etc.), >> > so users can deploy using these files without compiling from the source >> > code. >> > >> > Would it be sufficient to keep the current source-only tarball for the >> > release, and then publish the Docker images once the release vote passes >> > and is officially published? >> > >> > Thanks, >> > Jiadong >> > >> > On Tue, Feb 10, 2026 at 11:50 PM Ian Maxon <[email protected]> wrote: >> > >> > > The binaries need not be in the form of .deb files or something like >> > > that. A container image can be one, AFAIK. That is why I was puzzled- >> > > I saw lots of scripts and such for orchestrating and deploying the >> > > service, but they would be hard to use if the user had to first >> > > compile everything and then deploy it to a private tag or registry or >> > > something. >> > > I think having the release in a form that makes it easiest for users >> > > to actually use, is definitely something to aim for. >> > > >> > > On Tue, Feb 10, 2026 at 9:22 PM Jiadong Bai <[email protected]> >> wrote: >> > > > >> > > > 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://urldefense.com/v3/__https://hub.docker.com/u/apache?page=1&search=texera__;!!CzAuKJ42GuquVTTmVmPViYEvSg!JWC1i6LlFoRSyIHpCFIxXKPfxbjPHxZzd1wgYW_ntPAh5zBk7aa3S_q9NoE5RXbmxdDNHiBTALcqyp2i$ >> > > > > 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://urldefense.com/v3/__https://github.com/apache/texera/tree/v1.1.0-incubating-rc2__;!!CzAuKJ42GuquVTTmVmPViYEvSg!JWC1i6LlFoRSyIHpCFIxXKPfxbjPHxZzd1wgYW_ntPAh5zBk7aa3S_q9NoE5RXbmxdDNHiBTAA7lU6XM$ >> > > . >> > > > > > >> > > > > > The RC is a source-code-only tarball built via an automated >> GitHub >> > > > > Actions >> > > > > > workflow >> > > > > > < >> > > > > >> > > >> https://urldefense.com/v3/__https://github.com/apache/texera/blob/v1.1.0-incubating-rc2/.github/workflows/create-release-candidate.yml__;!!CzAuKJ42GuquVTTmVmPViYEvSg!JWC1i6LlFoRSyIHpCFIxXKPfxbjPHxZzd1wgYW_ntPAh5zBk7aa3S_q9NoE5RXbmxdDNHiBTAOtOcbr_$ >> > > > > >. >> > > > > > 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://urldefense.com/v3/__https://dist.apache.org/repos/dist/dev/incubator/texera/1.1.0-incubating-RC2/__;!!CzAuKJ42GuquVTTmVmPViYEvSg!JWC1i6LlFoRSyIHpCFIxXKPfxbjPHxZzd1wgYW_ntPAh5zBk7aa3S_q9NoE5RXbmxdDNHiBTAKy3zw4a$ >> > > > > > > > >> > > > > > > > == Git Tag == >> > > > > > > > >> > > >> https://urldefense.com/v3/__https://github.com/apache/texera/releases/tag/v1.1.0-incubating__;!!CzAuKJ42GuquVTTmVmPViYEvSg!JWC1i6LlFoRSyIHpCFIxXKPfxbjPHxZzd1wgYW_ntPAh5zBk7aa3S_q9NoE5RXbmxdDNHiBTADV6GQ1g$ >> > > > > > > > Commit: 7048ce340a2557ff3810206c8583c3e775972746 >> > > > > > > > >> > > > > > > > == Keys == >> > > > > > > > KEYS file: >> > > >> https://urldefense.com/v3/__https://downloads.apache.org/incubator/texera/KEYS__;!!CzAuKJ42GuquVTTmVmPViYEvSg!JWC1i6LlFoRSyIHpCFIxXKPfxbjPHxZzd1wgYW_ntPAh5zBk7aa3S_q9NoE5RXbmxdDNHiBTAJw6GvmI$ >> > > > > > > > >> > > > > > > > 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 >> > > > > > > >> > > > > >> > > >> >
