(amoro-site) branch version_bump_when_releasing updated (50749d5 -> a7e9484)

[kl...@apache.org]

This is an automated email from the ASF dual-hosted git repository.

klion26 pushed a change to branch version_bump_when_releasing
in repository https://gitbox.apache.org/repos/asf/amoro-site.git


 discard 50749d5  [AMORO-SITE-63] Enhance the version bump logic when releasing
     new a7e9484  [AMORO-SITE-63] Enhance the version bump logic when releasing

This update added new revisions after undoing existing revisions.
That is to say, some revisions that were in the old version of the
branch are not in the new version.  This situation occurs
when a user --force pushes a change and generates a repository
containing something like this:

 * -- * -- B -- O -- O -- O   (50749d5)
            \
             N -- N -- N   refs/heads/version_bump_when_releasing (a7e9484)

You should already have received notification emails for all of the O
revisions, and so the following emails describe only the N revisions
from the common base, B.

Any revisions marked "omit" are not gone; other references still
refer to them.  Any revisions marked "discard" are gone forever.

The 1 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails.  The revisions
listed as "add" were already present in the repository and have only
been added to this reference.


Summary of changes:
 amoro-site/content/community/release-guide.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

(amoro-site) 01/01: [AMORO-SITE-63] Enhance the version bump logic when releasing

[kl...@apache.org]

This is an automated email from the ASF dual-hosted git repository.

klion26 pushed a commit to branch version_bump_when_releasing
in repository https://gitbox.apache.org/repos/asf/amoro-site.git

commit a7e94840f42729b2e7d97f1ef9b1dac3318bf560
Author: klion26 <qc...@gmail.com>
AuthorDate: Thu Sep 25 10:53:07 2025 +0800

    [AMORO-SITE-63] Enhance the version bump logic when releasing
---
 amoro-site/content/community/release-guide.md | 14 ++++++++++----
 1 file changed, 10 insertions(+), 4 deletions(-)

diff --git a/amoro-site/content/community/release-guide.md b/amoro-site/content/community/release-guide.md
index f9f02e0..162c024 100644
--- a/amoro-site/content/community/release-guide.md
+++ b/amoro-site/content/community/release-guide.md
@@ -232,22 +232,28 @@ $ mvn --encrypt-password <apache password>
 ## Build release
 
 ### Cut the release branch
+> The version of Apache Amoro follows the [Semantic Versioning](https://semver.org/), which looks like `{major}.{mior}.{patch}`
 
-Cut the release branch if it is not created in the Apache remote repository, if it already exists, check it out and pull the latest changes.
+Cut a branch for the `minor` version if it is not created in the Apache remote repository, if it already exists, check it out and pull the latest changes.
 
 ```shell
 $ cd ${AMORO_SOURCE_HOME}
 
-# Cut the release branch if it is not created 
+# Cut the release branch if it is not created, then push to the remote 
 $ git checkout -b 0.8.x
+$ git push apache 0.8.x
 
 # Or check it out and pull the latest changes if it is created
 $ git checkout 0.8.x
 $ git pull apache 0.8.x
 ```
 
-Change the project version to the release version in the `tools/change-version.sh`:
+Checkout a `patch` branch using the following command
+```
+$ git checkout -b 0.8.0-branch
+```
 
+Update the version in the new branch using the tool `tools/change-version.sh`:
 ```bash
 OLD="0.8-SNAPSHOT"
 NEW="0.8.0-incubating"
@@ -270,7 +276,7 @@ $ bash change-version.sh
 $ cd ..
 $ git add *
 $ git commit -m "Change project version to 0.8.0-incubating"
-$ git push apache 0.8.x
+$ git push apache 0.8.0-branch
 ```
 
 ### Create the release tag