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/incubator-dolphinscheduler-website.git


The following commit(s) were added to refs/heads/asf-site by this push:
     new 158f25b  Automated deployment: Tue Jan  7 12:28:46 UTC 2020 
d1afe3c15ab374181bcbbdb01ca538b17a11f9d9
158f25b is described below

commit 158f25b15ec18623aaae1b7002f019d4fdc9676b
Author: qiaozhanwei <[email protected]>
AuthorDate: Tue Jan 7 12:28:46 2020 +0000

    Automated deployment: Tue Jan  7 12:28:46 UTC 2020 
d1afe3c15ab374181bcbbdb01ca538b17a11f9d9
---
 en-us/docs/1.2.0/user_doc/backend-deployment.html  |  18 +-
 en-us/docs/1.2.0/user_doc/backend-deployment.json  |   2 +-
 en-us/docs/1.2.0/user_doc/frontend-deployment.html |   8 -
 en-us/docs/1.2.0/user_doc/frontend-deployment.json |   2 +-
 zh-cn/docs/1.2.0/user_doc/backend-deployment.html  |  18 +-
 zh-cn/docs/1.2.0/user_doc/backend-deployment.json  |   2 +-
 zh-cn/docs/1.2.0/user_doc/frontend-deployment.html |   8 -
 zh-cn/docs/1.2.0/user_doc/frontend-deployment.json |   2 +-
 zh-cn/docs/development/release.html                | 484 +++++++++++++++++++++
 zh-cn/docs/development/release.json                |   6 +
 10 files changed, 522 insertions(+), 28 deletions(-)

diff --git a/en-us/docs/1.2.0/user_doc/backend-deployment.html 
b/en-us/docs/1.2.0/user_doc/backend-deployment.html
index a9934e7..034aed3 100644
--- a/en-us/docs/1.2.0/user_doc/backend-deployment.html
+++ b/en-us/docs/1.2.0/user_doc/backend-deployment.html
@@ -76,7 +76,7 @@ Modify the following attributes in 
./conf/application-dao.properties</p>
 <pre><code> instruction of dolphinscheduler-backend directory 
 </code></pre>
 <pre><code class="language-directory">bin : Basic service startup script
-DISCLAIMER : DISCLAIMER
+DISCLAIMER-WIP : DISCLAIMER-WIP
 conf : Project Profile
 lib : The project relies on jar packages, including individual module jars and 
third-party jars
 LICENSE : LICENSE
@@ -98,7 +98,7 @@ install.sh :  One-click deployment script
 <p>Modify deployment parameters (depending on your server and business 
situation):</p>
 </li>
 <li>
-<p>Modify the parameters in <strong><a 
href="http://install.sh";>install.sh</a></strong> to replace the values required 
by your business</p>
+<p>Modify the parameters in <code>install.sh</code> to replace the values 
required by your business</p>
 <ul>
 <li>MonitorServerState switch variable, added in version 1.0.3, controls 
whether to start the self-start script (monitor master, worker status, if 
off-line will start automatically). The default value of &quot;false&quot; 
means that the self-start script is not started, and if it needs to start, it 
is changed to &quot;true&quot;.</li>
 <li>'hdfsStartupSate' switch variable controls whether to start hdfs
@@ -111,8 +111,8 @@ Change the variable to 'true' if you want to use hdfs, you 
also need to create t
 </li>
 </ul>
 <h2>Deployment</h2>
-<p>Either of the following two methods can be deployed,automated deployment is 
recommended, and experienced partners can use source deployment as well.</p>
-<h3>Automated Deployment</h3>
+<p>Either of the following two methods can be deployed,binary file deployment 
is recommended, and experienced partners can use source deployment as well.</p>
+<h3>Binary file Deployment</h3>
 <ul>
 <li>
 <p>Install zookeeper tools</p>
@@ -153,6 +153,16 @@ Change the variable to 'true' if you want to use hdfs, you 
also need to create t
 </ul>
 <p>After normal compilation, 
<code>apache-dolphinscheduler-incubating-${latest.release.version}-dolphinscheduler-backend-bin.tar.gz</code>
 is generated in the 
<code>./dolphinscheduler-dist/dolphinscheduler-backend/target</code> 
directory</p>
+<ul>
+<li>
+<p>Install zookeeper tools</p>
+<p><code>pip install kazoo</code></p>
+</li>
+<li>
+<p>Switch to deployment user, one-click deployment</p>
+<p><code>sh install.sh</code></p>
+</li>
+</ul>
 <h3>Start-and-stop services commonly used in systems (for service purposes, 
please refer to System Architecture Design for details)</h3>
 <ul>
 <li>
diff --git a/en-us/docs/1.2.0/user_doc/backend-deployment.json 
b/en-us/docs/1.2.0/user_doc/backend-deployment.json
index 2e0f6f5..a4fa6c4 100644
--- a/en-us/docs/1.2.0/user_doc/backend-deployment.json
+++ b/en-us/docs/1.2.0/user_doc/backend-deployment.json
@@ -1,6 +1,6 @@
 {
   "filename": "backend-deployment.md",
-  "__html": "<h1>Backend Deployment Document</h1>\n<p>There are two deployment 
modes for the backend:</p>\n<ul>\n<li>automatic deployment</li>\n<li>source 
code compile and then 
deployment</li>\n</ul>\n<h2>Preparations</h2>\n<p>Download the latest version 
of the installation package, download address:  <a 
href=\"https://dolphinscheduler.apache.org/en-us/docs/user_doc/download.html\";>download</a>,\ndownload
 
apache-dolphinscheduler-incubating-x.x.x-dolphinscheduler-backend-bin.tar.gz</p>\n<
 [...]
+  "__html": "<h1>Backend Deployment Document</h1>\n<p>There are two deployment 
modes for the backend:</p>\n<ul>\n<li>automatic deployment</li>\n<li>source 
code compile and then 
deployment</li>\n</ul>\n<h2>Preparations</h2>\n<p>Download the latest version 
of the installation package, download address:  <a 
href=\"https://dolphinscheduler.apache.org/en-us/docs/user_doc/download.html\";>download</a>,\ndownload
 
apache-dolphinscheduler-incubating-x.x.x-dolphinscheduler-backend-bin.tar.gz</p>\n<
 [...]
   "link": "/en-us/docs/1.2.0/user_doc/backend-deployment.html",
   "meta": {}
 }
