gaborkaszab commented on code in PR #187: URL: https://github.com/apache/iceberg-docs/pull/187#discussion_r1152908927
########## landing-page/content/common/how-to-release.md: ########## @@ -21,6 +21,18 @@ disableSidebar: true - limitations under the License. --> +## Introduction + +This page walks you through the release process of the Iceberg project. [Here](https://www.apache.org/legal/release-policy.html) you can read about the release process in general for an Apache project. + +Decisions about releases are made by three groups: + +* Release Manager: Does the work of creating the release, signing it, counting [votes](/how-to-release/#voting), announcing the release and so on. Requires the assistance of a committer for some steps. +* The community: Performs the discussion of whether it is the right time to create a release and what that release should contain. The community can also cast non-binding votes on the release. +* PMC: Gives binding votes on the release. Review Comment: Also non-binding votes are mentioned here. The basic idea for this section was to list the roles related to the release process. The community in general can give non-binding votes while the PMC can give binding ones. Yes, this is also mentioned in L221 but please note, that it is a sample text for the email to be sent out for voting. So in my opinion there is a need to mention the types of voting here and on L221 as well. -- 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: issues-unsubscr...@iceberg.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: issues-unsubscr...@iceberg.apache.org For additional commands, e-mail: issues-h...@iceberg.apache.org
