Dear Community & Teaclave PMC,

As part of growing the Apache Teaclave community, we strongly encourage
existing committers to take on the Release Manager (RM) role, which is an
important step toward becoming a PMC member.

However, since Teaclave has become a Top-Level Project (TLP), the release
process now requires PMC authorization for certain actions. According to
the ASF release publishing guidelines[1], the following operations are
currently restricted for committers who are not PMC members:
  (1) Before calling a release vote: Updating the KEYS file to add or
modify GPG keys used to verify the authenticity of release artifacts.
  (2) After a release vote passes: Moving PMC-approved release artifacts
from dist/dev to dist/release.

Action (2) is explicitly covered by a successful PMC release vote and can
be easily handled with the assistance of any PMC member.

To properly address Action (1) in advance and enable smoother future
releases, I am calling this vote to add the GPG key of Teaclave committer
ivila (Apache ID: ivila, GitHub handle: ivila), who is willing to take on
the Release Manager role, to the KEYS file under PMC approval, for use in
future Apache Teaclave releases.

Please vote on adding ivila’s GPG key to the KEYS file:
- +1 Approve
- 0 Neutral
- -1 Disapprove (please provide a reason)

This vote will remain open for 72 hours. If there are no objections, I will
proceed accordingly after the vote closes.

Thanks everyone for your time and support.

Best regards,
Zhaofeng Chen

[1] https://infra.apache.org/release-publishing.html#releasemanager

Reply via email to