\ No newline at end of file
diff --git a/en-us/docs/1.2.0/user_doc/frontend-deployment.html 
b/en-us/docs/1.2.0/user_doc/frontend-deployment.html
index 0d7d445..f7e5cb7 100644
--- a/en-us/docs/1.2.0/user_doc/frontend-deployment.html
+++ b/en-us/docs/1.2.0/user_doc/frontend-deployment.html
@@ -22,14 +22,6 @@ decompress<code>tar -zxvf 
apache-dolphinscheduler-incubating-x.x.x-dolphinschedu
 <h2>Deployment</h2>
 <p>Automated deployment is recommended for either of the following two ways</p>
 <h3>Automated Deployment</h3>
-<p>Edit the installation file<code>vi install-dolphinscheduler-ui.sh</code> in 
the<code>dolphinscheduler-ui</code> directory</p>
-<p>Change the front-end access port and the back-end proxy interface 
address</p>
-<pre><code># Configure the front-end access port
-esc_proxy=&quot;8888&quot;
-
-# Configure proxy back-end interface
-esc_proxy_port=&quot;http://192.168.xx.xx:12345&quot;
-</code></pre>
 <blockquote>
 <p>Front-end automatic deployment based on Linux system <code>yum</code> 
operation, before deployment, please install and update<code>yum</code></p>
 </blockquote>
diff --git a/en-us/docs/1.2.0/user_doc/frontend-deployment.json 
b/en-us/docs/1.2.0/user_doc/frontend-deployment.json
index 8eed66c..45e3b7a 100644
--- a/en-us/docs/1.2.0/user_doc/frontend-deployment.json
+++ b/en-us/docs/1.2.0/user_doc/frontend-deployment.json
@@ -1,6 +1,6 @@
 {
   "filename": "frontend-deployment.md",
-  "__html": "<h1>frontend-deployment</h1>\n<p>The front-end has three 
deployment modes: automated deployment, manual deployment and compiled source 
deployment.</p>\n<h2>Preparations</h2>\n<h4>Download the installation 
package</h4>\n<p>Please download the latest version of the installation 
package, download address: <a 
href=\"https://dolphinscheduler.apache.org/en-us/docs/user_doc/download.html\";>download</a></p>\n<p>After
 downloading apache-dolphinscheduler-incubating-x.x.x-dolphinschedu [...]
+  "__html": "<h1>frontend-deployment</h1>\n<p>The front-end has three 
deployment modes: automated deployment, manual deployment and compiled source 
deployment.</p>\n<h2>Preparations</h2>\n<h4>Download the installation 
package</h4>\n<p>Please download the latest version of the installation 
package, download address: <a 
href=\"https://dolphinscheduler.apache.org/en-us/docs/user_doc/download.html\";>download</a></p>\n<p>After
 downloading apache-dolphinscheduler-incubating-x.x.x-dolphinschedu [...]
   "link": "/en-us/docs/1.2.0/user_doc/frontend-deployment.html",
   "meta": {}
 }
\ No newline at end of file
diff --git a/zh-cn/docs/1.2.0/user_doc/backend-deployment.html 
b/zh-cn/docs/1.2.0/user_doc/backend-deployment.html
index 97b801e..4e2d338 100644
--- a/zh-cn/docs/1.2.0/user_doc/backend-deployment.html
+++ b/zh-cn/docs/1.2.0/user_doc/backend-deployment.html
@@ -93,7 +93,7 @@ install.sh : 一键部署脚本
 <p>修改部署参数(根据自己服务器及业务情况):</p>
 </li>
 <li>
-<p>修改 <strong><a 
href="http://install.sh";>install.sh</a></strong>中的各参数,替换成自身业务所需的值</p>
+<p>修改 <code>install.sh</code>中的各参数,替换成自身业务所需的值</p>
 <ul>
 <li>
 <p>monitorServerState 开关变量,在1.0.3版本中增加,控制是否启动自启动脚本(监控master,worker状态,如果掉线会自动启动)
@@ -111,8 +111,8 @@ install.sh : 一键部署脚本
 </li>
 </ul>
 <h2>2、部署</h2>
-<p>以下两种方式任选其一部署即可,推荐自动化部署,有经验的小伙伴也可以使用源码部署</p>
-<h3>2.1 自动部署</h3>
+<p>以下两种方式任选其一部署即可,推荐二进制文件部署,有经验的小伙伴也可以使用源码部署</p>
+<h3>2.1 二进制文件部署</h3>
 <ul>
 <li>
 <p>安装zookeeper工具</p>
@@ -156,7 +156,7 @@ install.sh : 一键部署脚本
 <pre><code class="language-查看目录"> ../
     ├── bin
     ├── conf
-    |── DISCLAIMER
+    |── DISCLAIMER-WIP
     |—— install.sh
     |—— lib
     |—— LICENSE
@@ -165,6 +165,16 @@ install.sh : 一键部署脚本
     |—— script
     |—— sql
 </code></pre>
+<ul>
+<li>
+<p>安装zookeeper工具</p>
+<p><code>pip install kazoo</code></p>
+</li>
+<li>
+<p>切换到部署用户,一键部署</p>
+<p><code>sh install.sh</code></p>
+</li>
+</ul>
 <h3>2.3 系统常用启停服务(服务用途请具体参见《系统架构设计》小节)</h3>
 <ul>
 <li>
