zhoujinsong commented on code in PR #64: URL: https://github.com/apache/amoro-site/pull/64#discussion_r2389998918
########## 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 Review Comment: Hi, I am not sure why we need a patch branch to change the project version. Can we change it in the release branch? -- 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]
