[GitHub] [kvrocks-website] git-hulk commented on a diff in pull request #155: Add the preparation section in create-a-release.md

["git-hulk (via GitHub)" <gi...@apache.org>]

git-hulk commented on code in PR #155:
URL: https://github.com/apache/kvrocks-website/pull/155#discussion_r1322471258


##########
community/create-a-release.md:
##########
@@ -18,6 +18,56 @@ Please remember that publishing software has legal consequences. This guide comp
 * [Release Distribution Policy](https://infra.apache.org/release-distribution)
 * [Release Creation Process](https://infra.apache.org/release-publishing.html)
 
+## Preparation
+
+Before the ASF release process, in order to ensure that the version release is more open and formal, we have formulated the following process.
+For Feature Release, this preparation process usually takes about one week. 
+
+### Release Manager
+
+The first step to release a version is to select a Release Manager, who will drive the entire process.
+
+The Release Manager is usually chosen from PMC members or committers, based on voluntary registration.
+However, if there are other contributors who have a strong desire to participate in the release process and no PMC member objects,
+the Release Manager can be selected from among them.
+
+If no one has a strong willingness to take on the role of Release Manager and a release is needed at this time,
+a person should be selected from among the PMC members to assume this responsibility.
+
+### Propose a release
+
+Once the Release Manager is determined, the first step is to create a Release Proposal and make it public on the community's mailing list or GitHub Discussion.
+
+The Release Proposal should include at least the following:
+- Whether this release is a Feature Release or Patch Release (to be explained later)
+- The release version number
+- The commits added in this release compared to the previous version (please indicate whether rebase/cherry-pick is needed to remove commits from or add commits to the unstable branch)
+- A deadline for cherry-picking period (only applicable to Feature Releases)
+
+Where:
+Feature Release: Typically denoted as `X.Y.0`, this type of release introduces new features along with other enhancements and bug fixes.
+Patch Release: Usually represented as `X.Y.Z`, this type of release is based on the version `X.Y.0` and includes only bug-fix patches without any new features.
+
+### Create the release branch
+
+If no one objects to the Release Proposal in the previous step, the Release Manager can create a new branch `X.Y` (Patch Releases do not need to create a branch and can directly use the existing release branch `X.Y`).
+
+The Release Manager can determine the deadline for publicizing the Release Proposal on their own, which is usually one to three days.
+
+### The cherry-picking period
+
+For Feature Release, after creating a new branch, it will enter a cherry-picking period, usually lasting for 5 days to one week. The Release Manager will provide the deadline in the Release Proposal.

Review Comment:
   I prefer at least 72 hours which is aligned with ASF vote policy, so that the release managers don't need to keep different time windows in mind.



-- 
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-unsubscribe@kvrocks.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org