Update release manual
diff --git a/_docs/08-release-manual.md b/_docs/08-release-manual.md
index 8102588..0d6479e 100644
--- a/_docs/08-release-manual.md
+++ b/_docs/08-release-manual.md
@@ -112,7 +112,7 @@
* Make sure that all the unit tests can pass via `mvn clean install`.
* Make sure that all the integration tests can pass via `mvn clean test -Pit-test`.
-After the successful building, remember to sign the artifact, and copy them to the svn repository, you could refer to [svn repository](https://dist.apache.org/repos/dist/release/rocketmq/4.2.0) .
+After the successful building, remember to sign the artifact(GPG and SHA512 signatures are required), and copy them to the svn repository, you could refer to [svn repository](https://dist.apache.org/repos/dist/release/rocketmq/4.2.0) .
## 4. Validate the Release Candidate
@@ -139,9 +139,9 @@
#### 4.3 verify tools
-Please follow the steps below to verify the checksums and PGP signatures:
+Please follow the steps below to verify the checksums and GPG signatures:
-1. Download the release artifacts, PGP signature file, MD5/SHA hash files.
+1. Download the release artifacts, GPG signature file, SHA512 hash files.
2. On unix platforms the following command can be executed:
```shell
@@ -154,7 +154,7 @@
or
```shell
- gpg --verify rocketmq-all-%version-number%-source-release.zip.asc rocketmq-all-%version-number%-source-release.zip
+ gpg --verify rocketmq-all-%version-number%-source-release.zip.asc rocketmq-all-%version-number%-bin-release.zip
```
Check the output to ensure it only contains good signatures:
@@ -162,10 +162,11 @@
gpg: Good signature from ... gpg: Signature made ...
```
-3. Compare MD5, SHA hash generated by the below command with the downloaded hash files.
+3. Compare SHA512 hash generated by the below command with the downloaded hash files.
```shell
gpg --print-mds rocketmq-all-%version-number%-source-release.zip
+ gpg --print-mds rocketmq-all-%version-number%-bin-release.zip
```
## 5. Release the Staging Artifacts
