This is an automated email from the ASF dual-hosted git repository.
dockerzhang pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/inlong-website.git
The following commit(s) were added to refs/heads/master by this push:
new d40acda9c3 [INLONG-810][Doc] Update version release related docs (#811)
d40acda9c3 is described below
commit d40acda9c36af83f52d90c3978f46578848f3bae
Author: vernedeng <[email protected]>
AuthorDate: Thu Jul 20 11:36:26 2023 +0800
[INLONG-810][Doc] Update version release related docs (#811)
Co-authored-by: vernedeng <[email protected]>
Co-authored-by: Charles Zhang <[email protected]>
---
community/how-to-release.md | 9 ++++++---
community/how-to-verify.md | 2 +-
.../current/how-to-release.md | 9 ++++++---
.../current/how-to-verify.md | 2 +-
4 files changed, 14 insertions(+), 8 deletions(-)
diff --git a/community/how-to-release.md b/community/how-to-release.md
index d333df5510..c3c6b270e2 100644
--- a/community/how-to-release.md
+++ b/community/how-to-release.md
@@ -118,6 +118,8 @@ Uploading takes about one minute, after that, you can check
it by your email at
The svn repository of the DEV branch is:
https://dist.apache.org/repos/dist/dev/inlong
The svn repository of the Release branch is:
https://dist.apache.org/repos/dist/release/inlong
+
+Please ensure that the `key` you added to `dev` and `release` branches is the
same.
:::
- Add the public key to KEYS in the dev branch to release the RC version
@@ -126,7 +128,7 @@ The svn repository of the Release branch is:
https://dist.apache.org/repos/dist/
$ svn co https://dist.apache.org/repos/dist/dev/inlong /tmp/inlong-dist-dev
$ cd inlong-dist-dev
# # Append your key to the KEYS file
-$ gpg --export --armor [email protected] >> KEYS
+$ (gpg --list-sigs <key id> && gpg --armor --export <key id>) >> KEYS
# Later on, if you are asked to enter a username and password, just use your
apache username and password.
$ svn ci -m "add gpg key for YOUR_NAME"
```
@@ -135,7 +137,7 @@ $ svn ci -m "add gpg key for YOUR_NAME"
```shell
$ svn co https://dist.apache.org/repos/dist/release/inlong
/tmp/inlong-dist-release
$ cd inlong-dist-release
-$ gpg --export --armor [email protected] >> KEYS
+$ (gpg --list-sigs <key id> && gpg --armor --export <key id>) >> KEYS
$ svn ci -m "add gpg key for YOUR_NAME"
```
@@ -287,7 +289,8 @@ $ svn commit -m "prepare for ${release_version}
${rc_version}"
- You will get a link like
`https://repository.apache.org/content/repositories/orgapacheinlong-{staging-id}`
on the Summary page if all checks passed. This link will be posted in the vote
email, so, keep it safe.
:::caution
-Close operation may fail, you should check the causes and fix them.
+- Close operation may not work, it's better to check and fix the causes.
+- The key you uploaded before may not be synchronized among the keyserver,
please upload it to `keyserver.ubuntu.com` or `keys.openpgp.org` if there is a
`Signature Validation` event.
:::
## Apache InLong community vote
diff --git a/community/how-to-verify.md b/community/how-to-verify.md
index 74491d319f..af4fc4886e 100644
--- a/community/how-to-verify.md
+++ b/community/how-to-verify.md
@@ -53,7 +53,7 @@ You can check the compilation and unit test through `mvn
clean package install`.
:::
### Check binary packages
-Unzip `apache-inlong-${release_version}-bin.tar.gz` and
`apache-inlong-${release_version}-sort-connectors.tar.gz` and check the
following:
+Unzip `apache-inlong-${release_version}-bin.tar.gz`, and the `Sort Connector`
corresponding to your Flink version, then check the following:
- Whether the LICENSE and NOTICE file exists and whether the content is correct
- Whether the normal deployment is successful
- Deploy the test environment and verify whether the production and
consumption can run normally
diff --git
a/i18n/zh-CN/docusaurus-plugin-content-docs-community/current/how-to-release.md
b/i18n/zh-CN/docusaurus-plugin-content-docs-community/current/how-to-release.md
index 049a74abd2..6e919cdfd2 100644
---
a/i18n/zh-CN/docusaurus-plugin-content-docs-community/current/how-to-release.md
+++
b/i18n/zh-CN/docusaurus-plugin-content-docs-community/current/how-to-release.md
@@ -116,6 +116,8 @@ $ gpg --keyserver pgpkeys.mit.edu --send-key <key id>
dev 分支的 svn 仓库：https://dist.apache.org/repos/dist/dev/inlong
release 分支的 SVN 仓库：https://dist.apache.org/repos/dist/release/inlong
+
+请确认 `dev` 和 `release` 分支中增加的 `key` 相同
:::
- 在 dev 分支中添加公钥到 KEYS，用于发布 RC 版本
@@ -124,7 +126,7 @@ release 分支的 SVN
仓库：https://dist.apache.org/repos/dist/release/inlong
$ svn co https://dist.apache.org/repos/dist/dev/inlong /tmp/inlong-dist-dev
$ cd inlong-dist-dev
# 追加你生成的 KEY 到文件 KEYS 中, 追加后最好检查一下是否正确
-$ gpg --export --armor [email protected] >> KEYS
+$ (gpg --list-sigs <key id> && gpg --armor --export <key id>) >> KEYS
# 接下来会要求输入用户名和密码，就用你的 apache 的用户名和密码
$ svn ci -m "add gpg key for YOUR_NAME"
```
@@ -133,7 +135,7 @@ $ svn ci -m "add gpg key for YOUR_NAME"
```shell
$ svn co https://dist.apache.org/repos/dist/release/inlong
/tmp/inlong-dist-release
$ cd inlong-dist-release
-$ gpg --export --armor [email protected] >> KEYS
+$ (gpg --list-sigs <key id> && gpg --armor --export <key id>) >> KEYS
$ svn ci -m "add gpg key for YOUR_NAME"
```
@@ -285,7 +287,8 @@ $ svn commit -m "prepare for ${release_version}
${rc_version}"
- 检查通过以后, 在下方的 Summary 标签页上出现一个连接，请保存好这个链接，需要放在接下来的投票邮件当中，链接类似
`https://repository.apache.org/content/repositories/orgapacheinlong-{staging-id}`
。
:::caution
-请注意点击 Close 可能会出现失败，请检查失败原因并处理
+- 如果 Close 操作失败，请检查失败原因并处理
+- 如果出现 `Signature Validation` 错误事件，可能是 `keyserver` 之间没有同步 `key`，可以重新上传 `key` 到
`keyserver.ubuntu.com` 或 `keys.openpgp.org`
:::
## Apache InLong 社区投票
diff --git
a/i18n/zh-CN/docusaurus-plugin-content-docs-community/current/how-to-verify.md
b/i18n/zh-CN/docusaurus-plugin-content-docs-community/current/how-to-verify.md
index 5b7f426cdb..a1d57c334a 100644
---
a/i18n/zh-CN/docusaurus-plugin-content-docs-community/current/how-to-verify.md
+++
b/i18n/zh-CN/docusaurus-plugin-content-docs-community/current/how-to-verify.md
@@ -53,7 +53,7 @@ for i in *.tar.gz; do echo $i; gpg --verify $i.asc $i ; done
:::
### 检查二进制包
-解压缩 `apache-inlong-${release_version}-bin.tar.gz` 和
`apache-inlong-${release_version}-sort-connectors.tar.gz`，进行如下检查:
+解压缩 `apache-inlong-${release_version}-bin.tar.gz`, 以及对应 Flink 版本的 `Sort
Connector`，进行如下检查:
- LICENSE and NOTICE 文件是否存在及内容是否正确
- 能否正常部署成功
- 部署测试环境、验证生产消费能否正常运行
