Hi Xuan,

I’d be interested in volunteering as the Release Manager for the v1.3
release line.

Best,
Meng

On Sat, Aug 22, 2026 at 8:27 PM Xuan Gu <[email protected]> wrote:

> Hi all,
>
> The v1.3 release branch is currently scheduled to be cut on September 1,
> 2026, and we would like to identify a Release Manager before then. I’d like
> to call for volunteers to serve as the Release Manager for the Apache
> Texera v1.3 release line.
>
> The Release Manager will help shepherd the v1.3 release line, including the
> initial v1.3.0-incubating release and follow-up patch releases in the same
> line, such as v1.3.1-incubating, v1.3.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 are 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
>
> A more detailed Release Manager guide is also available for reference.
>
> If you are interested in serving as the Release Manager for the v1.3
> release line, please reply to this thread at your earliest convenience.
>
> 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.
>
> Thanks,
> Xuan
>

Reply via email to