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/11/16 09:16:11 UTC
[inlong-website] branch fix-598 updated (f7d3251aff -> 598cdbd0f5)
This is an automated email from the ASF dual-hosted git repository.
dockerzhang pushed a change to branch fix-598
in repository https://gitbox.apache.org/repos/asf/inlong-website.git
omit f7d3251aff update format
omit ce2b1e3220 update format
omit 59f795e899 update format
omit 24b402acb8 update format
omit 9c4c6986d2 update format
omit b9b182de20 update format
omit c34af3c368 update format
omit 51625480ef update format
omit 6401672dde [INLONG-598][Doc] Update the how to release guide for Apache InLong
add 908a70dd32 [INLONG-598][Doc] Update the how to release guide for Apache InLong (#599)
add 92c2f4fcf9 [INLONG-596] Bump docusaurus to 2.2.0 (#597)
add 8e3444bdb0 [INLONG-594][Doc] Update the docker-compose guide format (#595)
add 4ac5ec641e [INLONG-600][Doc] Update the concept and introduction guide (#601)
add f859b7f666 [INLONG-588][Release] Modify download & release notes for 1.4.0 (#604)
new 598cdbd0f5 [INLONG-598][Doc] Update the how to release guide for Apache InLong(addendum)
This update added new revisions after undoing existing revisions.
That is to say, some revisions that were in the old version of the
branch are not in the new version. This situation occurs
when a user --force pushes a change and generates a repository
containing something like this:
* -- * -- B -- O -- O -- O (f7d3251aff)
\
N -- N -- N refs/heads/fix-598 (598cdbd0f5)
You should already have received notification emails for all of the O
revisions, and so the following emails describe only the N revisions
from the common base, B.
Any revisions marked "omit" are not gone; other references still
refer to them. Any revisions marked "discard" are gone forever.
The 1 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails. The revisions
listed as "add" were already present in the repository and have only
been added to this reference.
Summary of changes:
community/how-to-release.md | 48 ++-
docs/deployment/docker.md | 8 +-
docs/deployment/img/create_cluster_tag.png | Bin 22555 -> 22127 bytes
docs/design_and_concept/basic_concept.md | 28 +-
docs/introduction.md | 6 +-
download/index.md | 38 +-
download/release-1.3.0.md | 12 +-
download/release-1.4.0.md | 400 +++++++++++++++++++++
.../current/how-to-release.md | 48 +--
.../current/deployment/docker.md | 7 +-
.../current/design_and_concept/basic_concept.md | 28 +-
.../current/introduction.md | 12 +-
.../index.md | 18 +-
.../release-1.3.0.md | 12 +-
.../release-1.4.0.md | 400 +++++++++++++++++++++
package.json | 6 +-
16 files changed, 949 insertions(+), 122 deletions(-)
create mode 100644 download/release-1.4.0.md
create mode 100644 i18n/zh-CN/docusaurus-plugin-content-pages-download/release-1.4.0.md
[inlong-website] 01/01: [INLONG-598][Doc] Update the how to release guide for Apache InLong(addendum)
Posted by do...@apache.org.
This is an automated email from the ASF dual-hosted git repository.
dockerzhang pushed a commit to branch fix-598
in repository https://gitbox.apache.org/repos/asf/inlong-website.git
commit 598cdbd0f509c32d2dd64b5a4e1af47d1004a419
Author: dockerzhang <do...@apache.org>
AuthorDate: Wed Nov 16 17:15:53 2022 +0800
[INLONG-598][Doc] Update the how to release guide for Apache InLong(addendum)
---
community/how-to-release.md | 48 +++++++++++++---------
.../current/how-to-release.md | 48 ++++++++++++----------
2 files changed, 56 insertions(+), 40 deletions(-)
diff --git a/community/how-to-release.md b/community/how-to-release.md
index ec93fcb63b..0fe13bef46 100644
--- a/community/how-to-release.md
+++ b/community/how-to-release.md
@@ -283,13 +283,6 @@ $ svn commit -m "prepare for ${release_version} ${rc_version}"
Close operation may fail, you should check the causes and fix them.
:::
-### Clean up temporary files
-If the above steps are successful, the version release is booming, and you can clean up local temporary files and conduct community voting.
-```shell
-$ rm -rf /tmp/apache-inlong-${release_version}-${rc_version}/
-$ rm -rf /tmp/inlong-dist-dev/
-```
-
## Apache InLong community vote
### Start Vote
Send email to `dev@inlong.apache.org`, the vote template is:
@@ -377,14 +370,7 @@ Your InLong Release Manager
```shell
$ svn mv https://dist.apache.org/repos/dist/dev/inlong/${release_version}-${rc_version} https://dist.apache.org/repos/dist/release/inlong/${release_version} -m "Release ${release_version}"
```
-
-### Check whether the dev and release is correct
-- Make sure `${release_version}-${rc_version}` is deleted in [dev](https://dist.apache.org/repos/dist/dev/inlong/).
-- Delete release package of pre versions [release](https://dist.apache.org/repos/dist/release/inlong/)，these packages will be saved [here](https://archive.apache.org/dist/inlong/)
-```shell
-# last_release_version is the last version number, you can check is by accessing https://dist.apache.org/repos/dist/release/inlong/ ,e.g 1.3.0
-$ svn delete https://dist.apache.org/repos/dist/release/inlong/${last_release_version} -m "Delete ${last_release_version}"
-```
+Then make sure `${release_version}-${rc_version}` directory is deleted in [dev](https://dist.apache.org/repos/dist/dev/inlong/).
### Release version in Apache Staging
- Log in http://repository.apache.org with your Apache account
@@ -397,6 +383,9 @@ Wait the repository sync to other repositories which generally takes 24 hours
:::
### Update Documents and download links on official website
+- Update [download](https://inlong.apache.org/download/) resource links
+
+- Create a ${release-version} pair for the version document
### Send email to `dev@inlong.apache.org` and CC `announce@apache.org`
- Please make sure deployment in Apache Staging is successfully
@@ -406,7 +395,9 @@ Wait the repository sync to other repositories which generally takes 24 hours
- Release announce email, the template is：
```html
Title： [ANNOUNCE] Release Apache InLong ${release_version}
+
Content：
+
Hi all,
The Apache InLong community is pleased to announce
@@ -419,12 +410,15 @@ This platform helps you easily build stream-based data applications.
This release contains a number of new features, bug fixes and
improvements compared to the last version released before.
The notable changes since ${release_version} include:
-1. Features:
-2. Bug Fixed:
-3. Improvements:
+
+1. Feature-1
+2. Feature-2
+3. Feature-3
+
+${release_version} since the last versions, which can be found at:
Please refer to the change log for the complete list of changes:
-https://github.com/apache/inlong/blob/${release_version}-${rc_version}/CHANGES.md
+https://github.com/apache/inlong/blob/release-${release_version}/CHANGES.md
Apache InLong website: https://inlong.apache.org/
@@ -441,3 +435,19 @@ On behalf of Apache InLong community
### GitHub release package
- Go to https://github.com/apache/inlong, click the + sign under Releases on the right, then click Draft a new release
- The release title is ${release_version}, upload all files under https://downloads.apache.org/inlong/${release-version}
+
+## After the release
+### Clean up temporary files
+If the above steps are successful, the version release is booming, and you can clean up local temporary files and conduct community voting.
+```shell
+$ rm -rf /tmp/apache-inlong-${release_version}-${rc_version}/
+$ rm -rf /tmp/inlong-dist-dev/
+```
+
+### Archive the previous version packages
+Delete release package of previous versions [release](https://dist.apache.org/repos/dist/release/inlong/)，these packages will be saved [here](https://archive.apache.org/dist/inlong/)
+```shell
+# last_release_version is the last version number, you can check is by accessing https://dist.apache.org/repos/dist/release/inlong/ ,e.g 1.3.0
+$ svn delete https://dist.apache.org/repos/dist/release/inlong/${last_release_version} -m "Delete ${last_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 a62b9c45e5..7f1cc49554 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
@@ -282,13 +282,6 @@ $ svn commit -m "prepare for ${release_version} ${rc_version}"
请注意点击 Close 可能会出现失败，请检查失败原因并处理
:::
-### 清理本地临时文件
-若以上步骤操作成功，说明版本发布顺利，可以清理本地临时文件，进行社区投票。
-```shell
-$ rm -rf /tmp/apache-inlong-${release_version}-${rc_version}/
-$ rm -rf /tmp/inlong-dist-dev/
-```
-
## Apache InLong 社区投票
### 发起投票
发送邮件到 `dev@inlong.apache.org`，投票模板为：
@@ -376,14 +369,7 @@ Your InLong Release Manager
```shell
$ svn mv https://dist.apache.org/repos/dist/dev/inlong/${release_version}-${rc_version} https://dist.apache.org/repos/dist/release/inlong/${release_version} -m "Release ${release_version}"
```
-
-### 确认 dev 和 release 下的包是否正确
-- 确认 [dev](https://dist.apache.org/repos/dist/dev/inlong/) 下的 `${release_version}-${rc_version}` 已被删除
-- 删除 [release](https://dist.apache.org/repos/dist/release/inlong/) 目录下上一个版本的发布包，这些包会被自动保存在[这里](https://archive.apache.org/dist/inlong/)
-```shell
-# last_release_version 为上一个版本号，可以访问 https://dist.apache.org/repos/dist/release/inlong/ 查看，比如 1.3.0
-$ svn delete https://dist.apache.org/repos/dist/release/inlong/${last_release_version} -m "Delete ${last_release_version}"
-```
+然后确认 [dev](https://dist.apache.org/repos/dist/dev/inlong/) 下的 `${release_version}-${rc_version}` 目录是否已被删除。
### 在 Apache Staging 仓库发布版本
- 使用 Apache 账号登录 http://repository.apache.org
@@ -396,6 +382,9 @@ $ svn delete https://dist.apache.org/repos/dist/release/inlong/${last_release_ve
:::
### 更新官网文档和下载链接
+- 更新[下载页面](https://inlong.apache.org/download/)的资源链接
+
+- 创建 ${release-version} 对应对版本文档
### 发 ANNOUNCE 邮件，主送 `dev@inlong.apache.org`，抄送 `announce@apache.org`
- 请确保 Apache Staging 仓库已发布成功
@@ -405,10 +394,12 @@ $ svn delete https://dist.apache.org/repos/dist/release/inlong/${last_release_ve
- 宣布 release 邮件，模板为：
```html
标题： [ANNOUNCE] Release Apache InLong ${release_version}
+
内容：
+
Hi all,
-The Apache InLong community is pleased to announce
+The Apache InLong community is pleased to announce
that Apache InLong ${release_version} has been released!
Apache InLong is a one-stop integration framework for massive data that provides automatic, secure,
@@ -418,13 +409,13 @@ This platform helps you easily build stream-based data applications.
This release contains a number of new features, bug fixes and
improvements compared to the last version released before.
The notable changes since ${release_version} include:
-1. Features:
-2. Bug Fixed:
-3. Improvements:
+1. Feature-1
+2. Feature-2
+3. Feature-3
Please refer to the change log for the complete list of changes:
-https://github.com/apache/inlong/blob/${release_version}-${rc_version}/CHANGES.md
+https://github.com/apache/inlong/blob/release-${release_version}/CHANGES.md
Apache InLong website: https://inlong.apache.org/
@@ -440,4 +431,19 @@ On behalf of Apache InLong community
### GitHub 官网新增 release 包
- 进入 https://github.com/apache/inlong ，点击右侧 Releases 下 + 号， 然后点击 Draft a new release
-- release title 为 ${release_version}，上传 https://downloads.apache.org/inlong/${release-version} 下的所有文件到上传栏中再发布
\ No newline at end of file
+- release title 为 ${release_version}，上传 https://downloads.apache.org/inlong/${release-version} 下的所有文件到上传栏中再发布
+
+## 发布后
+### 清理本地临时文件
+若以上步骤操作成功，说明版本发布顺利，可以清理本地临时文件，进行社区投票。
+```shell
+$ rm -rf /tmp/apache-inlong-${release_version}-${rc_version}/
+$ rm -rf /tmp/inlong-dist-dev/
+```
+
+### 归档上一个版本的发布包
+删除 [release](https://dist.apache.org/repos/dist/release/inlong/) 目录下上一个版本的发布包，这些包会被自动保存在[这里](https://archive.apache.org/dist/inlong/)
+```shell
+# last_release_version 为上一个版本号，可以访问 https://dist.apache.org/repos/dist/release/inlong/ 查看，比如 1.3.0
+$ svn delete https://dist.apache.org/repos/dist/release/inlong/${last_release_version} -m "Delete ${last_release_version}"
+```
\ No newline at end of file