This is an automated email from the ASF dual-hosted git repository.
github-bot pushed a commit to branch asf-site
in repository https://gitbox.apache.org/repos/asf/dolphinscheduler-website.git
The following commit(s) were added to refs/heads/asf-site by this push:
new c9e3311 Automated deployment: 02faabeced7965d125e64dd66b17d9f21a41c05a
c9e3311 is described below
commit c9e331168f1b8f23752e26b512d7d39d7f5f71fe
Author: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
AuthorDate: Tue Feb 22 09:52:11 2022 +0000
Automated deployment: 02faabeced7965d125e64dd66b17d9f21a41c05a
---
en-us/community/release-prepare.html | 9 +--------
en-us/community/release-prepare.json | 2 +-
en-us/community/release.html | 13 ++++++++++++-
en-us/community/release.json | 2 +-
zh-cn/community/release-prepare.html | 9 +--------
zh-cn/community/release-prepare.json | 2 +-
zh-cn/community/release.html | 14 ++++++++++++--
zh-cn/community/release.json | 2 +-
8 files changed, 30 insertions(+), 23 deletions(-)
diff --git a/en-us/community/release-prepare.html
b/en-us/community/release-prepare.html
index 3324578..e33be46 100644
--- a/en-us/community/release-prepare.html
+++ b/en-us/community/release-prepare.html
@@ -22,14 +22,6 @@
<p>For example, to release <code>x.y.z</code>, the following updates are
required:</p>
<ul>
<li><code>pom.xml</code>: <code>revision</code>, <code>version</code>,
<code>tag</code> need to be updated to x.y.z</li>
-<li><code>ambari_plugin</code>:
-<ul>
-<li><code>ambari_plugin/common-services/DOLPHIN/x.y.z</code>: the directory
needs to be updated to x.y.z</li>
-<li><code>ambari_plugin/common-services/DOLPHIN/x.y.z/alerts.json</code>: the
content needs to be updated to x.y.z</li>
-<li><code>ambari_plugin/common-services/DOLPHIN/x.y.z/metainfo.xml</code>: the
content needs to be updated to x.y.z</li>
-<li><code>ambari_plugin/statcks/DOLPHIN/metainfo.xml</code>: the content needs
to be updated to x.y.z</li>
-</ul>
-</li>
<li><code>sql</code>:
<ul>
<li><code>dolphinscheduler_mysql.sql</code>: <code>t_ds_version</code> needs
to be updated to x.y.z</li>
@@ -50,6 +42,7 @@
<li><code>values.yaml</code>: <code>image.tag</code> needs to be updated to
x.y.z</li>
</ul>
</li>
+<li><code>dolphinscheduler-python/pydolphinscheduler/setup.py</code>: change
<code>version</code> to x.y.z</li>
</ul>
</div></section><footer class="footer-container"><div
class="footer-body"><div><h3>About us</h3><h4>Do you need feedback? Please
contact us through the following ways.</h4></div><div
class="contact-container"><ul><li><a
href="/en-us/community/development/subscribe.html"><img class="img-base"
src="/img/emailgray.png"/><img class="img-change"
src="/img/emailblue.png"/><p>Email List</p></a></li><li><a
href="https://twitter.com/dolphinschedule";><img class="img-base"
src="/img/twittergray.png [...]
<script
src="//cdn.jsdelivr.net/npm/[email protected]/dist/react-with-addons.min.js"></script>
diff --git a/en-us/community/release-prepare.json
b/en-us/community/release-prepare.json
index 9d619b3..d979a13 100644
--- a/en-us/community/release-prepare.json
+++ b/en-us/community/release-prepare.json
@@ -1,6 +1,6 @@
{
"filename": "release-prepare.md",
- "__html": "<h1>Release Preparation</h1>\n<h2>Check
release-docs</h2>\n<p>Compared with the last release, the
<code>release-docs</code> of the current release needs to be updated to the
latest, if there are dependencies and versions
changes</p>\n<ul>\n<li><code>dolphinscheduler-dist/release-docs/LICENSE</code></li>\n<li><code>dolphinscheduler-dist/release-docs/NOTICE</code></li>\n<li><code>dolphinscheduler-dist/release-docs/licenses</code></li>\n</ul>\n<h2>Update
Version</h2>\n<p>For ex [...]
+ "__html": "<h1>Release Preparation</h1>\n<h2>Check
release-docs</h2>\n<p>Compared with the last release, the
<code>release-docs</code> of the current release needs to be updated to the
latest, if there are dependencies and versions
changes</p>\n<ul>\n<li><code>dolphinscheduler-dist/release-docs/LICENSE</code></li>\n<li><code>dolphinscheduler-dist/release-docs/NOTICE</code></li>\n<li><code>dolphinscheduler-dist/release-docs/licenses</code></li>\n</ul>\n<h2>Update
Version</h2>\n<p>For ex [...]
"link": "/dist/en-us/community/release-prepare.html",
"meta": {}
}
\ No newline at end of file
diff --git a/en-us/community/release.html b/en-us/community/release.html
index bb0af25..b7582ef 100644
--- a/en-us/community/release.html
+++ b/en-us/community/release.html
@@ -155,12 +155,19 @@ It is alright for <code>KEYS</code> to only include the
public key of the deploy
cd ~/ds_svn/dev/dolphinscheduler/${RELEASE.VERSION}
</code></pre>
<p>Add source code packages, binary packages and executable binary packages to
SVN working directory.</p>
-<pre><code class="language-shell">cp -f
~/dolphinscheduler/dolphinscheduler-dist/target/*.tar.gz
~/ds_svn/dev/dolphinscheduler/${RELEASE.VERSION}
+<pre><code class="language-shell"><span class="hljs-meta">#</span><span
class="bash"> Source and binary tarball <span class="hljs-keyword">for</span>
main code</span>
+cp -f ~/dolphinscheduler/dolphinscheduler-dist/target/*.tar.gz
~/ds_svn/dev/dolphinscheduler/${RELEASE.VERSION}
cp -f ~/dolphinscheduler/dolphinscheduler-dist/target/*.tar.gz.asc
~/ds_svn/dev/dolphinscheduler/${RELEASE.VERSION}
+<span class="hljs-meta">
+#</span><span class="bash"> Source and binary tarball <span
class="hljs-keyword">for</span> Python API</span>
+mkdir -p ~/ds_svn/dev/dolphinscheduler/${RELEASE.VERSION}/python
+cp -f ~/dolphinscheduler/dolphinscheduler-dist/target/python/*
~/ds_svn/dev/dolphinscheduler/${RELEASE.VERSION}/python
</code></pre>
<h3>Generate sign files</h3>
<pre><code class="language-shell">shasum -a 512
apache-dolphinscheduler-${RELEASE.VERSION}-src.tar.gz >>
apache-dolphinscheduler-${RELEASE.VERSION}-src.tar.gz.sha512
shasum -b -a 512 apache-dolphinscheduler-${RELEASE.VERSION}-bin.tar.gz
>> apache-dolphinscheduler-${RELEASE.VERSION}-bin.tar.gz.sha512
+shasum -a 512 python/apache-dolphinscheduler-${RELEASE.VERSION}.tar.gz
>> python/apache-dolphinscheduler-${RELEASE.VERSION}.tar.gz.sha512
+shasum -b -a 512
python/apache_dolphinscheduler-${RELEASE.VERSION}-py3-none-any.whl >>
python/apache_dolphinscheduler-${RELEASE.VERSION}-py3-none-any.whl.sha512
</code></pre>
<h3>Commit to Apache SVN</h3>
<pre><code class="language-shell">svn add *
@@ -170,6 +177,8 @@ svn --username=${APACHE LDAP username} commit -m
"release ${RELEASE.VERSION
<h3>Check sha512 hash</h3>
<pre><code class="language-shell">shasum -c
apache-dolphinscheduler-${RELEASE.VERSION}-src.tar.gz.sha512
shasum -c apache-dolphinscheduler-${RELEASE.VERSION}-bin.tar.gz.sha512
+shasum -c python/apache-dolphinscheduler-${RELEASE.VERSION}.tar.gz.sha512
+shasum -c
python/apache_dolphinscheduler-${RELEASE.VERSION}-py3-none-any.whl.sha512
</code></pre>
<h3>Check gpg Signature</h3>
<p>First, import releaser's public key.
@@ -196,6 +205,8 @@ Your decision? 5
<p>Then, check the gpg signature.</p>
<pre><code class="language-shell">gpg --verify
apache-dolphinscheduler-${RELEASE.VERSION}-src.tar.gz.asc
apache-dolphinscheduler-${RELEASE.VERSION}-src.tar.gz
gpg --verify apache-dolphinscheduler-${RELEASE.VERSION}-bin.tar.gz.asc
apache-dolphinscheduler-${RELEASE.VERSION}-bin.tar.gz
+gpg --verify python/apache-dolphinscheduler-${RELEASE.VERSION}.tar.gz.asc
python/apache-dolphinscheduler-${RELEASE.VERSION}.tar.gz
+gpg --verify
python/apache_dolphinscheduler-${RELEASE.VERSION}-py3-none-any.whl.asc
python/apache_dolphinscheduler-${RELEASE.VERSION}-py3-none-any.whl
</code></pre>
<h3>Check Released Files</h3>
<h4>Check source package</h4>
diff --git a/en-us/community/release.json b/en-us/community/release.json
index 01fd764..9a92b5d 100644
--- a/en-us/community/release.json
+++ b/en-us/community/release.json
@@ -1,6 +1,6 @@
{
"filename": "release.md",
- "__html": "<h1>Release Guide</h1>\n<h2>GPG Settings</h2>\n<h3>Install
GPG</h3>\n<p>Download installation package on <a
href=\"https://www.gnupg.org/download/index.html\";>official GnuPG
website</a>.\nThe command of GnuPG 1.x version can differ a little from that of
2.x version.\nThe following instructions take <code>GnuPG-2.1.23</code> version
for example.</p>\n<p>After the installation, execute the following command to
check the version number.</p>\n<pre><code class=\"language-shell\"> [...]
+ "__html": "<h1>Release Guide</h1>\n<h2>GPG Settings</h2>\n<h3>Install
GPG</h3>\n<p>Download installation package on <a
href=\"https://www.gnupg.org/download/index.html\";>official GnuPG
website</a>.\nThe command of GnuPG 1.x version can differ a little from that of
2.x version.\nThe following instructions take <code>GnuPG-2.1.23</code> version
for example.</p>\n<p>After the installation, execute the following command to
check the version number.</p>\n<pre><code class=\"language-shell\"> [...]
"link": "/dist/en-us/community/release.html",
"meta": {}
}
\ No newline at end of file
diff --git a/zh-cn/community/release-prepare.html
b/zh-cn/community/release-prepare.html
index 0d153f8..6b84724 100644
--- a/zh-cn/community/release-prepare.html
+++ b/zh-cn/community/release-prepare.html
@@ -22,14 +22,6 @@
<p>例如要发版 <code>x.y.z</code>，需要先进行以下修改:</p>
<ul>
<li><code>pom.xml</code>: <code>revision</code>, <code>version</code>,
<code>tag</code> 标签版本更新为 x.y.z</li>
-<li><code>ambari_plugin</code>:
-<ul>
-<li><code>ambari_plugin/common-services/DOLPHIN/x.y.z</code>: 目录版本更新为
x.y.z</li>
-<li><code>ambari_plugin/common-services/DOLPHIN/x.y.z/alerts.json</code>:
内容版本更新为 x.y.z</li>
-<li><code>ambari_plugin/common-services/DOLPHIN/x.y.z/metainfo.xml</code>:
内容版本更新为 x.y.z</li>
-<li><code>ambari_plugin/statcks/DOLPHIN/metainfo.xml</code>: 内容版本更新为 x.y.z</li>
-</ul>
-</li>
<li><code>sql</code>:
<ul>
<li><code>dolphinscheduler_mysql.sql</code>: <code>t_ds_version</code> 版本更新为
x.y.z</li>
@@ -50,6 +42,7 @@
<li><code>values.yaml</code>: <code>image.tag</code> 版本更新为 x.y.z</li>
</ul>
</li>
+<li><code>dolphinscheduler-python/pydolphinscheduler/setup.py</code>: 修改其中的
<code>version</code> 为 x.y.z</li>
</ul>
</div></section><footer class="footer-container"><div
class="footer-body"><div><h3>联系我们</h3><h4>有问题需要反馈？请通过以下方式联系我们。</h4></div><div
class="contact-container"><ul><li><a
href="/zh-cn/community/development/subscribe.html"><img class="img-base"
src="/img/emailgray.png"/><img class="img-change"
src="/img/emailblue.png"/><p>邮件列表</p></a></li><li><a
href="https://twitter.com/dolphinschedule";><img class="img-base"
src="/img/twittergray.png"/><img class="img-change"
src="/img/twitterblue.png"/><p [...]
<script
src="//cdn.jsdelivr.net/npm/[email protected]/dist/react-with-addons.min.js"></script>
diff --git a/zh-cn/community/release-prepare.json
b/zh-cn/community/release-prepare.json
index 8f566fc..2fb5d36 100644
--- a/zh-cn/community/release-prepare.json
+++ b/zh-cn/community/release-prepare.json
@@ -1,6 +1,6 @@
{
"filename": "release-prepare.md",
- "__html": "<h1>发版准备</h1>\n<h2>检查
release-docs</h2>\n<p>和上一个版本比较，如果有依赖及版本发生了变化，当前版本的 <code>release-docs</code>
需要被更新到最新</p>\n<ul>\n<li><code>dolphinscheduler-dist/release-docs/LICENSE</code></li>\n<li><code>dolphinscheduler-dist/release-docs/NOTICE</code></li>\n<li><code>dolphinscheduler-dist/release-docs/licenses</code></li>\n</ul>\n<h2>更新版本</h2>\n<p>例如要发版
<code>x.y.z</code>，需要先进行以下修改:</p>\n<ul>\n<li><code>pom.xml</code>:
<code>revision</code>, <code>version</code>, <code>tag</code> 标签 [...]
+ "__html": "<h1>发版准备</h1>\n<h2>检查
release-docs</h2>\n<p>和上一个版本比较，如果有依赖及版本发生了变化，当前版本的 <code>release-docs</code>
需要被更新到最新</p>\n<ul>\n<li><code>dolphinscheduler-dist/release-docs/LICENSE</code></li>\n<li><code>dolphinscheduler-dist/release-docs/NOTICE</code></li>\n<li><code>dolphinscheduler-dist/release-docs/licenses</code></li>\n</ul>\n<h2>更新版本</h2>\n<p>例如要发版
<code>x.y.z</code>，需要先进行以下修改:</p>\n<ul>\n<li><code>pom.xml</code>:
<code>revision</code>, <code>version</code>, <code>tag</code> 标签 [...]
"link": "/dist/zh-cn/community/release-prepare.html",
"meta": {}
}
\ No newline at end of file
diff --git a/zh-cn/community/release.html b/zh-cn/community/release.html
index 0fc72d8..5a2c62b 100644
--- a/zh-cn/community/release.html
+++ b/zh-cn/community/release.html
@@ -169,13 +169,19 @@ cd ~/ds_svn/dev/dolphinscheduler
cd ~/ds_svn/dev/dolphinscheduler/${RELEASE.VERSION}
</code></pre>
<p>将源码包和二进制包添加至SVN工作目录。</p>
-<pre><code class="language-shell">cp -f
~/dolphinscheduler/dolphinscheduler-dist/target/*.tar.gz
~/ds_svn/dev/dolphinscheduler/${RELEASE.VERSION}
+<pre><code class="language-shell"><span class="hljs-meta">#</span><span
class="bash"> 主程序源码包和二进制包</span>
+cp -f ~/dolphinscheduler/dolphinscheduler-dist/target/*.tar.gz
~/ds_svn/dev/dolphinscheduler/${RELEASE.VERSION}
cp -f ~/dolphinscheduler/dolphinscheduler-dist/target/*.tar.gz.asc
~/ds_svn/dev/dolphinscheduler/${RELEASE.VERSION}
-
+<span class="hljs-meta">
+#</span><span class="bash"> Python API 源码和二进制包</span>
+mkdir -p ~/ds_svn/dev/dolphinscheduler/${RELEASE.VERSION}/python
+cp -f ~/dolphinscheduler/dolphinscheduler-dist/target/python/*
~/ds_svn/dev/dolphinscheduler/${RELEASE.VERSION}/python
</code></pre>
<h3>生成文件签名</h3>
<pre><code class="language-shell">shasum -a 512
apache-dolphinscheduler-${RELEASE.VERSION}-src.tar.gz >>
apache-dolphinscheduler-${RELEASE.VERSION}-src.tar.gz.sha512
shasum -b -a 512 apache-dolphinscheduler-${RELEASE.VERSION}-bin.tar.gz
>> apache-dolphinscheduler-${RELEASE.VERSION}-bin.tar.gz.sha512
+shasum -a 512 python/apache-dolphinscheduler-${RELEASE.VERSION}.tar.gz
>> python/apache-dolphinscheduler-${RELEASE.VERSION}.tar.gz.sha512
+shasum -b -a 512
python/apache_dolphinscheduler-${RELEASE.VERSION}-py3-none-any.whl >>
python/apache_dolphinscheduler-${RELEASE.VERSION}-py3-none-any.whl.sha512
</code></pre>
<h3>提交Apache SVN</h3>
<pre><code class="language-shell">cd ~/ds_svn/dev/dolphinscheduler
@@ -186,6 +192,8 @@ svn --username=${APACHE LDAP 用户名} commit -m "release
${RELEASE.VERSIO
<h3>检查sha512哈希</h3>
<pre><code class="language-shell">shasum -c
apache-dolphinscheduler-${RELEASE.VERSION}-src.tar.gz.sha512
shasum -c apache-dolphinscheduler-${RELEASE.VERSION}-bin.tar.gz.sha512
+shasum -c python/apache-dolphinscheduler-${RELEASE.VERSION}.tar.gz.sha512
+shasum -c
python/apache_dolphinscheduler-${RELEASE.VERSION}-py3-none-any.whl.sha512
</code></pre>
<h3>检查gpg签名</h3>
<p>首先导入发布人公钥。从svn仓库导入KEYS到本地环境。（发布版本的人不需要再导入，帮助做验证的人需要导入，用户名填发版人的即可）</p>
@@ -211,6 +219,8 @@ Your decision? 5
<p>然后进行gpg签名检查。</p>
<pre><code class="language-shell">gpg --verify
apache-dolphinscheduler-${RELEASE.VERSION}-src.tar.gz.asc
apache-dolphinscheduler-${RELEASE.VERSION}-src.tar.gz
gpg --verify apache-dolphinscheduler-${RELEASE.VERSION}-bin.tar.gz.asc
apache-dolphinscheduler-${RELEASE.VERSION}-bin.tar.gz
+gpg --verify python/apache-dolphinscheduler-${RELEASE.VERSION}.tar.gz.asc
python/apache-dolphinscheduler-${RELEASE.VERSION}.tar.gz
+gpg --verify
python/apache_dolphinscheduler-${RELEASE.VERSION}-py3-none-any.whl.asc
python/apache_dolphinscheduler-${RELEASE.VERSION}-py3-none-any.whl
</code></pre>
<h3>检查发布文件内容</h3>
<h4>检查源码包的文件内容</h4>
diff --git a/zh-cn/community/release.json b/zh-cn/community/release.json
index acae916..bc14210 100644
--- a/zh-cn/community/release.json
+++ b/zh-cn/community/release.json
@@ -1,6 +1,6 @@
{
"filename": "release.md",
- "__html": "<h1>发版指南</h1>\n<h2>GPG设置</h2>\n<h3>安装GPG</h3>\n<p>在<a
href=\"https://www.gnupg.org/download/index.html\";>GnuPG官网</a>下载安装包。\nGnuPG的1.x版本和2.x版本的命令有细微差别，下列说明以<code>GnuPG-2.1.23</code>版本为例。</p>\n<p>安装完成后，执行以下命令查看版本号。</p>\n<pre><code
class=\"language-shell\">gpg
--version\n</code></pre>\n<h3>创建key</h3>\n<p>安装完成后，执行以下命令创建key。</p>\n<p><code>GnuPG-2.x</code>可使用：</p>\n<pre><code
class=\"language-shell\">gpg
--full-gen-key\n</code></pre>\n<p><code>GnuPG-1.x</code>可使用：</p>\n<pre><code
[...]
+ "__html": "<h1>发版指南</h1>\n<h2>GPG设置</h2>\n<h3>安装GPG</h3>\n<p>在<a
href=\"https://www.gnupg.org/download/index.html\";>GnuPG官网</a>下载安装包。\nGnuPG的1.x版本和2.x版本的命令有细微差别，下列说明以<code>GnuPG-2.1.23</code>版本为例。</p>\n<p>安装完成后，执行以下命令查看版本号。</p>\n<pre><code
class=\"language-shell\">gpg
--version\n</code></pre>\n<h3>创建key</h3>\n<p>安装完成后，执行以下命令创建key。</p>\n<p><code>GnuPG-2.x</code>可使用：</p>\n<pre><code
class=\"language-shell\">gpg
--full-gen-key\n</code></pre>\n<p><code>GnuPG-1.x</code>可使用：</p>\n<pre><code
[...]
"link": "/dist/zh-cn/community/release.html",
"meta": {}
}
\ No newline at end of file
