You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@shardingsphere.apache.org by du...@apache.org on 2022/12/10 08:04:28 UTC
[shardingsphere] branch master updated: Revise release guide of ShardingSphere on Cloud (#22787)
This is an automated email from the ASF dual-hosted git repository.
duanzhengqiang 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 e369e7546ce Revise release guide of ShardingSphere on Cloud (#22787)
e369e7546ce is described below
commit e369e7546ce8f442909d11a50e6fc6ce12c6e7e4
Author: 吴伟杰 <wu...@apache.org>
AuthorDate: Sat Dec 10 16:04:21 2022 +0800
Revise release guide of ShardingSphere on Cloud (#22787)
---
.../involved/release/shardingsphere-on-cloud.cn.md | 9 +++------
.../involved/release/shardingsphere-on-cloud.en.md | 16 +++++++---------
2 files changed, 10 insertions(+), 15 deletions(-)
diff --git a/docs/community/content/involved/release/shardingsphere-on-cloud.cn.md b/docs/community/content/involved/release/shardingsphere-on-cloud.cn.md
index 9fe79417d28..efefee8f97c 100644
--- a/docs/community/content/involved/release/shardingsphere-on-cloud.cn.md
+++ b/docs/community/content/involved/release/shardingsphere-on-cloud.cn.md
@@ -281,6 +281,7 @@ helm verify apache-shardingsphere-proxy-${RELEASE.VERSION}.tgz
- 所有第三方依赖的许可证都在 `LICENSE` 文件中声明；
- 依赖许可证的完整版全部在 `license` 目录；
- 如果依赖的是 Apache 许可证并且存在 `NOTICE` 文件，那么这些 `NOTICE` 文件也需要加入到版本的 `NOTICE` 文件中。
+
### 3. 检查仓库制品
添加仓库
@@ -290,7 +291,7 @@ helm repo add apache https://apache.github.io/shardingsphere-on-cloud
helm search repo apache
```
-可以查询到三个制品即为发布成功,`helm repo add` 和 `helm search repo -l` 会根据 index.yaml 中的校验值进行校验
+可以查询到三个制品即为发布成功，`helm repo add` 和 `helm search repo -l` 会根据 index.yaml 中的校验值进行校验
```shell
NAME CHART VERSION APP VERSION DESCRIPTION
@@ -362,13 +363,9 @@ Checklist for reference:
[ ] Checksums and PGP signatures are valid.
-[ ] Source code distributions have correct names matching the current release.
-
[ ] LICENSE and NOTICE files are correct for each ShardingSphere on Cloud repo.
[ ] All files have license headers if necessary.
-
-[ ] No compiled archives bundled in source archive.
```
2. 宣布投票结果模板：
@@ -425,7 +422,7 @@ Website: https://shardingsphere.apache.org/
ShardingSphere on Cloud Resources:
- Issue: https://github.com/apache/shardingsphere-on-cloud/issues/
- Mailing list: dev@shardingsphere.apache.org
-- Documents: https://shardingsphere.apache.org/document/current/
+- Documents: https://shardingsphere.apache.org/oncloud/current/en/overview/
diff --git a/docs/community/content/involved/release/shardingsphere-on-cloud.en.md b/docs/community/content/involved/release/shardingsphere-on-cloud.en.md
index 436c0318f3c..43919dc941d 100644
--- a/docs/community/content/involved/release/shardingsphere-on-cloud.en.md
+++ b/docs/community/content/involved/release/shardingsphere-on-cloud.en.md
@@ -18,7 +18,7 @@ and shall be classified according to the following labels:
### 2. Confirm issue list
-Open [Github Issues](https://github.com/apache/shardingsphere-on-cloud/issues)，filter the issue whose milestone is `${RELEASE.VERSION}` and status is open:
+Open [Github Issues](https://github.com/apache/shardingsphere-on-cloud/issues), filter the issue whose milestone is `${RELEASE.VERSION}` and status is open:
1. Close the completed issue;
1. For outstanding issues, communicate with the developer in charge. If this release is not affected, modify milestone to the next version;
@@ -151,7 +151,7 @@ Each server will automatically synchronize with one another, so it would be okay
### 1. Create Release Branch
-Suppose `ShardingSphere on Cloud` source codes downloaded from github is under `~/shardingsphere-on-cloud/` and the version to be released is `${RELEASE.VERSION}`。
+Suppose `ShardingSphere on Cloud` source codes downloaded from GitHub is under `~/shardingsphere-on-cloud/` and the version to be released is `${RELEASE.VERSION}`.
Create `${RELEASE.VERSION}-release` branch, where all the following operations are performed.
```shell
@@ -205,7 +205,8 @@ helm package --sign --key '${GPG 用户名}' --keyring ~/.gnupg/secring.gpg apac
helm package --sign --key '${GPG 用户名}' --keyring ~/.gnupg/secring.gpg apache-shardingsphere-operator-cluster-charts
helm package --sign --key '${GPG 用户名}' --keyring ~/.gnupg/secring.gpg apache-shardingsphere-proxy-charts
```
-### 5. 上传 charts，生成 index
+### 5. Upload charts and generate index
+
1. Upload the tgz file generated in the previous step to the Assets of release
2. generate index.yaml
```shell
@@ -282,6 +283,7 @@ To check the following items:
* All software licenses mentioned in `LICENSE`
* All the third party dependency licenses are under `licenses` folder
* If it depends on Apache license and has a `NOTICE` file, that `NOTICE` file need to be added to `NOTICE` file of the release
+
### 3. Check products
add repo
@@ -344,7 +346,7 @@ Keys to verify the Release Candidate:
https://dist.apache.org/repos/dist/dev/shardingsphere/KEYS
Look at here for how to verify this release candidate:
-https://shardingsphere.apache.org/community/en/involved/release/shardingsphere/
+https://shardingsphere.apache.org/community/en/involved/release/shardingsphere-on-cloud/
GPG user ID:
${YOUR.GPG.USER.ID}
@@ -365,13 +367,9 @@ Checklist for reference:
[ ] Checksums and PGP signatures are valid.
-[ ] Source code distributions have correct names matching the current release.
-
[ ] LICENSE and NOTICE files are correct for each ShardingSphere on Cloud repo.
[ ] All files have license headers if necessary.
-
-[ ] No compiled archives bundled in source archive.
```
2. Announce the vote result:
@@ -429,7 +427,7 @@ Website: https://shardingsphere.apache.org/
ShardingSphere on Cloud Resources:
- Issue: https://github.com/apache/shardingsphere-on-cloud/issues/
- Mailing list: dev@shardingsphere.apache.org
-- Documents: https://shardingsphere.apache.org/document/current/
+- Documents: https://shardingsphere.apache.org/oncloud/current/en/overview/