You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@doris.apache.org by zy...@apache.org on 2024/01/25 08:00:14 UTC
(doris) branch master updated: [doc](release) fix connector release doc (#30362)
This is an automated email from the ASF dual-hosted git repository.
zykkk pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/doris.git
The following commit(s) were added to refs/heads/master by this push:
new d5df146ff1a [doc](release) fix connector release doc (#30362)
d5df146ff1a is described below
commit d5df146ff1a587bfc46ccc340c32241d24402336
Author: wudi <67...@qq.com>
AuthorDate: Thu Jan 25 16:00:05 2024 +0800
[doc](release) fix connector release doc (#30362)
---
.../release-and-verify/release-doris-connectors.md | 19 ++++++++++++++-----
.../release-and-verify/release-doris-connectors.md | 19 ++++++++++++++-----
2 files changed, 28 insertions(+), 10 deletions(-)
diff --git a/docs/en/community/release-and-verify/release-doris-connectors.md b/docs/en/community/release-and-verify/release-doris-connectors.md
index 43bbebd55ce..c90696e8291 100644
--- a/docs/en/community/release-and-verify/release-doris-connectors.md
+++ b/docs/en/community/release-and-verify/release-doris-connectors.md
@@ -44,10 +44,21 @@ First, see the [release preparation](./release-prepare.md) documentation to prep
Let's take the release of Spark Connector 1.2.0 as an example.
-### 1. Prepare branch
+### 1. Prepare branch and tag
Create a branch in the code base: release-1.2.0, and checkout to this branch.
+Modify the version revision in the pom to the version number to be released, which is 1.2.0. And submit this modification, for example:
+```
+git commit -a -m "Commit for release 1.2.0"
+```
+
+Create tag and push
+```
+git tag 1.2.0
+git push origin 1.2.0
+```
+
### 2. Release to Maven staging
Because Spark Connector releases different releases for different Spark versions (such as 2.3, 3.1, 3.2), we need to process each version separately at compile time.
@@ -57,8 +68,7 @@ Let's take Spark version 2.3 and scala version 2.11 as examples:
mvn clean install \
-Dspark.version=2.3.0 \
-Dscala.version=2.11 \
--Dspark.major.version=2.3 \
--Drevision=1.2.0
+-Dspark.major.version=2.3
```
>Note: For related parameters, please refer to the compilation command in the build.sh script, and revision is the version number to be released this time.
@@ -67,8 +77,7 @@ mvn deploy \
-Papache-release \
-Dspark.version=2.3.0 \
-Dscala.version=2.11 \
--Dspark.major.version=2.3 \
--Drevision=1.2.0
+-Dspark.major.version=2.3
```
After successful execution, you can find the newly released version in [https://repository.apache.org/#stagingRepositories](https://repository.apache.org/#stagingRepositories):
diff --git a/docs/zh-CN/community/release-and-verify/release-doris-connectors.md b/docs/zh-CN/community/release-and-verify/release-doris-connectors.md
index bccb09fa2ca..62894b6f56c 100644
--- a/docs/zh-CN/community/release-and-verify/release-doris-connectors.md
+++ b/docs/zh-CN/community/release-and-verify/release-doris-connectors.md
@@ -44,10 +44,21 @@ Doris Connectors 目前包含：
我们以发布 Spark Connector 1.2.0 为例。
-### 1. 准备分支
+### 1. 准备分支和tag
在代码库中创建分支：release-1.2.0，并 checkout 到该分支。
+修改pom中的版本revision为要发布的版本号，即1.2.0。并且提交本次修改，例如：
+```
+git commit -a -m "Commit for release 1.2.0"
+```
+
+创建tag并推送
+```
+git tag 1.2.0
+git push origin 1.2.0
+```
+
### 2. 发布到 Maven staging
因为 Spark Connector 针对不同 Spark 版本（如 2.3, 3.1, 3.2）发布不同的 Release, 因此我们需要针对每一个版本单独在编译时进行处理。
@@ -57,8 +68,7 @@ Doris Connectors 目前包含：
mvn clean install \
-Dspark.version=2.3.0 \
-Dscala.version=2.11 \
--Dspark.major.version=2.3 \
--Drevision=1.2.0
+-Dspark.major.version=2.3
```
>注意：相关参数可以参考build.sh脚本中的编译命令，revision为本次要发布的版本号。
@@ -67,8 +77,7 @@ mvn deploy \
-Papache-release \
-Dspark.version=2.3.0 \
-Dscala.version=2.11 \
--Dspark.major.version=2.3 \
--Drevision=1.2.0
+-Dspark.major.version=2.3
```
执行成功后，在 [https://repository.apache.org/#stagingRepositories](https://repository.apache.org/#stagingRepositories) 里面可以找到刚刚发布的版本：
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@doris.apache.org
For additional commands, e-mail: commits-help@doris.apache.org