Hi all, Following the adoption of the Release Manager role definition, I would like to call for volunteers to serve as the Release Manager for the Apache Texera v1.2 release line.
The Release Manager will help shepherd the v1.2 release line, including the initial v1.2.0-incubating release and follow-up patch releases in the same line, such as v1.2.1-incubating, v1.2.2-incubating, and so on. This is a coordination and execution role. The Release Manager does not have special authority to approve a release alone. The release still follows the normal Apache voting process, including PPMC approval and IPMC approval where required during incubation. The Release Manager must be a Texera committer. The expected responsibilities include but not limited to: - Coordinating the release timeline, branch cut and release candidate preparation - Preparing release artifacts, source packages, tags, checksums, and signatures - Coordinating the release vote and the incubation release vote - Publishing approved release artifacts with help from PPMC members when needed - Updating website/download links, documentation, and announcements as needed - Keeping the community informed about release status, blockers, and next steps * We are preparing a more detailed doc for Release Manager to follow. If you are interested in serving as the Release Manager for the v1.2 release line, please reply to this thread at your earliest convenience. Since the v1.2 release branch is scheduled to be cut on June 1, 2026, which is today, we need to identify a Release Manager as soon as possible. To keep the process moving, once we have enough volunteers, we may start coordinating to select one as the Release Manager. If there are no volunteers, the PPMC may encourage, nominate, or appoint a Release Manager when needed. Best regards, Yicong Huang
