adutra commented on code in PR #3874: URL: https://github.com/apache/polaris/pull/3874#discussion_r2846561279
########## site/content/community/release-guides/_index.md: ########## @@ -43,3 +43,37 @@ 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. +Generally, they manage the technical, legal, and procedural steps, including code freezing, signing artifacts, and coordinating voting, to ensure compliance with the [Apache Software Foundation policies](#prerequisites). + +### Key Responsibilities + +* **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**: + Ensuring all code complies with Apache legal, licensing, and security standards. +* **Technical Execution**: + Creating release candidates, tagging source code, signing artifacts using GnuPG, and publishing to ASF distribution channels. Review Comment: Is "using GnuPG" a requirement? ########## site/content/community/release-guides/_index.md: ########## @@ -43,3 +43,37 @@ 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. +Generally, they manage the technical, legal, and procedural steps, including code freezing, signing artifacts, and coordinating voting, to ensure compliance with the [Apache Software Foundation policies](#prerequisites). + +### Key Responsibilities + +* **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**: + Ensuring all code complies with Apache legal, licensing, and security standards. +* **Technical Execution**: + Creating release candidates, tagging source code, signing artifacts using GnuPG, and publishing to ASF distribution channels. +* **Documentation**: + Preparing release notes, changelogs, and deployment documentation. + +### 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 (e.g., in the PMC) and ensure the release is officially approved before release. Review Comment: What do you mean by `(e.g., in the PMC)` ? -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
