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

wangxj pushed a commit to branch 3.2.2-prepare
in repository https://gitbox.apache.org/repos/asf/dolphinscheduler.git


The following commit(s) were added to refs/heads/3.2.2-prepare by this push:
     new 8ee334fc2f modify doc of 3.2.2
8ee334fc2f is described below

commit 8ee334fc2f4803d7a628458018d82ca695b920d1
Author: wangxj959 <[email protected]>
AuthorDate: Sat Jul 20 14:22:53 2024 +0800

    modify doc of 3.2.2
---
 docs/docs/en/contribute/release.md            | 48 +++++++++++++--------------
 docs/docs/en/faq.md                           |  6 ++--
 docs/docs/en/guide/expansion-reduction.md     |  4 +--
 docs/docs/en/guide/installation/kubernetes.md | 12 +++----
 docs/docs/en/guide/installation/standalone.md |  2 +-
 docs/docs/en/guide/start/docker.md            | 10 +++---
 docs/docs/zh/contribute/release.md            | 44 ++++++++++++------------
 docs/docs/zh/faq.md                           |  6 ++--
 docs/docs/zh/guide/expansion-reduction.md     |  4 +--
 docs/docs/zh/guide/installation/kubernetes.md | 12 +++----
 docs/docs/zh/guide/installation/standalone.md |  2 +-
 docs/docs/zh/guide/start/docker.md            |  8 ++---
 12 files changed, 79 insertions(+), 79 deletions(-)

diff --git a/docs/docs/en/contribute/release.md 
b/docs/docs/en/contribute/release.md
index 4fffce4688..5437237270 100644
--- a/docs/docs/en/contribute/release.md
+++ b/docs/docs/en/contribute/release.md
@@ -165,8 +165,8 @@ SVN_DIR=<PATH-TO-SVN-ROOT>  # to keep binary package 
checkout from SVN, the sub
 
 > Note: We can use the variable directly in you bash after we set environment, 
 > without changing anything. For example, we
 > can use command `git clone -b "${VERSION}"-prepare 
 > https://github.com/apache/dolphinscheduler.git` to clone the release branch
