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

panjuan pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/shardingsphere.git


The following commit(s) were added to refs/heads/master by this push:
     new 9f98cc3  refine elasticjob release guide (#6461)
9f98cc3 is described below

commit 9f98cc380332a56ddd2514f255a68bea4ce66265
Author: Zhang Yonglun <[email protected]>
AuthorDate: Mon Jul 27 16:35:05 2020 +0800

    refine elasticjob release guide (#6461)
---
 docs/community/content/contribute/release-elasticjob.cn.md | 8 +++++++-
 docs/community/content/contribute/release-elasticjob.en.md | 8 +++++++-
 2 files changed, 14 insertions(+), 2 deletions(-)

diff --git a/docs/community/content/contribute/release-elasticjob.cn.md 
b/docs/community/content/contribute/release-elasticjob.cn.md
index 8de21b4..5cc46a2 100644
--- a/docs/community/content/contribute/release-elasticjob.cn.md
+++ b/docs/community/content/contribute/release-elasticjob.cn.md
@@ -146,6 +146,8 @@ cp -f 
~/elasticjob/elasticjob-distribution/elasticjob-lite-distribution/target/*
 cp -f 
~/elasticjob/elasticjob-distribution/elasticjob-lite-distribution/target/*.tar.gz.asc
 ~/ss_svn/dev/shardingsphere/elasticjob-${RELEASE.VERSION}
 cp -f 
~/elasticjob/elasticjob-distribution/elasticjob-cloud-distribution/target/*.tar.gz
 ~/ss_svn/dev/shardingsphere/elasticjob-${RELEASE.VERSION}
 cp -f 
~/elasticjob/elasticjob-distribution/elasticjob-cloud-distribution/target/*.tar.gz.asc
 ~/ss_svn/dev/shardingsphere/elasticjob-${RELEASE.VERSION}
+cp -f 
~/elasticjob/elasticjob-distribution/elasticjob-cloud-scheduler-distribution/target/*.tar.gz
 ~/ss_svn/dev/shardingsphere/elasticjob-${RELEASE.VERSION}
+cp -f 
~/elasticjob/elasticjob-distribution/elasticjob-cloud-scheduler-distribution/target/*.tar.gz.asc
 ~/ss_svn/dev/shardingsphere/elasticjob-${RELEASE.VERSION}
 ```
 
 ### 生成文件签名
@@ -154,6 +156,7 @@ cp -f 
~/elasticjob/elasticjob-distribution/elasticjob-cloud-distribution/target/
 shasum -a 512 apache-shardingsphere-elasticjob-${RELEASE.VERSION}-src.zip >> 
apache-shardingsphere-elasticjob-${RELEASE.VERSION}-src.zip.sha512
 shasum -b -a 512 
apache-shardingsphere-elasticjob-${RELEASE.VERSION}-lite-bin.tar.gz >> 
apache-shardingsphere-elasticjob-${RELEASE.VERSION}-lite-bin.tar.gz.sha512
 shasum -b -a 512 
apache-shardingsphere-elasticjob-${RELEASE.VERSION}-cloud-bin.tar.gz >> 
apache-shardingsphere-elasticjob-${RELEASE.VERSION}-cloud-bin.tar.gz.sha512
+shasum -b -a 512 
apache-shardingsphere-elasticjob-${RELEASE.VERSION}-cloud-scheduler-bin.tar.gz 
>> 
apache-shardingsphere-elasticjob-${RELEASE.VERSION}-cloud-scheduler-bin.tar.gz.sha512
 ```
 
 ### 提交Apache SVN
@@ -171,6 +174,7 @@ svn --username=${APACHE LDAP 用户名} commit -m "release 
elasticjob-${RELEASE.
 shasum -c apache-shardingsphere-elasticjob-${RELEASE.VERSION}-src.zip.sha512
 shasum -c 
apache-shardingsphere-elasticjob-${RELEASE.VERSION}-lite-bin.tar.gz.sha512
 shasum -c 
apache-shardingsphere-elasticjob-${RELEASE.VERSION}-cloud-bin.tar.gz.sha512
+shasum -c 
apache-shardingsphere-elasticjob-${RELEASE.VERSION}-cloud-scheduler-bin.tar.gz.sha512
 ```
 
 ### 检查gpg签名
@@ -204,6 +208,7 @@ Your decision? 5
 gpg --verify apache-shardingsphere-elasticjob-${RELEASE.VERSION}-src.zip.asc 
apache-shardingsphere-elasticjob-${RELEASE.VERSION}-src.zip
 gpg --verify 
apache-shardingsphere-elasticjob-${RELEASE.VERSION}-lite-bin.tar.gz.asc 
apache-shardingsphere-elasticjob-${RELEASE.VERSION}-lite-bin.tar.gz
 gpg --verify 
apache-shardingsphere-elasticjob-${RELEASE.VERSION}-cloud-bin.tar.gz.asc 
apache-shardingsphere-elasticjob-${RELEASE.VERSION}-cloud-bin.tar.gz
+gpg --verify 
apache-shardingsphere-elasticjob-${RELEASE.VERSION}-cloud-scheduler-bin.tar.gz.asc
 apache-shardingsphere-elasticjob-${RELEASE.VERSION}-cloud-scheduler-bin.tar.gz
 ```
 
 ### 检查发布文件内容
@@ -229,7 +234,8 @@ diff -r 
apache-shardingsphere-elasticjob-${RELEASE.VERSION}-src-release sharding
 
 #### 检查二进制包的文件内容
 
-解压缩`apache-shardingsphere-elasticjob-${RELEASE.VERSION}-lite-bin.tar.gz`和`apache-shardingsphere-elasticjob-${RELEASE.VERSION}-cloud-bin.tar.gz`
+解压缩`apache-shardingsphere-elasticjob-${RELEASE.VERSION}-lite-bin.tar.gz`,`apache-shardingsphere-elasticjob-${RELEASE.VERSION}-cloud-bin.tar.gz`
+和`apache-shardingsphere-elasticjob-${RELEASE.VERSION}-cloud-scheduler-bin.tar.gz`
 进行如下检查:
 
 - 存在`LICENSE`和`NOTICE`文件
diff --git a/docs/community/content/contribute/release-elasticjob.en.md 
b/docs/community/content/contribute/release-elasticjob.en.md
index 70a4ebe..74645b6 100644
--- a/docs/community/content/contribute/release-elasticjob.en.md
+++ b/docs/community/content/contribute/release-elasticjob.en.md
@@ -147,6 +147,8 @@ cp -f 
~/elasticjob/elasticjob-distribution/elasticjob-lite-distribution/target/*
 cp -f 
~/elasticjob/elasticjob-distribution/elasticjob-lite-distribution/target/*.tar.gz.asc
 ~/ss_svn/dev/shardingsphere/elasticjob-${RELEASE.VERSION}
 cp -f 
~/elasticjob/elasticjob-distribution/elasticjob-cloud-distribution/target/*.tar.gz
 ~/ss_svn/dev/shardingsphere/elasticjob-${RELEASE.VERSION}
 cp -f 
~/elasticjob/elasticjob-distribution/elasticjob-cloud-distribution/target/*.tar.gz.asc
 ~/ss_svn/dev/shardingsphere/elasticjob-${RELEASE.VERSION}
+cp -f 
~/elasticjob/elasticjob-distribution/elasticjob-cloud-scheduler-distribution/target/*.tar.gz
 ~/ss_svn/dev/shardingsphere/elasticjob-${RELEASE.VERSION}
+cp -f 
~/elasticjob/elasticjob-distribution/elasticjob-cloud-scheduler-distribution/target/*.tar.gz.asc
 ~/ss_svn/dev/shardingsphere/elasticjob-${RELEASE.VERSION}
 ```
 
 ### Generate sign files
@@ -155,6 +157,7 @@ cp -f 
~/elasticjob/elasticjob-distribution/elasticjob-cloud-distribution/target/
 shasum -a 512 apache-shardingsphere-elasticjob-${RELEASE.VERSION}-src.zip >> 
apache-shardingsphere-elasticjob-${RELEASE.VERSION}-src.zip.sha512
 shasum -b -a 512 
apache-shardingsphere-elasticjob-${RELEASE.VERSION}-lite-bin.tar.gz >> 
apache-shardingsphere-elasticjob-${RELEASE.VERSION}-lite-bin.tar.gz.sha512
 shasum -b -a 512 
apache-shardingsphere-elasticjob-${RELEASE.VERSION}-cloud-bin.tar.gz >> 
apache-shardingsphere-elasticjob-${RELEASE.VERSION}-cloud-bin.tar.gz.sha512
+shasum -b -a 512 
apache-shardingsphere-elasticjob-${RELEASE.VERSION}-cloud-scheduler-bin.tar.gz 
>> 
apache-shardingsphere-elasticjob-${RELEASE.VERSION}-cloud-scheduler-bin.tar.gz.sha512
 ```
 
 ### Commit to Apache SVN
@@ -172,6 +175,7 @@ svn --username=${APACHE LDAP username} commit -m "release 
elasticjob-${RELEASE.V
 shasum -c apache-shardingsphere-elasticjob-${RELEASE.VERSION}-src.zip.sha512
 shasum -c 
apache-shardingsphere-elasticjob-${RELEASE.VERSION}-lite-bin.tar.gz.sha512
 shasum -c 
apache-shardingsphere-elasticjob-${RELEASE.VERSION}-cloud-bin.tar.gz.sha512
+shasum -c 
apache-shardingsphere-elasticjob-${RELEASE.VERSION}-cloud-scheduler-bin.tar.gz.sha512
 ```
 
 ### Check gpg Signature
@@ -206,6 +210,7 @@ Then, check the gpg signature.
 gpg --verify apache-shardingsphere-elasticjob-${RELEASE.VERSION}-src.zip.asc 
apache-shardingsphere-elasticjob-${RELEASE.VERSION}-src.zip
 gpg --verify 
apache-shardingsphere-elasticjob-${RELEASE.VERSION}-lite-bin.tar.gz.asc 
apache-shardingsphere-elasticjob-${RELEASE.VERSION}-lite-bin.tar.gz
 gpg --verify 
apache-shardingsphere-elasticjob-${RELEASE.VERSION}-cloud-bin.tar.gz.asc 
apache-shardingsphere-elasticjob-${RELEASE.VERSION}-cloud-bin.tar.gz
+gpg --verify 
apache-shardingsphere-elasticjob-${RELEASE.VERSION}-cloud-scheduler-bin.tar.gz.asc
 apache-shardingsphere-elasticjob-${RELEASE.VERSION}-cloud-scheduler-bin.tar.gz
 ```
 
 ### Check Released Files
@@ -231,7 +236,8 @@ diff -r 
apache-shardingsphere-elasticjob-${RELEASE.VERSION}-src-release sharding
 
 #### Check binary packages
 
-Decompress 
`apache-shardingsphere-elasticjob-${RELEASE.VERSION}-lite-bin.tar.gz` and 
`apache-shardingsphere-elasticjob-${RELEASE.VERSION}-cloud-bin.tar.gz`
+Decompress 
`apache-shardingsphere-elasticjob-${RELEASE.VERSION}-lite-bin.tar.gz`, 
`apache-shardingsphere-elasticjob-${RELEASE.VERSION}-cloud-bin.tar.gz`
+and 
`apache-shardingsphere-elasticjob-${RELEASE.VERSION}-cloud-scheduler-bin.tar.gz`
 to check the following items:
 
 *   `LICENSE` and `NOTICE` files exist

Reply via email to