This is an automated email from the ASF dual-hosted git repository.
snazy pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/polaris.git
The following commit(s) were added to refs/heads/main by this push:
new 36d478b7c6 Site: Add explicit release relevant ASF docs and policies
(#3874)
36d478b7c6 is described below
commit 36d478b7c6b7f512357999a20e8f838ce1c1a47c
Author: Robert Stupp <[email protected]>
AuthorDate: Thu Feb 26 13:19:11 2026 +0100
Site: Add explicit release relevant ASF docs and policies (#3874)
---
site/content/community/release-guides/_index.md | 37 +++++++++++++++++++++++++
1 file changed, 37 insertions(+)
diff --git a/site/content/community/release-guides/_index.md
b/site/content/community/release-guides/_index.md
index c9f3051651..6e4a44c891 100644
--- a/site/content/community/release-guides/_index.md
+++ b/site/content/community/release-guides/_index.md
@@ -43,3 +43,40 @@ The [manual release guide](manual-release-guide/) walks
through each step of cre
### Release Verification Guide
The [release verification guide](release-verification-guide/) provides
instructions for verifying an Apache Polaris release, like verifying checksums
and signatures, ensuring release artifacts integrity, ...
+
+## Release manager
+
+An Apache Release Manager is a designated project committer responsible for
shepherding a software release from community consensus to final distribution.
+They proactively drive the technical, legal, and procedural steps, including
code freezing, signing artifacts, and coordinating voting.
+All releases must comply with the [Release
Policy](https://www.apache.org/legal/release-policy.html)
+
+### Key Responsibilities
+
+Release managers do the mechanical work.
+
+* **Release Coordination**:
+ Planning timelines, managing the release lifecycle, and acting as the
liaison between the development community and the Project Management Committee
(PMC).
+* **Compliance and Safety**:
+ The goal is that all code complies with the ASF's legal, licensing, and
security standards.
+* **Technical Execution**:
+ Creating release candidates, tagging source code, signing artifacts, and
publishing to ASF distribution channels.
+* **Documentation**:
+ Preparing release notes, changelogs, and deployment documentation.
+
+### PMC and PMC Chair Responsibilities
+
+The PMC in general, and the PMC chair in particular (as an officer of the
Foundation), remain responsible for compliance with ASF requirements.
+
+### Role Requirements & Process:
+
+* **Committer Status**:
+ Committers on the project can typically act as release managers, ensuring
they have necessary access to the release infrastructure.
+* **Voluntary & Rotational**:
+ The role is voluntary, and we encourage rotating release managers to ensure
multiple community members are comfortable with the process.
+* **Voting Process**:
+ Release managers initiate the voting process and ensure the release is
officially approved before release.
+
+## Further information
+
+* [Release Creation Process](https://infra.apache.org/release-publishing.html)
+* [Assembling LICENSE and NOTICE
files](https://infra.apache.org/licensing-howto.html)