-> and it can be successful by converting the `"${VERSION}"` to 
`<THE-VERSION-YOU-RELEASE>`. But you have to change `<VERSION>` manually in
-> some of not bash step like [vote mail](#vote-procedure), we are using 
`<VERSION>` instead of `"${VERSION}"` to notice release
+> and it can be successful by converting the `"${VERSION}"` to 
`<THE-VERSION-YOU-RELEASE>`. But you have to change `3.2.2` manually in
+> some of not bash step like [vote mail](#vote-procedure), we are using 
`3.2.2` instead of `"${VERSION}"` to notice release
 > manager they have to change by hand.
 
 ### Update Documentation or Code Version
@@ -185,7 +185,7 @@ We need to update some documentation before the Maven 
release. For example, to r
     - `Chart.yaml`: `appVersion` and `version` needs to be updated to x.y.z
     - `values.yaml`: `image.tag` needs to be updated to x.y.z
 - Version in the docs:
-  - Change the placeholder `<version>`(except `pom`) to the `x.y.z` in 
directory `docs`
+  - Change the placeholder `3.2.2`(except `pom`) to the `x.y.z` in directory 
`docs`
   - Add new history version
     - `docs/docs/en/history-versions.md` and 
`docs/docs/zh/history-versions.md`: Add the new version and link for `x.y.z`
   - `docs/configs/docsdev.js`: change `/dev/` to `/x.y.z/`, **DO NOT** change 
this filename, is will be auto change by website tools.
@@ -340,7 +340,7 @@ svn --username="${A_USERNAME}" commit -m "release 
${VERSION}"
 
 #### Check source package
 
-Decompress `apache-dolphinscheduler-<VERSION>-src.tar.gz` then check the 
following items:
+Decompress `apache-dolphinscheduler-3.2.2-src.tar.gz` then check the following 
items:
 
 - Check whether source tarball is oversized for including nonessential files
 - `LICENSE` and `NOTICE` files exist
@@ -353,7 +353,7 @@ Decompress `apache-dolphinscheduler-<VERSION>-src.tar.gz` 
then check the followi
 
 #### Check binary packages
 
-Decompress `apache-dolphinscheduler-<VERSION>-bin.tar.gz` to check the 
following items:
+Decompress `apache-dolphinscheduler-3.2.2-bin.tar.gz` to check the following 
items:
 
 - `LICENSE` and `NOTICE` files exist
 - Correct year in `NOTICE` file
@@ -389,7 +389,7 @@ Announce the vote result: send the result vote e-mail to 
`[email protected]
 Title:
 
 ```txt
-[VOTE] Release Apache DolphinScheduler <VERSION>
+[VOTE] Release Apache DolphinScheduler 3.2.2
 ```
 
 Body:
@@ -397,15 +397,15 @@ Body:
 ```txt
 Hello DolphinScheduler Community,
 
-This is a call for vote to release Apache DolphinScheduler version <VERSION>
+This is a call for vote to release Apache DolphinScheduler version 3.2.2
 
-Release notes: 
https://github.com/apache/dolphinscheduler/releases/tag/<VERSION>
+Release notes: https://github.com/apache/dolphinscheduler/releases/tag/3.2.2
 
-The release candidates: 
https://dist.apache.org/repos/dist/dev/dolphinscheduler/<VERSION>/
+The release candidates: 
https://dist.apache.org/repos/dist/dev/dolphinscheduler/3.2.2/
 
 Maven 2 staging repository: 
https://repository.apache.org/content/repositories/<STAGING.REPOSITORY>/org/apache/dolphinscheduler/
 
-Git tag for the release: 
https://github.com/apache/dolphinscheduler/tree/<VERSION>
+Git tag for the release: https://github.com/apache/dolphinscheduler/tree/3.2.2
 
 Release Commit ID: 
https://github.com/apache/dolphinscheduler/commit/<SHA-VALUE>
 
@@ -436,13 +436,13 @@ Checklist for reference:
 Title:
 
 ```txt
-[RESULT][VOTE] Release Apache DolphinScheduler <VERSION>
+[RESULT][VOTE] Release Apache DolphinScheduler 3.2.2
 ```
 
 Body:
 
 ```txt
-The vote to release Apache DolphinScheduler <VERSION> has passed.Here is the 
vote result,
+The vote to release Apache DolphinScheduler 3.2.2 has passed.Here is the vote 
result,
 
 4 PMC member +1 votes:
 
@@ -478,19 +478,19 @@ and then find DolphinScheduler in [apache staging 
repositories](https://reposito
 ### Update Document
 
 Website should be present before you send the announce mail this section will 
tell you how to change the website. For example,
-the release version is `<VERSION>`, the following updates are required(note it 
will take effect immediately when the PR is merged):
+the release version is `3.2.2`, the following updates are required(note it 
will take effect immediately when the PR is merged):
 
 - Repository **apache/dolphinscheduler-website**:
-  - `config/download.json`: add the download of the `<VERSION>` release package
-  - `scripts/conf.sh`: Add new release version `<VERSION>` key-value pair to 
variable `DEV_RELEASE_DOCS_VERSIONS`
+  - `config/download.json`: add the download of the `3.2.2` release package
+  - `scripts/conf.sh`: Add new release version `3.2.2` key-value pair to 
variable `DEV_RELEASE_DOCS_VERSIONS`
 - Repository **apache/dolphinscheduler** (dev branch):
   - `docs/configs/site.js`:
-    - `docsLatest`: update to `<VERSION>`
-    - `docs0`: The `text` of two places of `en-us/zh-cn` needs to be updated 
to `latest(<VERSION>)`
-  - `docs/configs/index.md.jsx`: Add `<VERSION>: docsxyzConfig` and add new 
`import` for the new `docsxyzConfig`
-  - `docs/docs/en/history-versions.md` and `docs/docs/zh/history-versions.md`: 
Add new `<VERSION>` release docs.
+    - `docsLatest`: update to `3.2.2`
+    - `docs0`: The `text` of two places of `en-us/zh-cn` needs to be updated 
to `latest(3.2.2)`
+  - `docs/configs/index.md.jsx`: Add `3.2.2: docsxyzConfig` and add new 
`import` for the new `docsxyzConfig`
+  - `docs/docs/en/history-versions.md` and `docs/docs/zh/history-versions.md`: 
Add new `3.2.2` release docs.
   - `.github/ISSUE_TEMPLATE/bug-report.yml`: DolphinScheduler's GitHub 
[bug-report](https://github.com/apache/dolphinscheduler/blob/dev/.github/ISSUE_TEMPLATE/bug-report.yml)
-    issue template have **Version** selection bottom. So after released we 
should add the new `<VERSION>` to
+    issue template have **Version** selection bottom. So after released we 
should add the new `3.2.2` to
     bug-report.yml
 
 ### Publish Docker Image and Helm Chart
@@ -511,7 +511,7 @@ Announcement e-mail template as below:
 Title:
 
 ```txt
-[ANNOUNCE] Release Apache DolphinScheduler <VERSION>
+[ANNOUNCE] Release Apache DolphinScheduler 3.2.2
 ```
 
 Body:
@@ -519,7 +519,7 @@ Body:
 ```txt
 Hi all,
 
-We are glad to announce the release of Apache DolphinScheduler <VERSION>. Once 
again I would like to express my thanks to your help.
+We are glad to announce the release of Apache DolphinScheduler 3.2.2. Once 
again I would like to express my thanks to your help.
 
 Dolphin Scheduler is a distributed and easy-to-extend visual workflow 
scheduler system,
 dedicated to solving the complex task dependencies in data processing, making 
the scheduler system out of the box for data processing.
@@ -527,14 +527,14 @@ dedicated to solving the complex task dependencies in 
data processing, making th
 
 Download Links: https://dolphinscheduler.apache.org/en-us/download
 
-Release Notes: 
https://github.com/apache/dolphinscheduler/releases/tag/<VERSION>
+Release Notes: https://github.com/apache/dolphinscheduler/releases/tag/3.2.2
 
 Website: https://dolphinscheduler.apache.org/
 
 DolphinScheduler Resources:
 - Issue: https://github.com/apache/dolphinscheduler/issues/
 - Mailing list: [email protected]
-- Documents: 
https://dolphinscheduler.apache.org/en-us/docs/<VERSION>/about/introduction
+- Documents: 
https://dolphinscheduler.apache.org/en-us/docs/3.2.2/about/introduction
 ```
 
 ## News
diff --git a/docs/docs/en/faq.md b/docs/docs/en/faq.md
index 7ac4afb76e..15a2ba3a94 100644
--- a/docs/docs/en/faq.md
+++ b/docs/docs/en/faq.md
@@ -280,7 +280,7 @@ A : Will hive pom
 <dependency>
     <groupId>org.apache.hive</groupId>
     <artifactId>hive-jdbc</artifactId>
-    <version>2.3.9</version>
+    3.2.22.3.9</version>
 </dependency>
 ```
 
@@ -290,7 +290,7 @@ change into
 <dependency>
     <groupId>org.apache.hive</groupId>
     <artifactId>hive-jdbc</artifactId>
-    <version>1.1.0</version>
+    3.2.21.1.0</version>
 </dependency>
 ```
 
@@ -484,7 +484,7 @@ A: 1, Edit project root dir maven config file, remove scope 
test property so tha
 <dependency>
        <groupId>mysql</groupId>
        <artifactId>mysql-connector-java</artifactId>
-       <version>${mysql.connector.version}</version>
+       3.2.2${mysql.connector.version}</version>
        <scope>test<scope>
 </dependency>
 ```
diff --git a/docs/docs/en/guide/expansion-reduction.md 
b/docs/docs/en/guide/expansion-reduction.md
index 5c9dd7d1d2..45303dd704 100644
--- a/docs/docs/en/guide/expansion-reduction.md
+++ b/docs/docs/en/guide/expansion-reduction.md
@@ -30,9 +30,9 @@ Attention: DolphinScheduler itself does not depend on Hadoop, 
Hive, Spark, but w
 mkdir -p /opt
 cd /opt
 # decompress
-tar -zxvf apache-dolphinscheduler-<version>-bin.tar.gz -C /opt 
+tar -zxvf apache-dolphinscheduler-3.2.2-bin.tar.gz -C /opt 
 cd /opt
-mv apache-dolphinscheduler-<version>-bin  dolphinscheduler
+mv apache-dolphinscheduler-3.2.2-bin  dolphinscheduler
 ```
 
 ```markdown
diff --git a/docs/docs/en/guide/installation/kubernetes.md 
b/docs/docs/en/guide/installation/kubernetes.md
index a6587a5855..dd1ad77238 100644
--- a/docs/docs/en/guide/installation/kubernetes.md
+++ b/docs/docs/en/guide/installation/kubernetes.md
@@ -233,9 +233,9 @@ kubectl scale --replicas=6 sts dolphinscheduler-worker -n 
test # with test names
 2. Create a new `Dockerfile` to add MySQL driver:
 
 ```
-FROM 
dolphinscheduler.docker.scarf.sh/apache/dolphinscheduler-<service>:<version>
+FROM dolphinscheduler.docker.scarf.sh/apache/dolphinscheduler-<service>:3.2.2
 # For example
-# FROM dolphinscheduler.docker.scarf.sh/apache/dolphinscheduler-tools:<version>
+# FROM dolphinscheduler.docker.scarf.sh/apache/dolphinscheduler-tools:3.2.2
 
 # Attention Please, If the build is dolphinscheduler-tools image
 # You need to change the following line to: COPY 
mysql-connector-java-8.0.16.jar /opt/dolphinscheduler/tools/libs
@@ -284,9 +284,9 @@ externalDatabase:
 2. Create a new `Dockerfile` to add MySQL or Oracle driver:
 
 ```
-FROM 
dolphinscheduler.docker.scarf.sh/apache/dolphinscheduler-<service>:<version>
+FROM dolphinscheduler.docker.scarf.sh/apache/dolphinscheduler-<service>:3.2.2
 # For example
-# FROM 
dolphinscheduler.docker.scarf.sh/apache/dolphinscheduler-worker:<version>
+# FROM dolphinscheduler.docker.scarf.sh/apache/dolphinscheduler-worker:3.2.2
 
 # If you want to support MySQL Datasource
 COPY mysql-connector-java-8.0.16.jar /opt/dolphinscheduler/libs
@@ -316,7 +316,7 @@ docker build -t 
apache/dolphinscheduler-<service>:new-driver .
 1. Create a new `Dockerfile` to install pip:
 
 ```
-FROM dolphinscheduler.docker.scarf.sh/apache/dolphinscheduler-worker:<version>
+FROM dolphinscheduler.docker.scarf.sh/apache/dolphinscheduler-worker:3.2.2
 COPY requirements.txt /tmp
 RUN apt-get update && \
     apt-get install -y --no-install-recommends python-pip && \
@@ -351,7 +351,7 @@ docker build -t apache/dolphinscheduler-worker:pip .
 1. Create a new `Dockerfile` to install Python 3:
 
 ```
-FROM dolphinscheduler.docker.scarf.sh/apache/dolphinscheduler-worker:<version>
+FROM dolphinscheduler.docker.scarf.sh/apache/dolphinscheduler-worker:3.2.2
 RUN apt-get update && \
     apt-get install -y --no-install-recommends python3 && \
     rm -rf /var/lib/apt/lists/*
diff --git a/docs/docs/en/guide/installation/standalone.md 
b/docs/docs/en/guide/installation/standalone.md
index bd2d73f1ce..e4b0fb86cd 100644
--- a/docs/docs/en/guide/installation/standalone.md
+++ b/docs/docs/en/guide/installation/standalone.md
@@ -12,7 +12,7 @@ If you want to deploy DolphinScheduler in production, we 
recommend you follow [c
 ## Preparation
 
 - JDK:download [JDK][jdk] (1.8+), install and configure environment variable 
`JAVA_HOME` and append `bin` dir (included in `JAVA_HOME`) to `PATH` variable. 
You can skip this step if it already exists in your environment.
-- Binary package: download the DolphinScheduler binary package at [download 
page](https://dolphinscheduler.apache.org/en-us/download/<version>).  <!-- 
markdown-link-check-disable-line -->
+- Binary package: download the DolphinScheduler binary package at [download 
page](https://dolphinscheduler.apache.org/en-us/download/3.2.2).  <!-- 
markdown-link-check-disable-line -->
 
 ## Start DolphinScheduler Standalone Server
 
diff --git a/docs/docs/en/guide/start/docker.md 
b/docs/docs/en/guide/start/docker.md
index f29bcd5c75..9470e304e6 100644
--- a/docs/docs/en/guide/start/docker.md
+++ b/docs/docs/en/guide/start/docker.md
@@ -19,7 +19,7 @@ Start DolphinScheduler with standalone-server Docker images 
is the easiest way t
 you can learn DolphinScheduler's concepts and usage, with minimal cost.
 
 ```shell
-$ DOLPHINSCHEDULER_VERSION=<version>
+$ DOLPHINSCHEDULER_VERSION=3.2.2
 $ docker run --name dolphinscheduler-standalone-server -p 12345:12345 -p 
25333:25333 -d 
apache/dolphinscheduler-standalone-server:"${DOLPHINSCHEDULER_VERSION}"
 ```
 
@@ -37,11 +37,11 @@ be stored on disks after you change docker-compose 
configuration, and it is robu
 DolphinScheduler in a long term. You have to install 
[docker-compose](https://docs.docker.com/compose/install/) before you
 start servers.
 
-After complete the installation, get the `docker-compose.yaml` file from 
[download page](https://dolphinscheduler.apache.org/en-us/download/<version>)
+After complete the installation, get the `docker-compose.yaml` file from 
[download page](https://dolphinscheduler.apache.org/en-us/download/3.2.2)
 form its source package, and make sure you get the right version. After 
download the package, you can run the commands as below.
 
 ```shell
-$ DOLPHINSCHEDULER_VERSION=<version>
+$ DOLPHINSCHEDULER_VERSION=3.2.2
 $ tar -zxf apache-dolphinscheduler-"${DOLPHINSCHEDULER_VERSION}"-src.tar.gz
 # Going to docker-compose's location
 # For Mac or Linux users
@@ -68,7 +68,7 @@ $ docker-compose --profile all up -d
 container when it up. You could start DolphinScheduler server separately if 
you want to reuse your exists services.
 
 ```shell
-$ DOLPHINSCHEDULER_VERSION=<version>
+$ DOLPHINSCHEDULER_VERSION=3.2.2
 # Initialize the database, make sure database <DATABASE> already exists
 $ docker run -d --name dolphinscheduler-tools \
     -e DATABASE="postgresql" \
@@ -134,5 +134,5 @@ and use `admin` and `dolphinscheduler123` as default 
username and password in th
 
 You can modify some environment variables to change configurations when you 
are starting servers through Docker. We have
 an example in [using exists PostgreSQL 
ZooKeeper](#using-exists-postgresql-zookeeper) to change database and ZooKeeper 
configurations,
-and you could find all environment variables in [all environment 
variables](https://github.com/apache/dolphinscheduler/blob/<version>/script/env/dolphinscheduler_env.sh)
 <!-- markdown-link-check-disable-line -->
+and you could find all environment variables in [all environment 
variables](https://github.com/apache/dolphinscheduler/blob/3.2.2/script/env/dolphinscheduler_env.sh)
 <!-- markdown-link-check-disable-line -->
 and change them if you want.
diff --git a/docs/docs/zh/contribute/release.md 
b/docs/docs/zh/contribute/release.md
index 5f4f4bdf7c..ebee3d2b7e 100644
--- a/docs/docs/zh/contribute/release.md
+++ b/docs/docs/zh/contribute/release.md
@@ -172,7 +172,7 @@ SVN_DIR=<PATH-TO-SVN-ROOT>  # to keep binary package 
checkout from SVN, the sub
 
 > 注意:设置环境变量后,我们可以直接在你的 bash 中使用该变量,而无需更改任何内容。例如,我们可以直接使用命令 `git clone -b 
 > "${VERSION}"-prepare https://github.com/apache/dolphinscheduler.git`
 > 来克隆发布分支,他会自动将其中的 `"${VERSION}"` 转化成你设置的值 `<THE-VERSION-YOU-RELEASE>`。 
 > 但是您必须在一些非 bash 步骤中手动更改
-> `<VERSION>` 为对应的版本号,例如发起投票中的内容。我们使用 `<VERSION>` 而不是 `"${VERSION}"` 来提示 
release manager 他们必须手动更改这部分内容
+> `3.2.2` 为对应的版本号,例如发起投票中的内容。我们使用 `3.2.2` 而不是 `"${VERSION}"` 来提示 release 
manager 他们必须手动更改这部分内容
 
 ### 更新文档和代码的版本
 
@@ -190,7 +190,7 @@ SVN_DIR=<PATH-TO-SVN-ROOT>  # to keep binary package 
checkout from SVN, the sub
     - `Chart.yaml`: `appVersion` 和 `version` 版本更新为 x.y.z
     - `values.yaml`: `image.tag` 版本更新为 x.y.z
 - 修改文档(docs 模块)中的版本号:
-  - 将 `docs` 文件夹下文件的占位符 `<version>` (除了 pom.xml 相关的) 修改成 `x.y.z`
+  - 将 `docs` 文件夹下文件的占位符 `3.2.2` (除了 pom.xml 相关的) 修改成 `x.y.z`
   - 新增历史版本
     - `docs/docs/en/history-versions.md` 和 `docs/docs/zh/history-versions.md`: 
增加新的历史版本为 `x.y.z`
   - 修改文档 sidebar
@@ -347,7 +347,7 @@ svn --username="${A_USERNAME}" commit -m "release 
${VERSION}"
 
 #### 检查源码包的文件内容
 
-解压缩`apache-dolphinscheduler-<VERSION>-src.tar.gz`,进行如下检查:
+解压缩`apache-dolphinscheduler-3.2.2-src.tar.gz`,进行如下检查:
 
 - 检查源码包是否包含由于包含不必要文件,致使 tarball 过于庞大
 - 存在`LICENSE`和`NOTICE`文件
@@ -359,7 +359,7 @@ svn --username="${A_USERNAME}" commit -m "release 
${VERSION}"
 
 #### 检查二进制包的文件内容
 
-解压缩`apache-dolphinscheduler-<VERSION>-bin.tar.gz`进行如下检查:
+解压缩`apache-dolphinscheduler-3.2.2-bin.tar.gz`进行如下检查:
 
 - 存在`LICENSE`和`NOTICE`文件
 - 所有文本文件开头都有 ASF 许可证
@@ -394,7 +394,7 @@ DolphinScheduler 社区投票,发起投票邮件到`[email protected]
 标题:
 
 ```txt
-[VOTE] Release Apache DolphinScheduler <VERSION>
+[VOTE] Release Apache DolphinScheduler 3.2.2
 ```
 
 正文:
@@ -402,15 +402,15 @@ DolphinScheduler 社区投票,发起投票邮件到`[email protected]
 ```txt
 Hello DolphinScheduler Community,
 
-This is a call for vote to release Apache DolphinScheduler version <VERSION>
+This is a call for vote to release Apache DolphinScheduler version 3.2.2
 
-Release notes: 
https://github.com/apache/dolphinscheduler/releases/tag/<VERSION>
+Release notes: https://github.com/apache/dolphinscheduler/releases/tag/3.2.2
 
-The release candidates: 
https://dist.apache.org/repos/dist/dev/dolphinscheduler/<VERSION>/
+The release candidates: 
https://dist.apache.org/repos/dist/dev/dolphinscheduler/3.2.2/
 
 Maven 2 staging repository: 
https://repository.apache.org/content/repositories/<STAGING.REPOSITORY>/org/apache/dolphinscheduler/
 
-Git tag for the release: 
https://github.com/apache/dolphinscheduler/tree/<VERSION>
+Git tag for the release: https://github.com/apache/dolphinscheduler/tree/3.2.2
 
 Release Commit ID: 
https://github.com/apache/dolphinscheduler/commit/<SHA-VALUE>
 
@@ -441,11 +441,11 @@ Checklist for reference:
 Title:
 
 ```txt
-[RESULT][VOTE] Release Apache DolphinScheduler <VERSION>
+[RESULT][VOTE] Release Apache DolphinScheduler 3.2.2
 ```
 
 ```txt
-The vote to release Apache DolphinScheduler <VERSION> has passed.Here is the 
vote result,
+The vote to release Apache DolphinScheduler 3.2.2 has passed.Here is the vote 
result,
 
 4 PMC member +1 votes:
 
@@ -480,17 +480,17 @@ git push --delete "${GH_REMOTE}" "${VERSION}-prepare"
 
 ### 更新文档
 
-官网应该在您发送通知邮件之前完成更新,本节将告诉您如何更改网站。假设发版的版本是 `<VERSION>`,需要进行以下更新(注意,当修改 pull 
requests 被 merge 后就会生效):
+官网应该在您发送通知邮件之前完成更新,本节将告诉您如何更改网站。假设发版的版本是 `3.2.2`,需要进行以下更新(注意,当修改 pull requests 
被 merge 后就会生效):
 
 - **apache/dolphinscheduler-website** 仓库:
-  - `config/download.json`: 增加 `<VERSION>` 版本发布包的下载
-  - `scripts/conf.sh`: 在变量 `DEV_RELEASE_DOCS_VERSIONS` 中增加版本为 `<VERSION>` 的新键值对
+  - `config/download.json`: 增加 `3.2.2` 版本发布包的下载
+  - `scripts/conf.sh`: 在变量 `DEV_RELEASE_DOCS_VERSIONS` 中增加版本为 `3.2.2` 的新键值对
 - **apache/dolphinscheduler** 仓库 (dev 分支):
   - `docs/configs/site.js`:
-    - `docsLatest`: 更新为 `<VERSION>`
-    - `docs0`: 两处 `en-us/zh-cn` 的 `text` 更新为 `latest(<VERSION>)`
-  - `docs/configs/index.md.jsx`: 增加 `'<VERSION>': docsxyzConfig,` 以及新的 `import`
-  - `docs/docs/en/history-versions.md` 和 `docs/docs/zh/history-versions.md`: 
增加新的发版版本 `<VERSION>` 的链接
+    - `docsLatest`: 更新为 `3.2.2`
+    - `docs0`: 两处 `en-us/zh-cn` 的 `text` 更新为 `latest(3.2.2)`
+  - `docs/configs/index.md.jsx`: 增加 `'3.2.2': docsxyzConfig,` 以及新的 `import`
+  - `docs/docs/en/history-versions.md` 和 `docs/docs/zh/history-versions.md`: 
增加新的发版版本 `3.2.2` 的链接
   - `.github/ISSUE_TEMPLATE/bug-report.yml`: DolphinScheduler 在 GitHub bug 
report 的 issue 中有版本选择,当有新的版本发版后,需要更新
     
[bug-report](https://github.com/apache/dolphinscheduler/blob/dev/.github/ISSUE_TEMPLATE/bug-report.yml)
 中的 **Version** 部分。
 
@@ -510,7 +510,7 @@ git push --delete "${GH_REMOTE}" "${VERSION}-prepare"
 标题:
 
 ```txt
-[ANNOUNCE] Release Apache DolphinScheduler <VERSION>
+[ANNOUNCE] Release Apache DolphinScheduler 3.2.2
 ```
 
 正文:
@@ -518,7 +518,7 @@ git push --delete "${GH_REMOTE}" "${VERSION}-prepare"
 ```txt
 Hi all,
 
-We are glad to announce the release of Apache DolphinScheduler <VERSION>. Once 
again I would like to express my thanks to your help.
+We are glad to announce the release of Apache DolphinScheduler 3.2.2. Once 
again I would like to express my thanks to your help.
 
 Dolphin Scheduler is a distributed and easy-to-extend visual workflow 
scheduler system,
 dedicated to solving the complex task dependencies in data processing, making 
the scheduler system out of the box for data processing.
@@ -526,14 +526,14 @@ dedicated to solving the complex task dependencies in 
data processing, making th
 
 Download Links: https://dolphinscheduler.apache.org/zh-cn/download
 
-Release Notes: 
https://github.com/apache/dolphinscheduler/releases/tag/<VERSION>
+Release Notes: https://github.com/apache/dolphinscheduler/releases/tag/3.2.2
 
 Website: https://dolphinscheduler.apache.org/
 
 DolphinScheduler Resources:
 - Issue: https://github.com/apache/dolphinscheduler/issues/
 - Mailing list: [email protected]
-- Documents: 
https://dolphinscheduler.apache.org/zh-cn/docs/<VERSION>/about/introduction
+- Documents: 
https://dolphinscheduler.apache.org/zh-cn/docs/3.2.2/about/introduction
 ```
 
 ## News
diff --git a/docs/docs/zh/faq.md b/docs/docs/zh/faq.md
index a4f32d08a8..b41ff51b40 100644
--- a/docs/docs/zh/faq.md
+++ b/docs/docs/zh/faq.md
@@ -251,7 +251,7 @@ A: 将 hive pom
 <dependency>
     <groupId>org.apache.hive</groupId>
     <artifactId>hive-jdbc</artifactId>
-    <version>2.3.9</version>
+    3.2.22.3.9</version>
 </dependency>
 ```
 
@@ -261,7 +261,7 @@ A: 将 hive pom
 <dependency>
     <groupId>org.apache.hive</groupId>
     <artifactId>hive-jdbc</artifactId>
-    <version>1.1.0</version>
+    3.2.21.1.0</version>
 </dependency>
 ```
 
@@ -455,7 +455,7 @@ A:1,修改项目根目录 maven 配置文件,移除 scope 的 test 属性
 <dependency>
        <groupId>mysql</groupId>
        <artifactId>mysql-connector-java</artifactId>
-       <version>${mysql.connector.version}</version>
+       3.2.2${mysql.connector.version}</version>
        <scope>test<scope>
 </dependency>
 ```
diff --git a/docs/docs/zh/guide/expansion-reduction.md 
b/docs/docs/zh/guide/expansion-reduction.md
index ad27e32a35..36d04bed9f 100644
--- a/docs/docs/zh/guide/expansion-reduction.md
+++ b/docs/docs/zh/guide/expansion-reduction.md
@@ -30,9 +30,9 @@
 mkdir -p /opt
 cd /opt
 # 解压缩
-tar -zxvf apache-dolphinscheduler-<version>-bin.tar.gz -C /opt 
+tar -zxvf apache-dolphinscheduler-3.2.2-bin.tar.gz -C /opt 
 cd /opt
-mv apache-dolphinscheduler-<version>-bin  dolphinscheduler
+mv apache-dolphinscheduler-3.2.2-bin  dolphinscheduler
 ```
 
 ```markdown
diff --git a/docs/docs/zh/guide/installation/kubernetes.md 
b/docs/docs/zh/guide/installation/kubernetes.md
index f4b95de27b..4846d4b3e3 100644
--- a/docs/docs/zh/guide/installation/kubernetes.md
+++ b/docs/docs/zh/guide/installation/kubernetes.md
@@ -232,9 +232,9 @@ kubectl scale --replicas=6 sts dolphinscheduler-worker -n 
test # with test names
 2. 创建一个新的 `Dockerfile`,用于添加 MySQL 的驱动包:
 
 ```
-FROM 
dolphinscheduler.docker.scarf.sh/apache/dolphinscheduler-<service>:<version>
+FROM dolphinscheduler.docker.scarf.sh/apache/dolphinscheduler-<service>:3.2.2
 # 例如
-# FROM dolphinscheduler.docker.scarf.sh/apache/dolphinscheduler-tools:<version>
+# FROM dolphinscheduler.docker.scarf.sh/apache/dolphinscheduler-tools:3.2.2
 
 # 注意,如果构建的是dolphinscheduler-tools镜像
 # 需要将下面一行修改为COPY mysql-connector-java-8.0.16.jar 
/opt/dolphinscheduler/tools/libs
@@ -283,9 +283,9 @@ externalDatabase:
 2. 创建一个新的 `Dockerfile`,用于添加 MySQL 或者 Oracle 驱动包:
 
 ```
-FROM 
dolphinscheduler.docker.scarf.sh/apache/dolphinscheduler-<service>:<version>
+FROM dolphinscheduler.docker.scarf.sh/apache/dolphinscheduler-<service>:3.2.2
 # 例如
-# FROM 
dolphinscheduler.docker.scarf.sh/apache/dolphinscheduler-worker:<version>
+# FROM dolphinscheduler.docker.scarf.sh/apache/dolphinscheduler-worker:3.2.2
 
 # 如果你想支持 MySQL 数据源
 COPY mysql-connector-java-8.0.16.jar /opt/dolphinscheduler/libs
@@ -315,7 +315,7 @@ docker build -t 
apache/dolphinscheduler-<service>:new-driver .
 1. 创建一个新的 `Dockerfile`,用于安装 pip:
 
 ```
-FROM dolphinscheduler.docker.scarf.sh/apache/dolphinscheduler-worker:<version>
+FROM dolphinscheduler.docker.scarf.sh/apache/dolphinscheduler-worker:3.2.2
 COPY requirements.txt /tmp
 RUN apt-get update && \
     apt-get install -y --no-install-recommends python-pip && \
@@ -350,7 +350,7 @@ docker build -t apache/dolphinscheduler-worker:pip .
 1. 创建一个新的 `Dockerfile`,用于安装 Python 3:
 
 ```
-FROM dolphinscheduler.docker.scarf.sh/apache/dolphinscheduler-worker:<version>
+FROM dolphinscheduler.docker.scarf.sh/apache/dolphinscheduler-worker:3.2.2
 RUN apt-get update && \
     apt-get install -y --no-install-recommends python3 && \
     rm -rf /var/lib/apt/lists/*
diff --git a/docs/docs/zh/guide/installation/standalone.md 
b/docs/docs/zh/guide/installation/standalone.md
index dbd9ca94b6..34cbe8d6b7 100644
--- a/docs/docs/zh/guide/installation/standalone.md
+++ b/docs/docs/zh/guide/installation/standalone.md
@@ -10,7 +10,7 @@ Standalone 仅适用于 DolphinScheduler 的快速体验.
 ## 前置准备工作
 
 - JDK:下载[JDK][jdk] (1.8+),安装并配置 `JAVA_HOME` 环境变量,并将其下的 `bin` 目录追加到 `PATH` 
环境变量中。如果你的环境中已存在,可以跳过这步。
-- 二进制包:在[下载页面](https://dolphinscheduler.apache.org/en-us/download/<version>)下载 
DolphinScheduler 二进制包  <!-- markdown-link-check-disable-line -->
+- 二进制包:在[下载页面](https://dolphinscheduler.apache.org/en-us/download/3.2.2)下载 
DolphinScheduler 二进制包  <!-- markdown-link-check-disable-line -->
 
 ## 启动 DolphinScheduler Standalone Server
 
diff --git a/docs/docs/zh/guide/start/docker.md 
b/docs/docs/zh/guide/start/docker.md
index 2a3a577a73..3ab1d23cb8 100644
--- a/docs/docs/zh/guide/start/docker.md
+++ b/docs/docs/zh/guide/start/docker.md
@@ -18,7 +18,7 @@
 你可以最快速的体验到 DolphinScheduler 的大部分功能,了解主要和概念和内容。
 
 ```shell
-$ DOLPHINSCHEDULER_VERSION=<version>
+$ DOLPHINSCHEDULER_VERSION=3.2.2
 $ docker run --name dolphinscheduler-standalone-server -p 12345:12345 -p 
25333:25333 -d 
apache/dolphinscheduler-standalone-server:"${DOLPHINSCHEDULER_VERSION}"
 ```
 
@@ -33,11 +33,11 @@ $ docker run --name dolphinscheduler-standalone-server -p 
12345:12345 -p 25333:2
 服务重启的时候保留元数据(如需要挂载到本地路径需要做指定)。他更健壮,能保证用户体验更加完整的 DolphinScheduler 服务。这种方式需要先安装
 [docker-compose](https://docs.docker.com/compose/install/),链接适用于 
Mac,Linux,Windows。
 
-确保 docker-compose 顺利安装后,需要获取 `docker-compose.yaml` 
文件,通过[下载页面](https://dolphinscheduler.apache.org/en-us/download/<version>)
+确保 docker-compose 顺利安装后,需要获取 `docker-compose.yaml` 
文件,通过[下载页面](https://dolphinscheduler.apache.org/en-us/download/3.2.2)
 下载对应版本源码包可能是最快的方法,当下载完源码后就可以运行命令进行部署了。
 
 ```shell
-$ DOLPHINSCHEDULER_VERSION=<version>
+$ DOLPHINSCHEDULER_VERSION=3.2.2
 $ tar -zxf apache-dolphinscheduler-"${DOLPHINSCHEDULER_VERSION}"-src.tar.gz
 # Mac Linux 用户
 $ cd apache-dolphinscheduler-"${DOLPHINSCHEDULER_VERSION}"-src/deploy/docker
@@ -61,7 +61,7 @@ $ docker-compose --profile all up -d
 ZooKeeper 且不想启动新的服务,可以使用这个方式分别启动 DolphinScheduler 容器。
 
 ```shell
-$ DOLPHINSCHEDULER_VERSION=<version>
+$ DOLPHINSCHEDULER_VERSION=3.2.2
 # 初始化数据库,其确保数据库 <DATABASE> 已经存在
 $ docker run -d --name dolphinscheduler-tools \
     -e DATABASE="postgresql" \

Reply via email to