diff --git a/zh-cn/docs/1.2.0/user_doc/backend-deployment.json 
b/zh-cn/docs/1.2.0/user_doc/backend-deployment.json
index 48df998..cc90156 100644
--- a/zh-cn/docs/1.2.0/user_doc/backend-deployment.json
+++ b/zh-cn/docs/1.2.0/user_doc/backend-deployment.json
@@ -1,6 +1,6 @@
 {
   "filename": "backend-deployment.md",
-  "__html": 
"<h1>后端部署文档</h1>\n<p>后端有2种部署方式,分别为自动化部署和编译源码部署</p>\n<h2>1、准备工作</h2>\n<p>请下载最新版本的安装包,下载地址:
 <a 
href=\"https://dolphinscheduler.apache.org/en-us/docs/user_doc/download.html\";>下载</a></p>\n<h4>准备一:
 基础软件安装(必装项请自行安装)</h4>\n<ul>\n<li>PostgreSQL (8.2.15+) or Mysql (5.5+)  :  
两者任选其一即可</li>\n<li><a 
href=\"https://www.oracle.com/technetwork/java/javase/downloads/index.html\";>JDK</a>
 (1.8+) :  必装</li>\n<li>ZooKeeper (3.4.6+) :必装</li>\n<li>Hadoop (2.6+) or MinIo 
:选装, 如果需要使用到资源上传功能,可以选择Hado [...]
+  "__html": 
"<h1>后端部署文档</h1>\n<p>后端有2种部署方式,分别为自动化部署和编译源码部署</p>\n<h2>1、准备工作</h2>\n<p>请下载最新版本的安装包,下载地址:
 <a 
href=\"https://dolphinscheduler.apache.org/en-us/docs/user_doc/download.html\";>下载</a></p>\n<h4>准备一:
 基础软件安装(必装项请自行安装)</h4>\n<ul>\n<li>PostgreSQL (8.2.15+) or Mysql (5.5+)  :  
两者任选其一即可</li>\n<li><a 
href=\"https://www.oracle.com/technetwork/java/javase/downloads/index.html\";>JDK</a>
 (1.8+) :  必装</li>\n<li>ZooKeeper (3.4.6+) :必装</li>\n<li>Hadoop (2.6+) or MinIo 
:选装, 如果需要使用到资源上传功能,可以选择Hado [...]
   "link": "/zh-cn/docs/1.2.0/user_doc/backend-deployment.html",
   "meta": {}
 }
\ No newline at end of file
diff --git a/zh-cn/docs/1.2.0/user_doc/frontend-deployment.html 
b/zh-cn/docs/1.2.0/user_doc/frontend-deployment.html
index 62f5067..a161a06 100644
--- a/zh-cn/docs/1.2.0/user_doc/frontend-deployment.html
+++ b/zh-cn/docs/1.2.0/user_doc/frontend-deployment.html
@@ -22,14 +22,6 @@
 <h2>2、部署</h2>
 <p>以下两种方式任选其一部署即可,推荐自动化部署</p>
 <h3>2.1 自动化部署</h3>
-<p>在<code>dolphinscheduler-ui</code>目录下编辑安装文件<code>vi 
install-dolphinscheduler-ui.sh</code></p>
-<p>更改前端访问端口和后端代理接口地址</p>
-<pre><code># 配置前端访问端口
-esc_proxy=&quot;8888&quot;
-
-# 配置代理后端接口
-esc_proxy_port=&quot;http://192.168.xx.xx:12345&quot;
-</code></pre>
 <blockquote>
 <p>前端自动部署基于linux系统<code>yum</code>操作,部署之前请先安装更新<code>yum</code></p>
 </blockquote>
diff --git a/zh-cn/docs/1.2.0/user_doc/frontend-deployment.json 
b/zh-cn/docs/1.2.0/user_doc/frontend-deployment.json
index 425b43a..2a272cd 100644
--- a/zh-cn/docs/1.2.0/user_doc/frontend-deployment.json
+++ b/zh-cn/docs/1.2.0/user_doc/frontend-deployment.json
@@ -1,6 +1,6 @@
 {
   "filename": "frontend-deployment.md",
-  "__html": 
"<h1>前端部署文档</h1>\n<p>前端有3种部署方式,分别为自动化部署,手动部署和编译源码部署</p>\n<h2>1、准备工作</h2>\n<h4>下载安装包</h4>\n<p>请下载最新版本的安装包,下载地址:
 <a 
href=\"https://dolphinscheduler.apache.org/en-us/docs/user_doc/download.html\";>下载</a></p>\n<p>下载
 apache-dolphinscheduler-incubating-x.x.x-dolphinscheduler-front-bin.tar.gz 
后,\n解压<code>tar -zxvf 
apache-dolphinscheduler-incubating-x.x.x-dolphinscheduler-front-bin.tar.g 
./</code>后,进入<code>dolphinscheduler-ui</code>目录</p>\n<h2>2、部署</h2>\n<p>以下两种方式任选其一部署即可,推荐自动化部署</p>\
 [...]
+  "__html": 
"<h1>前端部署文档</h1>\n<p>前端有3种部署方式,分别为自动化部署,手动部署和编译源码部署</p>\n<h2>1、准备工作</h2>\n<h4>下载安装包</h4>\n<p>请下载最新版本的安装包,下载地址:
 <a 
href=\"https://dolphinscheduler.apache.org/en-us/docs/user_doc/download.html\";>下载</a></p>\n<p>下载
 apache-dolphinscheduler-incubating-x.x.x-dolphinscheduler-front-bin.tar.gz 
后,\n解压<code>tar -zxvf 
apache-dolphinscheduler-incubating-x.x.x-dolphinscheduler-front-bin.tar.g 
./</code>后,进入<code>dolphinscheduler-ui</code>目录</p>\n<h2>2、部署</h2>\n<p>以下两种方式任选其一部署即可,推荐自动化部署</p>\
 [...]
   "link": "/zh-cn/docs/1.2.0/user_doc/frontend-deployment.html",
   "meta": {}
 }
