jbonofre commented on code in PR #3874: URL: https://github.com/apache/polaris/pull/3874#discussion_r2846586213
########## 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). Review Comment: I think the link is broken to prerequisites. Also, release managers do the mechanical work; but the PMC in general, and the PMC chair in particular (as an officer of the Foundation), remains responsible for compliance with ASF requirements. So I would not mention release manager manages legal aspects, etc. The release manager "just" does the mechanical work, nothing else. ########## 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). Review Comment: Same comment as before, the release coordination/compliance and safety are not release manager "only" responsability. It's community driven on the mailing list. The technical execution/documentation is actually the core responsability of the release manager. -- 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]
