This is an automated email from the ASF dual-hosted git repository.
dinglei pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/rocketmq-site.git
The following commit(s) were added to refs/heads/master by this push:
new 538fa7a Update release manual
538fa7a is described below
commit 538fa7a8e9ad631bb441fce638bcf97f8fb73418
Author: ShannonDing <[email protected]>
AuthorDate: Thu Mar 28 20:53:20 2019 +0800
Update release manual
---
_docs/08-release-manual.md | 10 +++++-----
1 file changed, 5 insertions(+), 5 deletions(-)
diff --git a/_docs/08-release-manual.md b/_docs/08-release-manual.md
index 0d6479e..3bb0f51 100644
--- a/_docs/08-release-manual.md
+++ b/_docs/08-release-manual.md
@@ -112,7 +112,7 @@ Be aware of the os version, for some dependency is os
sensitive, such as netty t
* 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(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) .
+After the successful building, remember to sign the artifact(PGP 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
@@ -123,7 +123,7 @@ After the successful building, remember to sign the
artifact(GPG and SHA512 sign
* check LICENSE, should be Apache V2
* check NOTICE, should have a notice for third-party dependency if necessary
* extract the zip and check if the binary version is correct
- * verify the asc(pgp sign), md5, sha1
+ * verify the asc(PGP sign), SHA512
* start nameserver and broker according to the quick-start
* run clusterList command to see if the version is correct
* make sure there is no nohup.out in the binary files
@@ -133,15 +133,15 @@ After the successful building, remember to sign the
artifact(GPG and SHA512 sign
* check LICENSE, should be Apache V2
* check NOTICE, should have a notice for third-party dependency if necessary
* extract the zip and check if the source version is correct
- * verify the asc(pgp sign), md5, sha1
+ * verify the asc(PGP sign),SHA512
* build the source, start nameserver and broker according to the quick-start
* run clusterList command to see if the version is correct
#### 4.3 verify tools
-Please follow the steps below to verify the checksums and GPG signatures:
+Please follow the steps below to verify the checksums and PGP signatures:
-1. Download the release artifacts, GPG signature file, SHA512 hash files.
+1. Download the release artifacts, PGP signature file, SHA512 hash files.
2. On unix platforms the following command can be executed:
```shell
