rocketmq-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject [rocketmq-site] branch master updated: Update Release manual
Date Thu, 14 Mar 2019 13:54:52 GMT
This is an automated email from the ASF dual-hosted git repository.

dinglei pushed a commit to branch master
in repository

The following commit(s) were added to refs/heads/master by this push:
     new 6528606  Update Release manual
6528606 is described below

commit 6528606b062ea2d76f517748d955b7e4102f5410
Author: ShannonDing <>
AuthorDate: Thu Mar 14 21:54:06 2019 +0800

    Update Release manual
 _docs/ | 20 +++++++++++++-------
 1 file changed, 13 insertions(+), 7 deletions(-)

diff --git a/_docs/ b/_docs/
index 6f60c76..8102588 100644
--- a/_docs/
+++ b/_docs/
@@ -79,11 +79,14 @@ Generate the release notes via [RocketMQ JIRA](
 ## 2.Build the Source Release Candidate
 In this process, you need to use maven release plugin to release the artifact to maven repository.
And also, copy them to the svn repository.
-#### 2.1 Release to the maven repository
-Firstly, checkout a new branch from the target branch(master or develop) with its name equal
to the release version, like `release-4.2.0`.
+#### 2.1 Check the MQVersion
+Remember to check the current version of MQVersion again, which should be equal to this released
version like `release-4.5.0`.
+ ```java
+  public static final int CURRENT_VERSION = Version.V4_5_0.ordinal();
+ ```
+#### 2.2 Release to the maven repository
+Make sure that you are in the develop branch, and Github PRs related to this release version
are merged.
 Perform the following to generate and stage the artifacts:
 1. `mvn clean release:clean`
@@ -94,9 +97,12 @@ Now, the candidate release artifacts can be found in the [Nexus staging
 **Tips:** If you are performing a source-only release, please remove all artifacts from the
staging repo besides the .zip file containing the source and the javadocs jar file. In the
Nexus GUI, you can right click on each artifact to be deleted and then select `Delete`.
-#### 2.2 Rollback and Retry
+#### 2.3 Checkout release branch
+Checkout a new branch from the target branch(master or develop) according to the release
tag with its name equal to the release version, like `release-4.5.0`.
+#### 2.4 Rollback and Retry
 If the staging process encounter problem, you may need to rollback:
-Delete the branch and tag created in 3.1 and then redo it.
+Delete the branch and tag created in 2.1 and then redo it.
 ## 3.Build the Binary Release Candidate
 Checkout the code to be released(must be the same as the source branch), and build the binary

View raw message