This is an automated email from the ASF dual-hosted git repository.
twice pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/kvrocks-website.git
The following commit(s) were added to refs/heads/main by this push:
new 0194a70 Add the preparation section in create-a-release.md (#155)
0194a70 is described below
commit 0194a70f80f6c47d648ea56371366f0a94d253ab
Author: Twice <[email protected]>
AuthorDate: Thu Sep 14 12:05:05 2023 +0900
Add the preparation section in create-a-release.md (#155)
* Add the preparation section in create-a-release.md
Refer to https://github.com/apache/kvrocks/discussions/1540.
* Update community/create-a-release.md
* Update community/create-a-release.md
* Update community/create-a-release.md
* Update community/create-a-release.md
* Update community/create-a-release.md
* Update community/create-a-release.md
* Update community/create-a-release.md
---
community/create-a-release.md | 50 +++++++++++++++++++++++++++++++++++++++++++
1 file changed, 50 insertions(+)
diff --git a/community/create-a-release.md b/community/create-a-release.md
index 5d24742..7083e80 100644
--- a/community/create-a-release.md
+++ b/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 from 3 days to one week. The Release
Manager will provide the deadline in the Release Proposal.
+
+During this period, newly merged bug fixes (especially those related to
security) in the unstable branch will be unconditionally cherry-picked into the
release branch,
+while other types of commits (especially new features) need to declare
specific reasons and reply to the Release Proposal to apply for cherry-picking
into the release branch. The final decision-making power lies with the Release
Manager.
+
+Patch Releases do not require this process.
+
+### Start the official release vote
+
+After the cherry-picking period, the Release Manager can proceed with the ASF
release process,
+which will be described in the following sections.
+
## Adding GPG KEY
This section is a brief from the [Cryptography with
OpenPGP](https://infra.apache.org/openpgp.html) guideline.