\ No newline at end of file
diff --git a/zh-cn/docs/development/release.html 
b/zh-cn/docs/development/release.html
new file mode 100644
index 0000000..baff432
--- /dev/null
+++ b/zh-cn/docs/development/release.html
@@ -0,0 +1,484 @@
+<!DOCTYPE html>
+<html lang="en">
+
+<head>
+       <meta charset="UTF-8">
+       <meta name="viewport" content="width=device-width, initial-scale=1.0, 
maximum-scale=1.0, user-scalable=no">
+       <meta name="keywords" content="release" />
+       <meta name="description" content="release" />
+       <!-- 网页标签标题 -->
+       <title>release</title>
+       <link rel="shortcut icon" href="/img/docsite.ico"/>
+       <link rel="stylesheet" href="/build/documentation.css" />
+</head>
+<body>
+       <div id="root"><div class="documentation-page" 
data-reactroot=""><header class="header-container header-container-normal"><div 
class="header-body"><a href="/zh-cn/index.html"><img class="logo" 
src="/img/hlogo_colorful.svg"/></a><div class="search search-normal"><span 
class="icon-search"></span></div><span class="language-switch 
language-switch-normal">En</span><div class="header-menu"><img 
class="header-menu-toggle" src="/img/system/menu_gray.png"/><div><ul 
class="ant-menu blackClass an [...]
+<h3>安装GPG</h3>
+<p>在<a href="https://www.gnupg.org/download/index.html";>GnuPG官网</a>下载安装包。
+GnuPG的1.x版本和2.x版本的命令有细微差别,下列说明以<code>GnuPG-2.1.23</code>版本为例。</p>
+<p>安装完成后,执行以下命令查看版本号。</p>
+<pre><code class="language-shell">gpg --version
+</code></pre>
+<h3>创建key</h3>
+<p>安装完成后,执行以下命令创建key。</p>
+<p><code>GnuPG-2.x</code>可使用:</p>
+<pre><code class="language-shell">gpg --full-gen-key
+</code></pre>
+<p><code>GnuPG-1.x</code>可使用:</p>
+<pre><code class="language-shell">gpg --gen-key
+</code></pre>
+<p>根据提示完成key:</p>
+<p><strong>注意:请使用Apache mail生成GPG的Key。</strong></p>
+<pre><code class="language-shell">gpg (GnuPG) 2.0.12; Copyright (C) 2009 Free 
Software Foundation, Inc.
+This is free software: you are free to change and redistribute it.
+There is NO WARRANTY, to the extent permitted by law.
+
+Please select what kind of key you want:
+  (1) RSA and RSA (default)
+  (2) DSA and Elgamal
+  (3) DSA (sign only)
+  (4) RSA (sign only)
+Your selection? 1
+RSA keys may be between 1024 and 4096 bits long.
+What keysize do you want? (2048) 4096
+Requested keysize is 4096 bits
+Please specify how long the key should be valid.
+        0 = key does not expire
+     &lt;n&gt;  = key expires in n days
+     &lt;n&gt;w = key expires in n weeks
+     &lt;n&gt;m = key expires in n months
+     &lt;n&gt;y = key expires in n years
+Key is valid for? (0)
+Key does not expire at all
+Is this correct? (y/N) y
+
+GnuPG needs to construct a user ID to identify your key.
+
+Real name: ${输入用户名}
+Email address: ${输入邮件地址}
+Comment: ${输入注释}
+You selected this USER-ID:
+   "${输入的用户名} (${输入的注释}) &lt;${输入的邮件地址}&gt;"
+
+Change (N)ame, (C)omment, (E)mail or (O)kay/(Q)uit? O
+You need a Passphrase to protect your secret key. # 输入密码
+</code></pre>
+<h3>查看生成的key</h3>
+<pre><code class="language-shell">gpg --list-keys
+</code></pre>
+<p>执行结果:</p>
+<pre><code class="language-shell">pub   4096R/85E11560 2019-11-15
+uid                  ${用户名} (${注释}) &lt;{邮件地址}&gt;
+sub   4096R/A63BC462 2019-11-15
+</code></pre>
+<p>其中85E11560为公钥ID。</p>
+<h3>将公钥同步到服务器</h3>
+<p>命令如下:</p>
+<pre><code class="language-shell">gpg --keyserver 
hkp://pool.sks-keyservers.net --send-key 85E11560
+</code></pre>
+<p><code>pool.sks-keyservers.net</code>为随意挑选的<a 
href="https://sks-keyservers.net/status/";>公钥服务器</a>,每个服务器之间是自动同步的,选任意一个即可。</p>
+<h2>发布Apache Maven中央仓库</h2>
+<h3>设置settings.xml文件</h3>
+<p>将以下模板添加到 <code>~/.m2/settings.xml</code>中,所有密码需要加密后再填入。
+加密设置可参考<a 
href="http://maven.apache.org/guides/mini/guide-encryption.html";>这里</a>。</p>
+<pre><code class="language-xml"><span class="hljs-tag">&lt;<span 
class="hljs-name">settings</span>&gt;</span>
+  <span class="hljs-tag">&lt;<span class="hljs-name">servers</span>&gt;</span>
+    <span class="hljs-tag">&lt;<span class="hljs-name">server</span>&gt;</span>
+      <span class="hljs-tag">&lt;<span 
class="hljs-name">id</span>&gt;</span>apache.snapshots.https<span 
class="hljs-tag">&lt;/<span class="hljs-name">id</span>&gt;</span>
+      <span class="hljs-tag">&lt;<span 
class="hljs-name">username</span>&gt;</span> <span class="hljs-comment">&lt;!-- 
APACHE LDAP 用户名 --&gt;</span> <span class="hljs-tag">&lt;/<span 
class="hljs-name">username</span>&gt;</span>
+      <span class="hljs-tag">&lt;<span 
class="hljs-name">password</span>&gt;</span> <span class="hljs-comment">&lt;!-- 
APACHE LDAP 加密后的密码 --&gt;</span> <span class="hljs-tag">&lt;/<span 
class="hljs-name">password</span>&gt;</span>
+    <span class="hljs-tag">&lt;/<span 
class="hljs-name">server</span>&gt;</span>
+    <span class="hljs-tag">&lt;<span class="hljs-name">server</span>&gt;</span>
+      <span class="hljs-tag">&lt;<span 
class="hljs-name">id</span>&gt;</span>apache.releases.https<span 
class="hljs-tag">&lt;/<span class="hljs-name">id</span>&gt;</span>
+      <span class="hljs-tag">&lt;<span 
class="hljs-name">username</span>&gt;</span> <span class="hljs-comment">&lt;!-- 
APACHE LDAP 用户名 --&gt;</span> <span class="hljs-tag">&lt;/<span 
class="hljs-name">username</span>&gt;</span>
+      <span class="hljs-tag">&lt;<span 
class="hljs-name">password</span>&gt;</span> <span class="hljs-comment">&lt;!-- 
APACHE LDAP 加密后的密码 --&gt;</span> <span class="hljs-tag">&lt;/<span 
class="hljs-name">password</span>&gt;</span>
+    <span class="hljs-tag">&lt;/<span 
class="hljs-name">server</span>&gt;</span>
+  <span class="hljs-tag">&lt;/<span class="hljs-name">servers</span>&gt;</span>
+<span class="hljs-tag">&lt;/<span class="hljs-name">settings</span>&gt;</span>
+</code></pre>
+<h3>更新版本说明</h3>
+<pre><code>https://github.com/apache/incubator-dolphinscheduler/blob/dev/RELEASE-NOTES.md
+</code></pre>
+<h3>创建发布分支</h3>
+<p>假设从github下载的DolphinScheduler源代码在<code>~/incubator-dolphinscheduler/</code>目录;假设即将发布的版本为<code>${RELEASE.VERSION}</code>。
+创建<code>${RELEASE.VERSION}-release</code>分支,接下来的操作都在该分支进行。</p>
+<pre><code class="language-shell">cd ~/incubator-dolphinscheduler/
+git pull
+git checkout -b ${RELEASE.VERSION}-release
+git push origin ${RELEASE.VERSION}-release
+</code></pre>
+<h3>发布预校验</h3>
+<pre><code class="language-shell">mvn release:prepare -Prelease 
-Darguments="-DskipTests" -DautoVersionSubmodules=true -DdryRun=true 
-Dusername=${Github用户名}
+</code></pre>
+<p>-Prelease: 选择release的profile,这个profile会打包所有源码、jar文件以及可执行二进制包。</p>
+<p>-DautoVersionSubmodules=true:作用是发布过程中版本号只需要输入一次,不必为每个子模块都输入一次。</p>
+<p>-DdryRun=true:演练,即不产生版本号提交,不生成新的tag。</p>
+<h3>准备发布</h3>
+<p>首先清理发布预校验本地信息。</p>
+<pre><code class="language-shell">mvn release:clean
+</code></pre>
+<p>然后准备执行发布。</p>
+<pre><code class="language-shell">mvn release:prepare -Prelease 
-Darguments="-DskipTests" -DautoVersionSubmodules=true -DpushChanges=false 
-Dusername=${Github用户名}
+</code></pre>
+<p>和上一步演练的命令基本相同,去掉了-DdryRun=true参数。</p>
+<p>-DpushChanges=false:不要将修改后的版本号和tag自动提交至Github。</p>
+<p>将本地文件检查无误后,提交至github。</p>
+<pre><code class="language-shell">git push
+git push origin --tags
+</code></pre>
+<h3>部署发布</h3>
+<pre><code class="language-shell">mvn release:perform -Prelease 
-Darguments="-DskipTests" -DautoVersionSubmodules=true -Dusername=${Github用户名}
+</code></pre>
+<p>执行完该命令后,待发布版本会自动上传到Apache的临时筹备仓库(staging repository)。
+访问https://repository.apache.org/#stagingRepositories, 
使用Apache的LDAP账户登录后,就会看到上传的版本,<code>Repository</code>列的内容即为${STAGING.REPOSITORY}。
+点击<code>Close</code>来告诉Nexus这个构建已经完成,只有这样该版本才是可用的。
+如果电子签名等出现问题,<code>Close</code>会失败,可以通过<code>Activity</code>查看失败信息。</p>
+<h2>发布Apache SVN仓库</h2>
+<h3>检出dolphinscheduler发布目录</h3>
+<p>如无本地工作目录,则先创建本地工作目录。</p>
+<pre><code class="language-shell">mkdir -p ~/ds_svn/dev/
+cd ~/ds_svn/dev/
+</code></pre>
+<p>创建完毕后,从Apache SVN检出dolphinscheduler发布目录。</p>
+<pre><code class="language-shell">svn --username=${APACHE LDAP 用户名} co 
https://dist.apache.org/repos/dist/dev/incubator/dolphinscheduler
+cd ~/ds_svn/dev/dolphinscheduler
+</code></pre>
+<h3>添加gpg公钥</h3>
+<p>仅第一次部署的账号需要添加,只要<code>KEYS</code>中包含已经部署过的账户的公钥即可。</p>
+<pre><code class="language-shell">gpg -a --export ${GPG用户名} &gt;&gt; KEYS
+</code></pre>
+<h3>将待发布的内容添加至SVN目录</h3>
+<p>创建版本号目录。</p>
+<pre><code class="language-shell">mkdir -p 
~/ds_svn/dev/dolphinscheduler/${RELEASE.VERSION}
+cd ~/ds_svn/dev/dolphinscheduler/${RELEASE.VERSION}
+</code></pre>
+<p>将源码包和二进制包添加至SVN工作目录。</p>
+<pre><code class="language-shell">cp -f 
~/incubator-dolphinscheduler/dolphinscheduler-dist/dolphinscheduler-src/target/*.zip
 ~/ds_svn/dev/dolphinscheduler/${RELEASE.VERSION}
+cp -f 
~/incubator-dolphinscheduler/dolphinscheduler-dist/dolphinscheduler-src/target/*.zip.asc
 ~/ds_svn/dev/dolphinscheduler/${RELEASE.VERSION}
+cp -f 
~/incubator-dolphinscheduler/dolphinscheduler-dist/dolphinscheduler-backend/target/*.tar.gz
 ~/ds_svn/dev/dolphinscheduler/${RELEASE.VERSION}
+cp -f 
~/incubator-dolphinscheduler/dolphinscheduler-dist/dolphinscheduler-backend/target/*.tar.gz.asc
 ~/ds_svn/dev/dolphinscheduler/${RELEASE.VERSION}
+cp -f 
~/incubator-dolphinscheduler/dolphinscheduler-dist/dolphinscheduler-front/target/*.tar.gz
 ~/ds_svn/dev/dolphinscheduler/${RELEASE.VERSION}
+cp -f 
~/incubator-dolphinscheduler/dolphinscheduler-dist/dolphinscheduler-front/target/*.tar.gz.asc
 ~/ds_svn/dev/dolphinscheduler/${RELEASE.VERSION}
+</code></pre>
+<h3>生成文件签名</h3>
+<pre><code class="language-shell">shasum -a 512 
apache-dolphinscheduler-incubating-${RELEASE.VERSION}-src.zip &gt;&gt; 
apache-dolphinscheduler-incubating-${RELEASE.VERSION}-src.zip.sha512
+shasum -b -a 512 
apache-dolphinscheduler-incubating-${RELEASE.VERSION}-dolphinscheduler-backend-bin.tar.gz
 &gt;&gt; 
apache-dolphinscheduler-incubating-${RELEASE.VERSION}-dolphinscheduler-backend-bin.tar.gz.sha512
+shasum -b -a 512 
apache-dolphinscheduler-incubating-${RELEASE.VERSION}-dolphinscheduler-front-bin.tar.gz
 &gt;&gt; 
apache-dolphinscheduler-incubating-${RELEASE.VERSION}-dolphinscheduler-front-bin.tar.gz.sha512
+</code></pre>
+<h3>提交Apache SVN</h3>
+<pre><code class="language-shell">svn add *
+svn --username=${APACHE LDAP 用户名} commit -m "release ${RELEASE.VERSION}"
+</code></pre>
+<h2>检查发布结果</h2>
+<h3>检查sha512哈希</h3>
+<pre><code class="language-shell">shasum -c 
apache-dolphinscheduler-incubating-${RELEASE.VERSION}-src.zip.sha512
+shasum -c 
apache-dolphinscheduler-incubating-${RELEASE.VERSION}-dolphinscheduler-backend-bin.tar.gz.sha512
+shasum -c 
apache-dolphinscheduler-incubating-${RELEASE.VERSION}-dolphinscheduler-front-bin.tar.gz.sha512
+</code></pre>
+<h3>检查gpg签名</h3>
+<p>首先导入发布人公钥。从svn仓库导入KEYS到本地环境。(发布版本的人不需要再导入,帮助做验证的人需要导入,用户名填发版人的即可)</p>
+<pre><code class="language-shell">curl 
https://dist.apache.org/repos/dist/dev/incubator/dolphinscheduler/KEYS &gt;&gt; 
KEYS
+gpg --import KEYS
+gpg --edit-key "${发布人的gpg用户名}"
+<span class="hljs-meta">  &gt;</span><span class="bash"> trust</span>
+
+Please decide how far you trust this user to correctly verify other users' keys
+(by looking at passports, checking fingerprints from different sources, etc.)
+
+  1 = I don't know or won't say
+  2 = I do NOT trust
+  3 = I trust marginally
+  4 = I trust fully
+  5 = I trust ultimately
+  m = back to the main menu
+
+Your decision? 5
+<span class="hljs-meta">
+  &gt;</span><span class="bash"> save</span>
+</code></pre>
+<p>然后进行gpg签名检查。</p>
+<pre><code class="language-shell">gpg --verify 
apache-dolphinscheduler-incubating-${RELEASE.VERSION}-src.zip.asc 
apache-dolphinscheduler-incubating-${RELEASE.VERSION}-src.zip
+gpg --verify 
apache-dolphinscheduler-incubating-${RELEASE.VERSION}-dolphinscheduler-backend-bin.tar.gz.asc
 
apache-dolphinscheduler-incubating-${RELEASE.VERSION}-dolphinscheduler-backend-bin.tar.gz
+gpg --verify 
apache-dolphinscheduler-incubating-${RELEASE.VERSION}-dolphinscheduler-front-bin.tar.gz.asc
 
apache-dolphinscheduler-incubating-${RELEASE.VERSION}-dolphinscheduler-front-bin.tar.gz
+</code></pre>
+<h3>检查发布文件内容</h3>
+<h4>检查源码包的文件内容</h4>
+<p>解压缩<code>apache-dolphinscheduler-incubating-${RELEASE.VERSION}-src.zip</code>,进行如下检查:</p>
+<ul>
+<li>检查源码包是否包含由于包含不必要文件,致使tarball过于庞大</li>
+<li>文件夹包含单词<code>incubating</code></li>
+<li>存在<code>DISCLAIMER</code>文件</li>
+<li>存在<code>LICENSE</code>和<code>NOTICE</code>文件</li>
+<li>只存在文本文件,不存在二进制文件</li>
+<li>所有文件的开头都有ASF许可证</li>
+<li>能够正确编译,单元测试可以通过 (mvn install)</li>
+<li>版本内容与Github上tag的内容相符 (diff -r a verify_dir tag_dir)</li>
+<li>检查是否有多余文件或文件夹,例如空文件夹等</li>
+</ul>
+<h4>检查二进制包的文件内容</h4>
+<p>解压缩<code>apache-dolphinscheduler-incubating-${RELEASE.VERSION}-dolphinscheduler-backend-bin.tar.gz</code>和<code>apache-dolphinscheduler-incubating-${RELEASE.VERSION}-dolphinscheduler-front-bin.tar.gz</code>
+进行如下检查:</p>
+<ul>
+<li>文件夹包含单词<code>incubating</code></li>
+<li>存在<code>DISCLAIMER</code>文件</li>
+<li>存在<code>LICENSE</code>和<code>NOTICE</code>文件</li>
+<li>所有文本文件开头都有ASF许可证</li>
+<li>检查第三方依赖许可证:
+<ul>
+<li>第三方依赖的许可证兼容</li>
+<li>所有第三方依赖的许可证都在<code>LICENSE</code>文件中声名</li>
+<li>依赖许可证的完整版全部在<code>license</code>目录</li>
+<li>如果依赖的是Apache许可证并且存在<code>NOTICE</code>文件,那么这些<code>NOTICE</code>文件也需要加入到版本的<code>NOTICE</code>文件中</li>
+</ul>
+</li>
+</ul>
+<p>全部的检查列表参见<a 
href="https://cwiki.apache.org/confluence/display/INCUBATOR/Incubator+Release+Checklist";>这里</a>。</p>
+<h2>发起投票</h2>
+<h3>投票阶段</h3>
+<ol>
+<li>
+<p>DolphinScheduler社区投票,发起投票邮件到<code>[email protected]</code>。PPMC需要先按照文档检查版本的正确性,然后再进行投票。
+经过至少72小时并统计到3个<code>+1 PPMC member</code>票后,即可进入下一阶段的投票。</p>
+</li>
+<li>
+<p>Apache社区投票,发起投票邮件到<code>[email protected]</code>。经过至少72小时并统计到3个<code>+1
 binding</code>票后(只有IPMC的票才是binding),即可进行正式发布。</p>
+</li>
+<li>
+<p>宣布投票结果,发起投票结果邮件到<code>[email protected]</code>。</p>
+</li>
+</ol>
+<h3>投票模板</h3>
+<ol>
+<li>DolphinScheduler社区投票模板</li>
+</ol>
+<p>注意: 在社区投票过程中,需要邀请所有mentor参加投票。</p>
+<p>标题:</p>
+<pre><code>[VOTE] Release Apache DolphinScheduler (Incubating) 
${RELEASE.VERSION}
+</code></pre>
+<p>正文:</p>
+<pre><code>Hello DolphinScheduler Community,
+
+This is a call for vote to release Apache DolphinScheduler (Incubating) 
version ${RELEASE.VERSION}
+
+Release notes:
+https://github.com/apache/incubator-dolphinscheduler/blob/${RELEASE.VERSION}/ReleaseNotes.md
+
+The release candidates:
+https://dist.apache.org/repos/dist/dev/incubator/dolphinscheduler/${RELEASE.VERSION}/
+
+Maven 2 staging repository:
+https://repository.apache.org/content/repositories/${STAGING.REPOSITORY}/org/apache/dolphinscheduler/
+
+Git tag for the release:
+https://github.com/apache/incubator-dolphinscheduler/tree/${RELEASE.VERSION}
+
+Release Commit ID:
+https://github.com/apache/incubator-dolphinscheduler/commit/xxxxxxxxxxxxxxxxxxxxxxx
+
+Keys to verify the Release Candidate:
+https://dist.apache.org/repos/dist/dev/incubator/dolphinscheduler/KEYS
+
+Look at here for how to verify this release candidate:
+https://github.com/apache/incubator-dolphinscheduler/blob/1.2.0-release/README.md
+
+The vote will be open for at least 72 hours or until necessary number of votes 
are reached.
+
+Please vote accordingly:
+
+[ ] +1 approve
+
+[ ] +0 no opinion
+
+[ ] -1 disapprove with the reason
+
+Checklist for reference:
+
+[ ] Download links are valid.
+
+[ ] Checksums and PGP signatures are valid.
+
+[ ] Source code artifacts have correct names matching the current release.
+
+[ ] LICENSE and NOTICE files are correct for each DolphinScheduler repo.
+
+[ ] All files have license headers if necessary.
+
+[ ] No compiled archives bundled in source archive.
+
+More detail checklist  please refer:
+https://cwiki.apache.org/confluence/display/INCUBATOR/Incubator+Release+Checklist
+</code></pre>
+<ol start="2">
+<li>宣布投票结果模板:</li>
+</ol>
+<p>正文:</p>
+<pre><code>The vote to release Apache DolphinScheduler (Incubating) 
${RELEASE.VERSION} has passed.Here is the vote result,
+
+7 PPMC member +1 votes:
+
+xxx (mentor)
+xxx
+xxx (mentor)
+xxx
+xxx
+xxx (mentor)
+xxx
+
+1 community +1 vote:
+xxx
+
+Thanks everyone for taking time to check this release and help us.
+</code></pre>
+<ol start="3">
+<li>Apache社区投票邮件模板:</li>
+</ol>
+<p>标题:</p>
+<pre><code>[VOTE] Release Apache DolphinScheduler (Incubating) 
${RELEASE.VERSION}
+</code></pre>
+<p>正文:</p>
+<pre><code>Hello everyone,
+
+This is a call for vote to release Apache DolphinScheduler (Incubating) 
version ${RELEASE.VERSION}.
+
+The Apache DolphinScheduler community has voted on and approved a proposal to 
release
+Apache DolphinScheduler (Incubating) version ${RELEASE.VERSION}.
+
+We now kindly request the Incubator IPMC members review and vote on this 
incubator release.
+
+Dolphin Scheduler is a distributed and easy-to-expand visual DAG workflow 
scheduling system,
+dedicated to solving the complex dependencies in data processing, making the 
scheduling system out of the box for data processing.
+
+DolphinScheduler community vote and result threads:
+https://lists.apache.org/thread.html/xxxxxxxxxxxxxxxxxxxxxxx
+
+https://lists.apache.org/thread.html/xxxxxxxxxxxxxxxxxxxxxxx
+
+Release notes:
+https://github.com/apache/incubator-dolphinscheduler/blob/${RELEASE.VERSION}/ReleaseNotes.md
+
+The release candidates:
+https://dist.apache.org/repos/dist/dev/incubator/dolphinscheduler/${RELEASE.VERSION}/
+
+Maven 2 staging repository:
+https://repository.apache.org/content/repositories/${STAGING.REPOSITORY}/org/apache/dolphinscheduler/
+
+Git tag for the release:
+https://github.com/apache/incubator-dolphinscheduler/tree/${RELEASE.VERSION}
+
+Release Commit ID:
+https://github.com/apache/incubator-dolphinscheduler/commit/xxxxxxxxxxxxxxxxxxxxxxx
+
+Keys to verify the Release Candidate:
+https://dist.apache.org/repos/dist/dev/incubator/dolphinscheduler/KEYS
+
+Look at here for how to verify this release candidate:
+https://github.com/apache/incubator-dolphinscheduler/blob/1.2.0-release/README.md
+
+The vote will be open for at least 72 hours or until necessary number of votes 
are reached.
+Please vote accordingly:
+
+[ ] +1 approve
+
+[ ] +0 no opinion
+
+[ ] -1 disapprove with the reason
+
+Checklist for reference:
+
+[ ] Download links are valid.
+
+[ ] Checksums and PGP signatures are valid.
+
+[ ] Source code artifacts have correct names matching the current release.
+
+[ ] LICENSE and NOTICE files are correct for each DolphinScheduler repo.
+
+[ ] All files have license headers if necessary.
+
+[ ] No compiled archives bundled in source archive.
+
+More detail checklist  please refer:
+https://cwiki.apache.org/confluence/display/INCUBATOR/Incubator+Release+Checklist
+
+The following votes are carried over from DolphinScheduler dev mailing list,
+
++1 binding, xxx
++1 binding, xxx
+
++1 non-binding, xxx
++1 non-binding, xxx
+</code></pre>
+<ol start="4">
+<li>宣布投票结果模板:</li>
+</ol>
+<p><strong>注意:计算投票结果时,社区投票结果也需要包含在内。</strong></p>
+<p>正文:</p>
+<pre><code>We’ve received 3 +1 binding votes and one +1 non-binding vote:
+
++1 binding, xxx
++1 binding, xxx
++1 binding, xxx
+
++1 non-binding, xxx
+
+Thank you everyone for taking the time to review the release and help us.
+I will process to publish the release and send ANNOUNCE.
+</code></pre>
+<h2>完成发布</h2>
+<ol>
+<li>将源码和二进制包从svn的dev目录移动到release目录</li>
+</ol>
+<pre><code class="language-shell">svn mv 
https://dist.apache.org/repos/dist/dev/incubator/dolphinscheduler/${RELEASE.VERSION}
 https://dist.apache.org/repos/dist/release/incubator/dolphinscheduler/
+</code></pre>
+<ol start="2">
+<li>
+<p>在Apache Staging仓库找到DolphinScheduler并点击<code>Release</code></p>
+</li>
+<li>
+<p>更新下载页面</p>
+</li>
+</ol>
+<pre><code>https://dolphinscheduler.apache.org/en-us/docs/user_doc/download.html
+https://dolphinscheduler.apache.org/zh-cn/docs/user_doc/download.html
+</code></pre>
+<ol start="4">
+<li>发送邮件到<code>[email protected]</code>和<code>[email protected]</code>通知完成版本发布。</li>
+</ol>
+<p>通知邮件模板:</p>
+<p>标题:</p>
+<pre><code>[ANNOUNCE] Release Apache DolphinScheduler (Incubating) 
${RELEASE.VERSION}
+</code></pre>
+<p>正文:</p>
+<pre><code>Hi all,
+
+We are glad to announce the release of Apache DolphinScheduler(incubating) 
${RELEASE.VERSION}. Once again I would like to express my thanks to your help.
+
+Dolphin Scheduler is a distributed and easy-to-expand visual DAG workflow 
scheduling system,
+dedicated to solving the complex dependencies in data processing, making the 
scheduling system out of the box for data processing.
+
+
+Download Links: 
http://dolphinscheduler.apache.org/en-us/docs/user_doc/download.html
+
+Release Notes: 
https://github.com/apache/incubator-dolphinscheduler/blob/${RELEASE.VERSION}/ReleaseNotes.md
+
+Website: https://dolphinscheduler.apache.org/
+
+DolphinScheduler Resources:
+- Issue: https://github.com/apache/incubator-dolphinscheduler/issues/
+- Mailing list: [email protected]
+- Documents: 
https://github.com/apache/incubator-dolphinscheduler/blob/${RELEASE.VERSION}/README.md
+
+</code></pre>
+</div></section><footer class="footer-container"><div class="footer-body"><img 
src="/img/ds_gray.svg"/><div class="cols-container"><div class="col 
col-12"><h3>Disclaimer</h3><p>Apache DolphinScheduler (incubating) is an effort 
undergoing incubation at The Apache Software Foundation (ASF), sponsored by 
Incubator. 
+Incubation is required of all newly accepted projects until a further review 
indicates 
+that the infrastructure, communications, and decision making process have 
stabilized in a manner consistent with other successful ASF projects. 
+While incubation status is not necessarily a reflection of the completeness or 
stability of the code, 
+it does indicate that the project has yet to be fully endorsed by the 
ASF.</p></div><div class="col col-6"><dl><dt>文档</dt><dd><a 
href="/zh-cn/docs/developer_guide/architecture-design.html" 
target="_self">概览</a></dd><dd><a href="/zh-cn/docs/user_doc/quick-start.html" 
target="_self">快速开始</a></dd><dd><a 
href="/zh-cn/docs/development/developers.html" 
target="_self">开发者指南</a></dd></dl></div><div class="col 
col-6"><dl><dt>ASF</dt><dd><a href="http://www.apache.org"; 
target="_self">基金会</a></dd>< [...]
+       <script 
src="https://f.alicdn.com/react/15.4.1/react-with-addons.min.js";></script>
+       <script 
src="https://f.alicdn.com/react/15.4.1/react-dom.min.js";></script>
+       <script>
+               window.rootPath = '';
+  </script>
+       <script src="/build/documentation.js"></script>
+</body>
+</html>
\ No newline at end of file
diff --git a/zh-cn/docs/development/release.json 
b/zh-cn/docs/development/release.json
new file mode 100644
index 0000000..d094fac
--- /dev/null
+++ b/zh-cn/docs/development/release.json
@@ -0,0 +1,6 @@
+{
+  "filename": "release.md",
+  "__html": "<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 
class=\"languag [...]
+  "link": "/zh-cn/docs/development/release.html",
+  "meta": {}
+}
\ No newline at end of file

Reply via email to