You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@inlong.apache.org by do...@apache.org on 2022/09/19 03:17:31 UTC

[inlong-website] branch master updated: [INLONG-551][Doc] Update release doc and fix bugs (#559)

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 e701f62032 [INLONG-551][Doc] Update release doc and fix bugs (#559)
e701f62032 is described below

commit e701f620325e3f70d3e473886ad8a9db0dc22bb2
Author: Schnapps <zp...@connect.ust.hk>
AuthorDate: Mon Sep 19 11:17:26 2022 +0800

    [INLONG-551][Doc] Update release doc and fix bugs (#559)
    
    Co-authored-by: EMsnap <st...@tencent.com>
---
 community/how-to-release.md                                 | 13 ++++++++++---
 .../current/how-to-release.md                               | 12 +++++++++---
 2 files changed, 19 insertions(+), 6 deletions(-)

diff --git a/community/how-to-release.md b/community/how-to-release.md
index 04ddf4f806..abd7bcde78 100644
--- a/community/how-to-release.md
+++ b/community/how-to-release.md
@@ -31,7 +31,8 @@ $ gpg --version #check the version, should be 2.x
 ### Generate gpg Key
 #### Attentions:
 - Name is best to keep consistent with your full name of Apache ID
-- Email should be the Apache email
+- The mailbox used is apache. It is recommended that pg -k view all the keys. If the first one is not the key of the apache mailbox, if you need to specify the key in the step for encryption operation, the parameter is -u
+- Make sure that there is only one key, and delete the keys of other spare mailboxes first
 - Name is best to only use English to avoid garbled
 
 #### Generate the key as prompt
@@ -394,7 +395,8 @@ svn delete https://dist.apache.org/repos/dist/release/inlong/${last_release_vers
 ### Update links on official website
 
 ### Send email to `dev@inlong.apache.org` and CC `announce@apache.org`
-**Please make sure deployment in step 6.4 is successfully, and generally wait 24 hours between 6.4 and send emails** 
+**Please make sure deployment in step 6.4 is successfully, and generally wait 24 hours between 6.4 and send emails**
+**Log in to https://downloads.apache.org/inlong/${release-version}/ to see if there is an installation package**
 
 Release announce email template:
 ```html
@@ -421,7 +423,7 @@ https://github.com/apache/inlong/blob/${release_version}-${rc_version}/CHANGES.m
 
 Apache InLong website: https://inlong.apache.org/
 
-Download Links: https://inlong.apache.org/download/main
+Download Links: https://inlong.apache.org/download
 
 InLong Resources:
 - Issue: https://github.com/apache/inlong/issues
@@ -430,3 +432,8 @@ InLong Resources:
 Thanks
 On behalf of Apache InLong community
 ```
+
+### Official website added release package
+
+1. Go to https://github.com/apache/inlong, click the + sign under Releases on the right, then click Draft a new release
+2. The release title is ${release_version}, upload all files under https://downloads.apache.org/inlong/${release-version}
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 0203021212..84fb42dfe0 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
@@ -29,7 +29,7 @@ $ gpg --version #检查版本,应该为2.x
 ### 生成 gpg Key
 #### 需要注意以下几点:
 - 输入名字时最好与 Apache 中登记的 Full name 保持一致
-- 使用的邮箱应该是 apache 邮箱
+- 使用的邮箱必须是 apache 邮箱,建议先 gpg -k 查看所有 key, 如果列表中第一个不是 apache 邮箱的 key ,需要在后续步骤中指定 key 来进行加密解密操作,参数为 -u
 - 名字最好使用拼音或者英文,否则会出现乱码
 
 #### 根据提示,生成key
@@ -405,7 +405,8 @@ svn delete https://dist.apache.org/repos/dist/release/inlong/${last_release_vers
 ### 更新官网链接
 
 ### 发ANNOUNCE邮件,主送 `dev@inlong.apache.org`,抄送 `announce@apache.org`
-**请确保6.4中的仓库已发布成功,一般是在6.4后的24小时后发布邮件** 
+**请确保6.4中的仓库已发布成功,一般是在6.4后的24小时后发布邮件**
+**登陆 https://downloads.apache.org/inlong/${release-version}/ 查看是否有安装包**
 
 宣布 release 邮件模板:
 ```html
@@ -433,7 +434,7 @@ https://github.com/apache/inlong/blob/${release_version}-${rc_version}/CHANGES.m
 
 Apache InLong website: https://inlong.apache.org/
 
-Download Links: https://inlong.apache.org/download/main
+Download Links: https://inlong.apache.org/download
 
 InLong Resources:
 - Issue: https://github.com/apache/inlong/issues
@@ -442,3 +443,8 @@ InLong Resources:
 Thanks
 On behalf of Apache InLong community
 ```
+
+### 官网新增 release 包
+
+1. 进入 https://github.com/apache/inlong ,点击右侧 Releases 下 + 号, 然后点击 Draft a new release
+2. release title 为 ${release_version},上传 https://downloads.apache.org/inlong/${release-version} 下的所有文件到上传栏中再发布
\ No newline at end of file