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
