release prepare

Author: SbloodyS

NOTICE

@@ -1,5 +1,5 @@
 Apache DolphinScheduler
-Copyright 2019-2024 The Apache Software Foundation
+Copyright 2019-2025 The Apache Software Foundation
 
 This product includes software developed at
 The Apache Software Foundation (http://www.apache.org/).

deploy/docker/.env

@@ -16,7 +16,7 @@
 # under the License.
 #
 HUB=apache
-TAG=dev
+TAG=3.3.1
 
 TZ=Asia/Shanghai
 DATABASE=postgresql

deploy/kubernetes/dolphinscheduler/Chart.yaml

@@ -35,11 +35,11 @@ type: application
 
 # This is the chart version. This version number should be incremented each time you make changes
 # to the chart and its templates, including the app version.
-version: 3.1.0
+version: 3.3.1
 
 # This is the version number of the application being deployed. This version number should be
 # incremented each time you make changes to the application.
-appVersion: 3.1.0
+appVersion: 3.3.1
 
 dependencies:
 - name: postgresql

deploy/kubernetes/dolphinscheduler/values.yaml

@@ -33,7 +33,7 @@ image:
   # -- Docker image repository for the DolphinScheduler
   registry: apache
   # -- Docker image version for the DolphinScheduler
-  tag: latest
+  tag: 3.3.1
   # -- Image pull policy. Options: Always, Never, IfNotPresent
   pullPolicy: "IfNotPresent"
   # -- Specify a imagePullSecrets

docs/configs/docsdev.js

@@ -176,8 +176,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.3.1` manually in
+> some of not bash step like [vote mail](#vote-procedure), we are using `3.3.1` instead of `"${VERSION}"` to notice release
 > manager they have to change by hand.
 
 ### Update Documentation or Code Version
@@ -198,7 +198,7 @@ We need to update some documentation before the Maven release. For example, to r
   - `config`
     - `install-plugins.sh`: `dev-SNAPSHOT` 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.3.1`(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.
@@ -360,7 +360,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.3.1-src.tar.gz` then check the following items:
 
 - Check whether source tarball is oversized for including nonessential files
 - `LICENSE` and `NOTICE` files exist
@@ -373,7 +373,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.3.1-bin.tar.gz` to check the following items:
 
 - `LICENSE` and `NOTICE` files exist
 - Correct year in `NOTICE` file
@@ -409,23 +409,23 @@ Announce the vote result: send the result vote e-mail to `dev@dolphinscheduler.a
 Title：
 
 ```txt
-[VOTE] Release Apache DolphinScheduler <VERSION>
+[VOTE] Release Apache DolphinScheduler 3.3.1
 ```
 
 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.3.1
 
-Release notes: https://github.com/apache/dolphinscheduler/releases/tag/<VERSION>
+Release notes: https://github.com/apache/dolphinscheduler/releases/tag/3.3.1
 
-The release candidates: https://dist.apache.org/repos/dist/dev/dolphinscheduler/<VERSION>/
+The release candidates: https://dist.apache.org/repos/dist/dev/dolphinscheduler/3.3.1/
 
 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.3.1
 
 Release Commit ID: https://github.com/apache/dolphinscheduler/commit/<SHA-VALUE>
 
@@ -456,13 +456,13 @@ Checklist for reference:
 Title：
 
 ```txt
-[RESULT][VOTE] Release Apache DolphinScheduler <VERSION>
+[RESULT][VOTE] Release Apache DolphinScheduler 3.3.1
 ```
 
 Body：
 
 ```txt
-The vote to release Apache DolphinScheduler <VERSION> has passed.Here is the vote result,
+The vote to release Apache DolphinScheduler 3.3.1 has passed.Here is the vote result,
 
 4 PMC member +1 votes:
 
@@ -495,19 +495,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.3.1`, 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.3.1` release package
+  - `scripts/conf.sh`: Add new release version `3.3.1` 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.3.1`
+    - `docs0`: The `text` of two places of `en-us/zh-cn` needs to be updated to `latest(3.3.1)`
+  - `docs/configs/index.md.jsx`: Add `3.3.1: 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.3.1` 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.3.1` to
     bug-report.yml
 
 ### Publish Docker Image and Helm Chart
@@ -528,30 +528,30 @@ Announcement e-mail template as below：
 Title：
 
 ```txt
-[ANNOUNCE] Release Apache DolphinScheduler <VERSION>
+[ANNOUNCE] Release Apache DolphinScheduler 3.3.1
 ```
 
 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.3.1. 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.
 
 
 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.3.1
 
 Website: https://dolphinscheduler.apache.org/
 
 DolphinScheduler Resources:
 - Issue: https://github.com/apache/dolphinscheduler/issues/
 - Mailing list: dev@dolphinscheduler.apache.org
-- Documents: https://dolphinscheduler.apache.org/en-us/docs/<VERSION>/about/introduction
+- Documents: https://dolphinscheduler.apache.org/en-us/docs/3.3.1/about/introduction
 ```
 
 ## Remove prepare branch

docs/docs/en/contribute/release.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.3.12.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.3.11.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.3.1${mysql.connector.version}</version>
 	<scope>test<scope>
 </dependency>
 ```

docs/docs/en/faq.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.3.1-bin.tar.gz -C /opt 
 cd /opt
-mv apache-dolphinscheduler-<version>-bin  dolphinscheduler
+mv apache-dolphinscheduler-3.3.1-bin  dolphinscheduler
 ```
 
 ```markdown

docs/docs/en/guide/expansion-reduction.md

@@ -16,7 +16,7 @@ If you are a new hand and want to experience DolphinScheduler functions, we reco
 
 ```bash
 # Choose the corresponding version yourself
-helm upgrade --install dolphinscheduler --create-namespace --namespace dolphinscheduler oci://registry-1.docker.io/apache/dolphinscheduler-helm --version <version>
+helm upgrade --install dolphinscheduler --create-namespace --namespace dolphinscheduler oci://registry-1.docker.io/apache/dolphinscheduler-helm --version 3.3.1
 ```
 
 These commands are used to deploy DolphinScheduler on the Kubernetes cluster by default. The [Appendix-Configuration](#appendix-configuration) section lists the parameters that can be configured during installation.
@@ -98,7 +98,7 @@ helm install keda kedacore/keda \
 Secondly, you need to set `worker.keda.enabled` to `true` in `values.yaml` or install the chart by:
 
 ```bash
-helm upgrade --install dolphinscheduler --create-namespace --namespace dolphinscheduler oci://registry-1.docker.io/apache/dolphinscheduler-helm --version <version> --set worker.keda.enabled=true
+helm upgrade --install dolphinscheduler --create-namespace --namespace dolphinscheduler oci://registry-1.docker.io/apache/dolphinscheduler-helm --version 3.3.1 --set worker.keda.enabled=true
 ```
 
 Once autoscaling enabled, the number of workers will scale between `minReplicaCount` and `maxReplicaCount` based on the states
@@ -219,9 +219,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.3.1
 # For example
-# FROM dolphinscheduler.docker.scarf.sh/apache/dolphinscheduler-tools:<version>
+# FROM dolphinscheduler.docker.scarf.sh/apache/dolphinscheduler-tools:3.3.1
 
 # 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
@@ -270,9 +270,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.3.1
 # For example
-# FROM dolphinscheduler.docker.scarf.sh/apache/dolphinscheduler-worker:<version>
+# FROM dolphinscheduler.docker.scarf.sh/apache/dolphinscheduler-worker:3.3.1
 
 # If you want to support MySQL Datasource
 COPY mysql-connector-java-8.0.16.jar /opt/dolphinscheduler/libs
@@ -302,7 +302,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.3.1
 COPY requirements.txt /tmp
 RUN apt-get update && \
     apt-get install -y --no-install-recommends python-pip && \
@@ -337,7 +337,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.3.1
 RUN apt-get update && \
     apt-get install -y --no-install-recommends python3 && \
     rm -rf /var/lib/apt/lists/*
@@ -490,15 +490,15 @@ For example, if you need to deploy worker to both CPU and GPU servers in a clust
 
 ```bash
 # Install master, api-server, alert-server, and other default components, but do not install worker
-helm upgrade --install dolphinscheduler --create-namespace --namespace dolphinscheduler oci://registry-1.docker.io/apache/dolphinscheduler-helm --version <version> --set worker.enabled=false
+helm upgrade --install dolphinscheduler --create-namespace --namespace dolphinscheduler oci://registry-1.docker.io/apache/dolphinscheduler-helm --version 3.3.1 --set worker.enabled=false
 # Disable the installation of other components, only install worker, use the self-built CPU image, deploy to CPU servers with the `x86` label through nodeselector, and use zookeeper as the external registry center
-helm upgrade --install dolphinscheduler-cpu-worker --create-namespace --namespace dolphinscheduler oci://registry-1.docker.io/apache/dolphinscheduler-helm --version <version> \
+helm upgrade --install dolphinscheduler-cpu-worker --create-namespace --namespace dolphinscheduler oci://registry-1.docker.io/apache/dolphinscheduler-helm --version 3.3.1 \
      --set minio.enabled=false --set postgresql.enabled=false --set zookeeper.enabled=false \
      --set master.enabled=false  --set api.enabled=false --set alert.enabled=false \
      --set worker.enabled=true --set image.tag=latest-cpu --set worker.nodeSelector.cpu="x86" \
      --set externalRegistry.registryPluginName=zookeeper --set externalRegistry.registryServers=dolphinscheduler-zookeeper:2181
 # Disable the installation of other components, only install worker, use the self-built GPU image, deploy to GPU servers with the `a100` label through nodeselector, and use zookeeper as the external registry center
-helm upgrade --install dolphinscheduler-gpu-worker --create-namespace --namespace dolphinscheduler oci://registry-1.docker.io/apache/dolphinscheduler-helm --version <version> \
+helm upgrade --install dolphinscheduler-gpu-worker --create-namespace --namespace dolphinscheduler oci://registry-1.docker.io/apache/dolphinscheduler-helm --version 3.3.1 \
      --set minio.enabled=false --set postgresql.enabled=false --set zookeeper.enabled=false \
      --set master.enabled=false  --set api.enabled=false --set alert.enabled=false \
      --set worker.enabled=true --set image.tag=latest-gpu --set worker.nodeSelector.gpu="a100" \

docs/docs/en/guide/installation/kubernetes.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 or 11), 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.3.1).  <!-- markdown-link-check-disable-line -->
 
 ## Download Plugin Dependencies