[DISCUSS] Release Managers for Apache Maka 0.2.0

[Astro-Han]

We do not have a source RC yet, but there is one part of the release that we should not leave until the end: macOS and Windows code-signing access.

The Infra account setup may take a week or two. We would like to start it now while the source-release work continues.

Could one or two Maka committers volunteer as Release Managers for 0.2.0?

We need help with two platform-signing paths:

• macOS: join the ASF Apple Developer Program using an Apple ID created with an @apache.org address, then help verify signing, notarization and stapling.
• Windows: obtain an individual ssl.com eSigner account, complete the OTP setup, then help sign and verify the release candidates.

One person can cover both, or we can split them between two people. A backup would also be useful. These are personal accounts and cannot be shared.

If you are willing to help, please reply with:

• your Apache ID;
• macOS, Windows, or both;
• whether you would prefer to be the primary or backup Release Manager; and
• whether you expect to have time for the account setup and release work over the next couple of weeks.

This does not mean handling the whole release alone. The rest of us will continue preparing and reviewing the artifacts, checks and release materials. We mainly need named people who can complete the personal account steps and perform the final platform signing.

Once we have volunteers, we will record the assignment on dev@maka.apache.org and prepare two INFRA Jira requests:

1. ASF Apple Developer Program membership;
2. ssl.com eSigner access.

Related work:

• First-release tracker: [TRACKING] Apache Maka 0.2.0-incubating source release #2974
• Desktop release gate: release: publish ASF-compliant Desktop convenience artifacts #3276
• Code-signing prerequisite: infra: obtain ASF code signing identities for Desktop artifacts #3414
• ASF Apple Developer Program: https://infra.apache.org/apple-dev-program.html
• ASF code-signing access: https://infra.apache.org/code-signing-access.html

Drafted with help from OpenAI Codex. I reviewed the final text and take responsibility for posting it.

[yihanzhu]

I’m not currently a Maka committer, so I can’t hold the personal ASF signing credentials. I’d still be happy to help with the non-credential parts if needed :)

[M4n5ter]

English

I volunteer as a backup Release Manager for both macOS and Windows for Apache Maka 0.2.0.

• Apache ID: wyt
• Platforms: macOS and Windows
• Role: Backup Release Manager
• Availability: I expect to have time for the account setup and release work over the next few weeks.

中文

我愿意担任 Apache Maka 0.2.0 的 macOS 和 Windows 双平台 Backup Release Manager。

• Apache ID：wyt
• 平台：macOS 和 Windows
• 角色：Backup Release Manager
• 时间：未来几周可以投入账号配置和发布工作。

[Astro-Han]

I can volunteer as the primary Release Manager for Apache Maka 0.2.0 and cover both the macOS and Windows signing setup.

• Apache ID: astrohan
• Scope: source release, macOS, and Windows
• Role: primary
• Availability: I expect to have time for the account setup and release work over the next couple of weeks.

I would also like to suggest @M4n5ter (Apache ID: wyt) as the backup Release Manager, subject to his confirmation. He has been closely involved in the release work, including much of the npm release preparation.

Once the assignment is confirmed, I can file the Apple Developer Program and eSigner INFRA requests.

[Astro-Han]

English

Resolved: release managers are named and the follow-up work has moved on

This discussion asked for Release Manager volunteers for Apache Maka 0.2.0, specifically to start the platform code-signing account setup early. That is done.

Release Managers for Apache Maka 0.2.0:

• Primary: Yuhan Lei, Apache ID astrohan — source release, macOS, and Windows
• Backup: Yongtao Wang, Apache ID wyt — macOS and Windows

Both assignments are recorded in the two INFRA requests this discussion said we would file:

• INFRA-28301 — add both release managers to the ASF Apple Developer Program. Both have created Apple IDs on their @apache.org addresses. Status is Waiting for Infra as of 2026-08-30.
• INFRA-28302 — provision individual ssl.com eSigner accounts for both. Accepted and queued as of 2026-08-27.

The source-release signing key is published in the podling KEYS file at https://dist.apache.org/repos/dist/dev/incubator/maka/KEYS.

Thanks to everyone who replied, including those who offered help on the non-credential parts.

Further code-signing work continues on #3414, and the source release itself on #2974. Closing this as resolved.

简体中文

已解决：Release Manager 已确定，后续工作已转入对应 issue

本讨论是为 Apache Maka 0.2.0 征集 Release Manager，重点是尽早启动平台代码签名的账号配置。这件事已经完成。

Apache Maka 0.2.0 的 Release Manager：

• 正：Yuhan Lei，Apache ID astrohan —— 源码发布、macOS、Windows
• 备：Yongtao Wang，Apache ID wyt —— macOS 与 Windows

两项任命都已记录在本讨论中提到要提交的两张 INFRA 工单里：

• INFRA-28301 —— 将两位 Release Manager 加入 ASF Apple Developer Program。两人都已用各自的 @apache.org 邮箱创建 Apple ID。截至 2026-08-30 状态为 Waiting for Infra。
• INFRA-28302 —— 为两人各自开通 ssl.com eSigner 账号。截至 2026-08-27 已受理并排队。

源码发布的签名密钥已发布在 podling KEYS 文件：https://dist.apache.org/repos/dist/dev/incubator/maka/KEYS。

感谢所有回复的人，也包括表示愿意协助非凭据部分工作的朋友。

后续代码签名工作在 #3414 继续，源码发布本身在 #2974。本讨论以已解决关闭。

---

Drafted with help from Claude Code. I reviewed the final text and take responsibility for posting it.