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-hugegraph-doc.git
The following commit(s) were added to refs/heads/asf-site by this push:
new ac419b6b translate validate-release.md to English (#164)
ac419b6b is described below
commit ac419b6b0bcf57fa26d9af11c4c10fc86436a355
Author: imbajin <[email protected]>
AuthorDate: Sat Dec 31 06:46:01 2022 +0000
translate validate-release.md to English (#164)
* translate validate-release.md to English
* Update validate-release.md
Co-authored-by: yuanbingze <[email protected]>
Co-authored-by: imbajin <[email protected]>
4003b76d6eef5828c5a5bbda318d9f686da39d76
---
css/shortcodes.css | 4 +-
docs/_print/index.html | 12 ++--
docs/contribution-guidelines/_print/index.html | 12 ++--
docs/contribution-guidelines/index.xml | 70 +++++++++++-----------
.../validate-release/index.html | 36 +++++------
docs/index.xml | 70 +++++++++++-----------
en/sitemap.xml | 2 +-
sitemap.xml | 2 +-
8 files changed, 101 insertions(+), 107 deletions(-)
diff --git a/css/shortcodes.css b/css/shortcodes.css
index 0aa1c0f8..2fc3093a 100644
--- a/css/shortcodes.css
+++ b/css/shortcodes.css
@@ -1,2 +1,2 @@
-@import "shortcodes/tabbed-pane.css";
-@import "shortcodes/cards-pane.css";
+@import "shortcodes/tabbed-pane.css";
+@import "shortcodes/cards-pane.css";
diff --git a/docs/_print/index.html b/docs/_print/index.html
index 46f51897..816e4e98 100644
--- a/docs/_print/index.html
+++ b/docs/_print/index.html
@@ -6598,18 +6598,18 @@ HugeGraph目前采用EdgeCut的分区方案。</p><h3 id=3-vertexid-策略>3. Ve
</span></span><span style=display:flex><span>git rebase -i master
</span></span></code></pre></div></blockquote><p>And push it to GitHub fork
repo again:</p><div class=highlight><pre tabindex=0
style=background-color:#f8f8f8;-moz-tab-size:4;-o-tab-size:4;tab-size:4><code
class=language-shell data-lang=shell><span style=display:flex><span><span
style=color:#8f5902;font-style:italic># force push the local commit to fork
repo</span>
</span></span><span style=display:flex><span>git push -f origin
bugfix-branch:bugfix-branch
-</span></span></code></pre></div><p>GitHub will automatically update the Pull
Request after we push it, just wait for code review.</p></div><div
class=td-content style=page-break-before:always><h1
id=pg-dc89ef117bed0b0ef3c6487f9a6a8bd0>9.2 - Subscribe Mailing Lists</h1><p>It
is highly recommended to subscribe to the development mailing list to keep
up-to-date with the community.</p><p>In the process of using HugeGraph, if you
have any questions or ideas, suggestions, you can participate [...]
+</span></span></code></pre></div><p>GitHub will automatically update the Pull
Request after we push it, just wait for code review.</p></div><div
class=td-content style=page-break-before:always><h1
id=pg-dc89ef117bed0b0ef3c6487f9a6a8bd0>9.2 - Subscribe Mailing Lists</h1><p>It
is highly recommended to subscribe to the development mailing list to keep
up-to-date with the community.</p><p>In the process of using HugeGraph, if you
have any questions or ideas, suggestions, you can participate [...]
</span></span><span style=display:flex><span>curl xxx >> PK
</span></span><span style=display:flex><span>gpg --import PK
-</span></span><span style=display:flex><span><span
style=color:#8f5902;font-style:italic># 1.2 等待响应后输入 trust 表示信任 tom 的公钥
(其他人名类似)</span>
+</span></span><span style=display:flex><span><span
style=color:#8f5902;font-style:italic># 1.2 Enter trust after waiting for the
response to trust Tom's public key (other names are similar)</span>
</span></span><span style=display:flex><span>gpg -edit-key tom
</span></span><span style=display:flex><span>
-</span></span><span style=display:flex><span><span
style=color:#8f5902;font-style:italic># 2. 检查签名 (可用 0x03 章节的第 ⑧ 步的 for
循环脚本批量遍历)</span>
+</span></span><span style=display:flex><span><span
style=color:#8f5902;font-style:italic># 2. Check the signature (you can use the
for loop script in step ⑧ of Chapter 0x03 to traverse in batches)</span>
</span></span><span style=display:flex><span>gpg --verify xx.asc
xxx-source.tar.gz
-</span></span><span style=display:flex><span>gpg --verify xx.asc
xxx-binary.tar.gz <span style=color:#8f5902;font-style:italic># 注: 我们目前没有
binary 后缀</span>
-</span></span></code></pre></div><p>先确认了整体的完整性/一致性, 然后接下来确认具体的内容
(<strong>关键</strong>)</p><h4 id=3-检查压缩包内容>3. 检查压缩包内容</h4><p>这里分源码包 + 二进制包两个方面,
源码包更为严格, 挑核心的部分说 (完整的列表参考官方 <a
href=https://cwiki.apache.org/confluence/display/INCUBATOR/Incubator+Release+Checklist>Wiki</a>,
比较长)</p><p>首先我们需要从 apache 官方的 <code>release-candidate</code> 地址下载包到本地 (地址:
<code>dist.apache.org/repos/dist/dev/hugegraph/</code>)</p><h5 id=a-源码包>A.
源码包</h5><p>解压 <code>xxx-hugegraph-source.tar.gz</code>后, 进行如下检查:</p><o [...]
+</span></span><span style=display:flex><span>gpg --verify xx.asc
xxx-binary.tar.gz <span style=color:#8f5902;font-style:italic># Note: We
currently do not have a binary suffix</span>
+</span></span></code></pre></div><p>First confirm the overall
integrity/consistency, and then confirm the specific content
(<strong>key</strong>)</p><h4 id=3-check-the-archive-contents>3. Check the
archive contents</h4><p>Here it is divided into two aspects: source code
package + binary package, The source code package is more strict, it can be
said that the core part (Because it is longer,For a complete list refer to the
official <a href=https://cwiki.apache.org/confluence/display/INCUB [...]
</span></span><span style=display:flex><span>mvn clean <span
style=color:#204a87>test</span> -Dcheckstyle.skip<span
style=color:#ce5c00;font-weight:700>=</span><span
style=color:#204a87>false</span>
-</span></span></code></pre></div><h5 id=b-二进制包>B. 二进制包</h5><p>解压
<code>xxx-hugegraph.tar.gz</code>后, 进行如下检查:</p><ol><li>文件夹都带有
<code>incubating</code></li><li>存在 <code>LICENSE</code> + <code>NOTICE</code>
文件并且内容正常</li><li>通过 gpg 命令确认每个文件的签名正常</li></ol><p><strong>注:</strong>
如果二进制包里面引入了第三方依赖, 则需要更新 LICENSE, 加入第三方依赖的 LICENSE; 若第三方依赖 LICENSE 是 Apache 2.0,
且对应的项目中包含了 NOTICE, 则还需要更新我们的 NOTICE 文件</p><h4 id=4-检查官网以及-github-等页面>4. 检查官网以及
github 等页面</h4><ol><li>确保官网至少满足 <a href=https://whimsy.apa [...]
+</span></span></code></pre></div><h5 id=b-binary-package>B. binary
package</h5><p>After decompressing <code>xxx-hugegraph.tar.gz</code>, perform
the following checks:</p><ol><li>folders with
<code>incubating</code></li><li><code>LICENSE</code> and <code>NOTICE</code>
file exists and the content is normal</li><li>Confirm that the signature of
each file is normal through the gpg command</li></ol><p><strong>Note:</strong>
If a third-party dependency is introduced in the binary package, you [...]
<script
src=https://cdn.jsdelivr.net/npm/[email protected]/dist/js/bootstrap.min.js
integrity="sha512-UR25UO94eTnCVwjbXozyeVd6ZqpaAE9naiEUBK/A+QDbfSTQFhPGj5lOR6d8tsgbBk84Ggb5A3EkjsOgPRPcKA=="
crossorigin=anonymous></script>
<script src=/js/tabpane-persist.js></script>
<script
src=/js/main.min.aa9f4c5dae6a98b2c46277f4c56f1673a2b000d1756ce4ffae93784cab25e6d5.js
integrity="sha256-qp9MXa5qmLLEYnf0xW8Wc6KwANF1bOT/rpN4TKsl5tU="
crossorigin=anonymous></script>
diff --git a/docs/contribution-guidelines/_print/index.html
b/docs/contribution-guidelines/_print/index.html
index f8048faa..0544d466 100644
--- a/docs/contribution-guidelines/_print/index.html
+++ b/docs/contribution-guidelines/_print/index.html
@@ -46,18 +46,18 @@
</span></span><span style=display:flex><span>git rebase -i master
</span></span></code></pre></div></blockquote><p>And push it to GitHub fork
repo again:</p><div class=highlight><pre tabindex=0
style=background-color:#f8f8f8;-moz-tab-size:4;-o-tab-size:4;tab-size:4><code
class=language-shell data-lang=shell><span style=display:flex><span><span
style=color:#8f5902;font-style:italic># force push the local commit to fork
repo</span>
</span></span><span style=display:flex><span>git push -f origin
bugfix-branch:bugfix-branch
-</span></span></code></pre></div><p>GitHub will automatically update the Pull
Request after we push it, just wait for code review.</p></div><div
class=td-content style=page-break-before:always><h1
id=pg-dc89ef117bed0b0ef3c6487f9a6a8bd0>2 - Subscribe Mailing Lists</h1><p>It is
highly recommended to subscribe to the development mailing list to keep
up-to-date with the community.</p><p>In the process of using HugeGraph, if you
have any questions or ideas, suggestions, you can participate in [...]
+</span></span></code></pre></div><p>GitHub will automatically update the Pull
Request after we push it, just wait for code review.</p></div><div
class=td-content style=page-break-before:always><h1
id=pg-dc89ef117bed0b0ef3c6487f9a6a8bd0>2 - Subscribe Mailing Lists</h1><p>It is
highly recommended to subscribe to the development mailing list to keep
up-to-date with the community.</p><p>In the process of using HugeGraph, if you
have any questions or ideas, suggestions, you can participate in [...]
</span></span><span style=display:flex><span>curl xxx >> PK
</span></span><span style=display:flex><span>gpg --import PK
-</span></span><span style=display:flex><span><span
style=color:#8f5902;font-style:italic># 1.2 等待响应后输入 trust 表示信任 tom 的公钥
(其他人名类似)</span>
+</span></span><span style=display:flex><span><span
style=color:#8f5902;font-style:italic># 1.2 Enter trust after waiting for the
response to trust Tom's public key (other names are similar)</span>
</span></span><span style=display:flex><span>gpg -edit-key tom
</span></span><span style=display:flex><span>
-</span></span><span style=display:flex><span><span
style=color:#8f5902;font-style:italic># 2. 检查签名 (可用 0x03 章节的第 ⑧ 步的 for
循环脚本批量遍历)</span>
+</span></span><span style=display:flex><span><span
style=color:#8f5902;font-style:italic># 2. Check the signature (you can use the
for loop script in step ⑧ of Chapter 0x03 to traverse in batches)</span>
</span></span><span style=display:flex><span>gpg --verify xx.asc
xxx-source.tar.gz
-</span></span><span style=display:flex><span>gpg --verify xx.asc
xxx-binary.tar.gz <span style=color:#8f5902;font-style:italic># 注: 我们目前没有
binary 后缀</span>
-</span></span></code></pre></div><p>先确认了整体的完整性/一致性, 然后接下来确认具体的内容
(<strong>关键</strong>)</p><h4 id=3-检查压缩包内容>3. 检查压缩包内容</h4><p>这里分源码包 + 二进制包两个方面,
源码包更为严格, 挑核心的部分说 (完整的列表参考官方 <a
href=https://cwiki.apache.org/confluence/display/INCUBATOR/Incubator+Release+Checklist>Wiki</a>,
比较长)</p><p>首先我们需要从 apache 官方的 <code>release-candidate</code> 地址下载包到本地 (地址:
<code>dist.apache.org/repos/dist/dev/hugegraph/</code>)</p><h5 id=a-源码包>A.
源码包</h5><p>解压 <code>xxx-hugegraph-source.tar.gz</code>后, 进行如下检查:</p><o [...]
+</span></span><span style=display:flex><span>gpg --verify xx.asc
xxx-binary.tar.gz <span style=color:#8f5902;font-style:italic># Note: We
currently do not have a binary suffix</span>
+</span></span></code></pre></div><p>First confirm the overall
integrity/consistency, and then confirm the specific content
(<strong>key</strong>)</p><h4 id=3-check-the-archive-contents>3. Check the
archive contents</h4><p>Here it is divided into two aspects: source code
package + binary package, The source code package is more strict, it can be
said that the core part (Because it is longer,For a complete list refer to the
official <a href=https://cwiki.apache.org/confluence/display/INCUB [...]
</span></span><span style=display:flex><span>mvn clean <span
style=color:#204a87>test</span> -Dcheckstyle.skip<span
style=color:#ce5c00;font-weight:700>=</span><span
style=color:#204a87>false</span>
-</span></span></code></pre></div><h5 id=b-二进制包>B. 二进制包</h5><p>解压
<code>xxx-hugegraph.tar.gz</code>后, 进行如下检查:</p><ol><li>文件夹都带有
<code>incubating</code></li><li>存在 <code>LICENSE</code> + <code>NOTICE</code>
文件并且内容正常</li><li>通过 gpg 命令确认每个文件的签名正常</li></ol><p><strong>注:</strong>
如果二进制包里面引入了第三方依赖, 则需要更新 LICENSE, 加入第三方依赖的 LICENSE; 若第三方依赖 LICENSE 是 Apache 2.0,
且对应的项目中包含了 NOTICE, 则还需要更新我们的 NOTICE 文件</p><h4 id=4-检查官网以及-github-等页面>4. 检查官网以及
github 等页面</h4><ol><li>确保官网至少满足 <a href=https://whimsy.apa [...]
+</span></span></code></pre></div><h5 id=b-binary-package>B. binary
package</h5><p>After decompressing <code>xxx-hugegraph.tar.gz</code>, perform
the following checks:</p><ol><li>folders with
<code>incubating</code></li><li><code>LICENSE</code> and <code>NOTICE</code>
file exists and the content is normal</li><li>Confirm that the signature of
each file is normal through the gpg command</li></ol><p><strong>Note:</strong>
If a third-party dependency is introduced in the binary package, you [...]
<script
src=https://cdn.jsdelivr.net/npm/[email protected]/dist/js/bootstrap.min.js
integrity="sha512-UR25UO94eTnCVwjbXozyeVd6ZqpaAE9naiEUBK/A+QDbfSTQFhPGj5lOR6d8tsgbBk84Ggb5A3EkjsOgPRPcKA=="
crossorigin=anonymous></script>
<script src=/js/tabpane-persist.js></script>
<script
src=/js/main.min.aa9f4c5dae6a98b2c46277f4c56f1673a2b000d1756ce4ffae93784cab25e6d5.js
integrity="sha256-qp9MXa5qmLLEYnf0xW8Wc6KwANF1bOT/rpN4TKsl5tU="
crossorigin=anonymous></script>
diff --git a/docs/contribution-guidelines/index.xml
b/docs/contribution-guidelines/index.xml
index edc7b448..b3f7d2e6 100644
--- a/docs/contribution-guidelines/index.xml
+++ b/docs/contribution-guidelines/index.xml
@@ -133,52 +133,52 @@
</li>
</ol></description></item><item><title>Docs: Validate Apache
Release</title><link>/docs/contribution-guidelines/validate-release/</link><pubDate>Mon,
01 Jan 0001 00:00:00
+0000</pubDate><guid>/docs/contribution-guidelines/validate-release/</guid><description>
<blockquote>
-<p>TODO: Translate this article to English!</p>
+<p>TODO: enhance this doc soon</p>
</blockquote>
-<h2 id="验证阶段">验证阶段</h2>
-<p>当内部的临时发布和打包工作完成后, 其他的社区开发者(尤其是 PMC)需要参与到<a
href="https://cwiki.apache.org/confluence/display/INCUBATOR/Incubator+Release+Checklist";>验证环节</a>确保某个人发布版本的&quot;正确性
+ 完整性&quot;, 这里需要<strong>每个人</strong>都尽量参与,
然后后序<strong>邮件回复</strong>的时候说明自己<strong>已检查</strong>了哪些项.
(下面是核心项)</p>
-<h4 id="1-检查-hash-值">1. 检查 hash 值</h4>
-<p>首先需要检查 <code>source + binary</code> 包的文件完整性, 通过
<code>shasum</code> 进行校验, 确保和发布到 apache/github 上的 hash 值一致 (一般是 sha512),
这里同0x02的最后一步检验.</p>
-<h4 id="2-检查-gpg-签名">2. 检查 gpg 签名</h4>
-<p>这个就是为了确保发布的包是由<strong>可信赖</strong>的人上传的, 假设 tom 签名后上传, 其他人应该下载 A
的<strong>公钥</strong>然后进行<strong>签名确认</strong>, 相关命令:</p>
-<div class="highlight"><pre tabindex="0"
style="background-color:#f8f8f8;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code
class="language-bash" data-lang="bash"><span
style="display:flex;"><span><span
style="color:#8f5902;font-style:italic"># 1. 下载项目可信赖公钥到本地 (首次需要)</span>
+<h2 id="verification">Verification</h2>
+<p>When the internal temporary release and packaging work is completed,
other community developers (especially PMC) need to participate in the <a
href="https://cwiki.apache.org/confluence/display/INCUBATOR/Incubator+Release+Checklist";>verification
link</a>To ensure the &ldquo;correctness + completeness&rdquo; of
someone&rsquo;s published version, here requires
<strong>everyone</strong> to participate as much as possible, and then
explain which items you have &l [...]
+<h4 id="1-check-hash-value">1. check hash value</h4>
+<p>First you need to check the file integrity of the <code>source +
binary</code> package, Verify by <code>shasum</code> to ensure that it
is consistent with the hash value published on apache/github (Usually sha512),
Here is the same as the last step of 0x02 inspection.</p>
+<h4 id="2-check-gpg-signature">2. check gpg signature</h4>
+<p>This is to ensure that the published package is uploaded by a
<strong>reliable</strong> person. Assuming tom signs and uploads, others
should download A’s <strong>public key</strong> and then perform
<strong>signature confirmation</strong>. Related commands:</p>
+<div class="highlight"><pre tabindex="0"
style="background-color:#f8f8f8;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code
class="language-bash" data-lang="bash"><span
style="display:flex;"><span><span
style="color:#8f5902;font-style:italic"># 1. Download the trusted public key of
the project to the local (required for the first time)</span>
</span></span><span style="display:flex;"><span>curl xxx
&gt;&gt; PK
</span></span><span style="display:flex;"><span>gpg --import PK
-</span></span><span style="display:flex;"><span><span
style="color:#8f5902;font-style:italic"># 1.2 等待响应后输入 trust 表示信任 tom 的公钥
(其他人名类似)</span>
+</span></span><span style="display:flex;"><span><span
style="color:#8f5902;font-style:italic"># 1.2 Enter trust after waiting for the
response to trust Tom&#39;s public key (other names are similar)</span>
</span></span><span style="display:flex;"><span>gpg -edit-key tom
</span></span><span style="display:flex;"><span>
-</span></span><span style="display:flex;"><span><span
style="color:#8f5902;font-style:italic"># 2. 检查签名 (可用 0x03 章节的第 ⑧ 步的 for
循环脚本批量遍历)</span>
+</span></span><span style="display:flex;"><span><span
style="color:#8f5902;font-style:italic"># 2. Check the signature (you can use
the for loop script in step ⑧ of Chapter 0x03 to traverse in batches)</span>
</span></span><span style="display:flex;"><span>gpg --verify
xx.asc xxx-source.tar.gz
-</span></span><span style="display:flex;"><span>gpg --verify
xx.asc xxx-binary.tar.gz <span style="color:#8f5902;font-style:italic"># 注:
我们目前没有 binary 后缀</span>
-</span></span></code></pre></div><p>先确认了整体的完整性/一致性,
然后接下来确认具体的内容 (<strong>关键</strong>)</p>
-<h4 id="3-检查压缩包内容">3. 检查压缩包内容</h4>
-<p>这里分源码包 + 二进制包两个方面, 源码包更为严格, 挑核心的部分说 (完整的列表参考官方 <a
href="https://cwiki.apache.org/confluence/display/INCUBATOR/Incubator+Release+Checklist";>Wiki</a>,
比较长)</p>
-<p>首先我们需要从 apache 官方的 <code>release-candidate</code> 地址下载包到本地 (地址:
<code>dist.apache.org/repos/dist/dev/hugegraph/</code>)</p>
-<h5 id="a-源码包">A. 源码包</h5>
-<p>解压 <code>xxx-hugegraph-source.tar.gz</code>后, 进行如下检查:</p>
+</span></span><span style="display:flex;"><span>gpg --verify
xx.asc xxx-binary.tar.gz <span style="color:#8f5902;font-style:italic">#
Note: We currently do not have a binary suffix</span>
+</span></span></code></pre></div><p>First confirm the
overall integrity/consistency, and then confirm the specific content
(<strong>key</strong>)</p>
+<h4 id="3-check-the-archive-contents">3. Check the archive contents</h4>
+<p>Here it is divided into two aspects: source code package + binary
package, The source code package is more strict, it can be said that the core
part (Because it is longer,For a complete list refer to the official <a
href="https://cwiki.apache.org/confluence/display/INCUBATOR/Incubator+Release+Checklist";>Wiki</a>)</p>
+<p>First of all, we need to download the package from the apache official
<code>release-candidate</code> URL to the local (URL:
<code>dist.apache.org/repos/dist/dev/hugegraph/</code>)</p>
+<h5 id="a-source-package">A. source package</h5>
+<p>After decompressing <code>xxx-hugegraph-source.tar.gz</code>, Do
the following checks:</p>
<ol>
-<li>文件夹都带有 <code>incubating</code>,
且不存在<strong>空的</strong>文件/文件夹</li>
-<li>存在<code>DISCLAIMER</code>文件</li>
-<li>存在 <code>LICENSE</code> + <code>NOTICE</code>
文件并且内容正常</li>
-<li><strong>不存在</strong>任何二进制文件</li>
-<li>源码文件都包含标准 <code>ASF License</code> 头 (这个用插件跑一下为主)</li>
-<li>检查每个父/子模块的 <code>pom.xml</code> 版本号是否一致 (且符合期望)</li>
-<li>检查前 3 ~ 5 个 commit 提交, 点进去看看是否修改处和源码文件一致</li>
-<li>最后, 确保源码可以正常/正确编译 (然后看看测试和规范)</li>
+<li>folders with <code>incubating</code>, and no
<strong>empty</strong> files/folders</li>
+<li><code>DISCLAIMER</code> file exists</li>
+<li><code>LICENSE</code> + <code>NOTICE</code> file exists and
the content is normal</li>
+<li>** does not exist ** any binaries</li>
+<li>The source code files all contain the standard <code>ASF
License</code> header ((this can be done using a plugin))</li>
+<li>Check whether the <code>pom.xml</code> version number of each
parent/child module is consistent (and meet expectations)</li>
+<li>Check the first 3 to 5 commits, click to see if the modification is
consistent with the source file</li>
+<li>Finally, make sure the source code works/compiles correctly (then look
at tests and specs)</li>
</ol>
-<div class="highlight"><pre tabindex="0"
style="background-color:#f8f8f8;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code
class="language-bash" data-lang="bash"><span
style="display:flex;"><span><span
style="color:#8f5902;font-style:italic"># 同时也可以检查一下代码风格是否符合规范,
不符合的可以放下一次调整</span>
+<div class="highlight"><pre tabindex="0"
style="background-color:#f8f8f8;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code
class="language-bash" data-lang="bash"><span
style="display:flex;"><span><span
style="color:#8f5902;font-style:italic"># At the same time, you can also check
whether the code style conforms to the specification, and if it does not
conform, you can put down an adjustment</span>
</span></span><span style="display:flex;"><span>mvn clean <span
style="color:#204a87">test</span> -Dcheckstyle.skip<span
style="color:#ce5c00;font-weight:bold">=</span><span
style="color:#204a87">false</span>
-</span></span></code></pre></div><h5 id="b-二进制包">B.
二进制包</h5>
-<p>解压 <code>xxx-hugegraph.tar.gz</code>后, 进行如下检查:</p>
+</span></span></code></pre></div><h5
id="b-binary-package">B. binary package</h5>
+<p>After decompressing <code>xxx-hugegraph.tar.gz</code>, perform the
following checks:</p>
<ol>
-<li>文件夹都带有 <code>incubating</code></li>
-<li>存在 <code>LICENSE</code> + <code>NOTICE</code>
文件并且内容正常</li>
-<li>通过 gpg 命令确认每个文件的签名正常</li>
+<li>folders with <code>incubating</code></li>
+<li><code>LICENSE</code> and <code>NOTICE</code> file exists
and the content is normal</li>
+<li>Confirm that the signature of each file is normal through the gpg
command</li>
</ol>
-<p><strong>注:</strong> 如果二进制包里面引入了第三方依赖, 则需要更新 LICENSE, 加入第三方依赖的
LICENSE; 若第三方依赖 LICENSE 是 Apache 2.0, 且对应的项目中包含了 NOTICE, 则还需要更新我们的 NOTICE
文件</p>
-<h4 id="4-检查官网以及-github-等页面">4. 检查官网以及 github 等页面</h4>
+<p><strong>Note:</strong> If a third-party dependency is introduced
in the binary package, you need to update the LICENSE and add the third-party
dependent LICENSE; if the third-party dependent LICENSE is Apache 2.0, and the
corresponding project contains NOTICE, you also need to update Our NOTICE
file</p>
+<h4 id="4-check-the-official-website-and-github-and-other-pages">4. Check
the official website and github and other pages</h4>
<ol>
-<li>确保官网至少满足 <a
href="https://whimsy.apache.org/pods/project/hugegraph";>apache website
check</a>, 以及没有死链等</li>
-<li>更新<strong>下载链接</strong>以及版本更新说明</li>
+<li>Make sure that the official website at least meets <a
href="https://whimsy.apache.org/pods/project/hugegraph";>apache website
check</a>, and no circular links etc.</li>
+<li>Update <strong>download link</strong> and version update
instructions</li>
<li>&hellip;</li>
</ol></description></item></channel></rss>
\ No newline at end of file
diff --git a/docs/contribution-guidelines/validate-release/index.html
b/docs/contribution-guidelines/validate-release/index.html
index 74de2655..152d3186 100644
--- a/docs/contribution-guidelines/validate-release/index.html
+++ b/docs/contribution-guidelines/validate-release/index.html
@@ -1,37 +1,31 @@
<!doctype html><html lang=en class=no-js><head><meta charset=utf-8><meta
name=viewport
content="width=device-width,initial-scale=1,shrink-to-fit=no"><meta
name=generator content="Hugo 0.102.3"><meta name=robots content="index,
follow"><link rel="shortcut icon" href=/favicons/favicon.ico><link
rel=apple-touch-icon href=/favicons/apple-touch-icon-180x180.png
sizes=180x180><link rel=icon type=image/png href=/favicons/favicon-16x16.png
sizes=16x16><link rel=icon type=image/png href=/favicons [...]
-TODO: Translate this article to English!
+TODO: enhance this doc soon
-验证阶段
-当内部的临时发布和打包工作完成后, 其他的社区开发者(尤其是 PMC)需要参与到验证环节确保某个人发布版本的"正确性 + 完整性",
这里需要每个人都尽量参与, 然后后序邮件回复的时候 …"><meta property="og:title" content="Validate Apache
Release"><meta property="og:description" content="TODO: Translate this article
to English!
-验证阶段 当内部的临时发布和打包工作完成后, 其他的社区开发者(尤其是 PMC)需要参与到验证环节确保某个人发布版本的"正确性 +
完整性", 这里需要每个人都尽量参与, 然后后序邮件回复的时候说明自己已检查了哪些项. (下面是核心项)
-1. 检查 hash 值 首先需要检查 source + binary 包的文件完整性, 通过 shasum 进行校验, 确保和发布到
apache/github 上的 hash 值一致 (一般是 sha512), 这里同0x02的最后一步检验.
-2. 检查 gpg 签名 这个就是为了确保发布的包是由可信赖的人上传的, 假设 tom 签名后上传, 其他人应该下载 A 的公钥然后进行签名确认, 相关命令:
-# 1. 下载项目可信赖公钥到本地 (首次需要) curl xxx >> PK gpg --import PK # 1.2 等待响应后输入 trust
表示信任 tom 的公钥 (其他人名类似) gpg -edit-key tom # 2."><meta property="og:type"
content="article"><meta property="og:url"
content="/docs/contribution-guidelines/validate-release/"><meta
property="article:section" content="docs"><meta
property="article:modified_time" content="2022-12-30T19:36:31+08:00"><meta
property="og:site_name" content="HugeGraph"><meta itemprop=name
content="Validate Apache Release"><meta itemprop=des [...]
-验证阶段 当内部的临时发布和打包工作完成后, 其他的社区开发者(尤其是 PMC)需要参与到验证环节确保某个人发布版本的"正确性 +
完整性", 这里需要每个人都尽量参与, 然后后序邮件回复的时候说明自己已检查了哪些项. (下面是核心项)
-1. 检查 hash 值 首先需要检查 source + binary 包的文件完整性, 通过 shasum 进行校验, 确保和发布到
apache/github 上的 hash 值一致 (一般是 sha512), 这里同0x02的最后一步检验.
-2. 检查 gpg 签名 这个就是为了确保发布的包是由可信赖的人上传的, 假设 tom 签名后上传, 其他人应该下载 A 的公钥然后进行签名确认, 相关命令:
-# 1. 下载项目可信赖公钥到本地 (首次需要) curl xxx >> PK gpg --import PK # 1.2 等待响应后输入 trust
表示信任 tom 的公钥 (其他人名类似) gpg -edit-key tom # 2."><meta itemprop=dateModified
content="2022-12-30T19:36:31+08:00"><meta itemprop=wordCount
content="196"><meta itemprop=keywords content><meta name=twitter:card
content="summary"><meta name=twitter:title content="Validate Apache
Release"><meta name=twitter:description content="TODO: Translate this article
to English!
-验证阶段 当内部的临时发布和打包工作完成后, 其他的社区开发者(尤其是 PMC)需要参与到验证环节确保某个人发布版本的"正确性 +
完整性", 这里需要每个人都尽量参与, 然后后序邮件回复的时候说明自己已检查了哪些项. (下面是核心项)
-1. 检查 hash 值 首先需要检查 source + binary 包的文件完整性, 通过 shasum 进行校验, 确保和发布到
apache/github 上的 hash 值一致 (一般是 sha512), 这里同0x02的最后一步检验.
-2. 检查 gpg 签名 这个就是为了确保发布的包是由可信赖的人上传的, 假设 tom 签名后上传, 其他人应该下载 A 的公钥然后进行签名确认, 相关命令:
-# 1. 下载项目可信赖公钥到本地 (首次需要) curl xxx >> PK gpg --import PK # 1.2 等待响应后输入 trust
表示信任 tom 的公钥 (其他人名类似) gpg -edit-key tom # 2."><link rel=preload
href=/scss/main.min.3bdb596b76fcb366af48203b8a7820669f5437dd9ec431ee2c8b18063301106e.css
as=style><link
href=/scss/main.min.3bdb596b76fcb366af48203b8a7820669f5437dd9ec431ee2c8b18063301106e.css
rel=stylesheet integrity><script
src=https://code.jquery.com/jquery-3.5.1.min.js
integrity="sha256-9/aliU8dGd2tb6OSsuzixeV4y/faTqgFtohetphbbj0=" crossorigin=an
[...]
+Verification
+When the internal temporary release and packaging work is completed, other
community developers (especially …"><meta property="og:title" content="Validate
Apache Release"><meta property="og:description" content="TODO: enhance this doc
soon
+Verification When the internal temporary release and packaging work is
completed, other community developers (especially PMC) need to participate in
the verification linkTo ensure the “correctness + completeness” of
someone’s published version, here requires everyone to participate as
much as possible, and then explain which items you have checked in the
subsequent email reply. (The following are the core items)
+1. check hash value First you need to check the file integrity of the source +
binary package, Verify by shasum to ensure that it is consistent with the hash
value published on apache/github (Usually sha512), Here is the same as the last
step of 0x02 inspection."><meta property="og:type" content="article"><meta
property="og:url"
content="/docs/contribution-guidelines/validate-release/"><meta
property="article:section" content="docs"><meta
property="article:modified_time" content="2022-12 [...]
+Verification When the internal temporary release and packaging work is
completed, other community developers (especially PMC) need to participate in
the verification linkTo ensure the “correctness + completeness” of
someone’s published version, here requires everyone to participate as
much as possible, and then explain which items you have checked in the
subsequent email reply. (The following are the core items)
+1. check hash value First you need to check the file integrity of the source +
binary package, Verify by shasum to ensure that it is consistent with the hash
value published on apache/github (Usually sha512), Here is the same as the last
step of 0x02 inspection."><meta itemprop=dateModified
content="2022-12-31T14:45:20+08:00"><meta itemprop=wordCount
content="563"><meta itemprop=keywords content><meta name=twitter:card
content="summary"><meta name=twitter:title content="Validate Apache R [...]
+Verification When the internal temporary release and packaging work is
completed, other community developers (especially PMC) need to participate in
the verification linkTo ensure the “correctness + completeness” of
someone’s published version, here requires everyone to participate as
much as possible, and then explain which items you have checked in the
subsequent email reply. (The following are the core items)
+1. check hash value First you need to check the file integrity of the source +
binary package, Verify by shasum to ensure that it is consistent with the hash
value published on apache/github (Usually sha512), Here is the same as the last
step of 0x02 inspection."><link rel=preload
href=/scss/main.min.3bdb596b76fcb366af48203b8a7820669f5437dd9ec431ee2c8b18063301106e.css
as=style><link
href=/scss/main.min.3bdb596b76fcb366af48203b8a7820669f5437dd9ec431ee2c8b18063301106e.css
rel=stylesheet in [...]
<link rel=stylesheet href=/css/prism.css><script
type=application/javascript>var
doNotTrack=!1;doNotTrack||(window.ga=window.ga||function(){(ga.q=ga.q||[]).push(arguments)},ga.l=+new
Date,ga("create","UA-00000000-0","auto"),ga("send","pageview"))</script><script
async src=https://www.google-analytics.com/analytics.js></script></head><body
class=td-page><header><nav class="js-navbar-scroll navbar navbar-expand
navbar-dark flex-column flex-md-row td-navbar"><a class=navbar-brand href=/><sp
[...]
<a
href=https://github.com/apache/incubator-hugegraph-doc/edit/master/content/en/docs/contribution-guidelines/validate-release.md
class=td-page-meta--edit target=_blank rel=noopener><i class="fa fa-edit
fa-fw"></i> Edit this page</a>
<a
href="https://github.com/apache/incubator-hugegraph-doc/new/master/content/en/docs/contribution-guidelines/validate-release.md?filename=change-me.md&value=---%0Atitle%3A+%22Long+Page+Title%22%0AlinkTitle%3A+%22Short+Nav+Title%22%0Aweight%3A+100%0Adescription%3A+%3E-%0A+++++Page+description+for+heading+and+indexes.%0A---%0A%0A%23%23+Heading%0A%0AEdit+this+template+to+create+your+new+page.%0A%0A%2A+Give+it+a+good+name%2C+ending+in+%60.md%60+-+e.g.+%60getting-started.md%60%0A%2A+Edit+the
[...]
<a
href="https://github.com/apache/incubator-hugegraph-doc/issues/new?title=Validate%20Apache%20Release";
class=td-page-meta--issue target=_blank rel=noopener><i class="fab fa-github
fa-fw"></i> Create documentation issue</a>
<a href=https://github.com/apache/incubator-hugegraph/issues/new
class=td-page-meta--project-issue target=_blank rel=noopener><i class="fas
fa-tasks fa-fw"></i> Create project issue</a>
-<a id=print href=/docs/contribution-guidelines/_print/><i class="fa fa-print
fa-fw"></i> Print entire section</a></div></aside><main class="col-12 col-md-9
col-xl-8 pl-md-5" role=main><nav aria-label=breadcrumb class=td-breadcrumbs><ol
class=breadcrumb><li class=breadcrumb-item><a
href=/docs/>Documentation</a></li><li class=breadcrumb-item><a
href=/docs/contribution-guidelines/>Contribution Guidelines</a></li><li
class="breadcrumb-item active" aria-current=page><a href=/docs/contribution
[...]
+<a id=print href=/docs/contribution-guidelines/_print/><i class="fa fa-print
fa-fw"></i> Print entire section</a></div></aside><main class="col-12 col-md-9
col-xl-8 pl-md-5" role=main><nav aria-label=breadcrumb class=td-breadcrumbs><ol
class=breadcrumb><li class=breadcrumb-item><a
href=/docs/>Documentation</a></li><li class=breadcrumb-item><a
href=/docs/contribution-guidelines/>Contribution Guidelines</a></li><li
class="breadcrumb-item active" aria-current=page><a href=/docs/contribution
[...]
</span></span><span style=display:flex><span>curl xxx >> PK
</span></span><span style=display:flex><span>gpg --import PK
-</span></span><span style=display:flex><span><span
style=color:#8f5902;font-style:italic># 1.2 等待响应后输入 trust 表示信任 tom 的公钥
(其他人名类似)</span>
+</span></span><span style=display:flex><span><span
style=color:#8f5902;font-style:italic># 1.2 Enter trust after waiting for the
response to trust Tom's public key (other names are similar)</span>
</span></span><span style=display:flex><span>gpg -edit-key tom
</span></span><span style=display:flex><span>
-</span></span><span style=display:flex><span><span
style=color:#8f5902;font-style:italic># 2. 检查签名 (可用 0x03 章节的第 ⑧ 步的 for
循环脚本批量遍历)</span>
+</span></span><span style=display:flex><span><span
style=color:#8f5902;font-style:italic># 2. Check the signature (you can use the
for loop script in step ⑧ of Chapter 0x03 to traverse in batches)</span>
</span></span><span style=display:flex><span>gpg --verify xx.asc
xxx-source.tar.gz
-</span></span><span style=display:flex><span>gpg --verify xx.asc
xxx-binary.tar.gz <span style=color:#8f5902;font-style:italic># 注: 我们目前没有
binary 后缀</span>
-</span></span></code></pre></div><p>先确认了整体的完整性/一致性, 然后接下来确认具体的内容
(<strong>关键</strong>)</p><h4 id=3-检查压缩包内容>3. 检查压缩包内容</h4><p>这里分源码包 + 二进制包两个方面,
源码包更为严格, 挑核心的部分说 (完整的列表参考官方 <a
href=https://cwiki.apache.org/confluence/display/INCUBATOR/Incubator+Release+Checklist>Wiki</a>,
比较长)</p><p>首先我们需要从 apache 官方的 <code>release-candidate</code> 地址下载包到本地 (地址:
<code>dist.apache.org/repos/dist/dev/hugegraph/</code>)</p><h5 id=a-源码包>A.
源码包</h5><p>解压 <code>xxx-hugegraph-source.tar.gz</code>后, 进行如下检查:</p><o [...]
+</span></span><span style=display:flex><span>gpg --verify xx.asc
xxx-binary.tar.gz <span style=color:#8f5902;font-style:italic># Note: We
currently do not have a binary suffix</span>
+</span></span></code></pre></div><p>First confirm the overall
integrity/consistency, and then confirm the specific content
(<strong>key</strong>)</p><h4 id=3-check-the-archive-contents>3. Check the
archive contents</h4><p>Here it is divided into two aspects: source code
package + binary package, The source code package is more strict, it can be
said that the core part (Because it is longer,For a complete list refer to the
official <a href=https://cwiki.apache.org/confluence/display/INCUB [...]
</span></span><span style=display:flex><span>mvn clean <span
style=color:#204a87>test</span> -Dcheckstyle.skip<span
style=color:#ce5c00;font-weight:700>=</span><span
style=color:#204a87>false</span>
-</span></span></code></pre></div><h5 id=b-二进制包>B. 二进制包</h5><p>解压
<code>xxx-hugegraph.tar.gz</code>后, 进行如下检查:</p><ol><li>文件夹都带有
<code>incubating</code></li><li>存在 <code>LICENSE</code> + <code>NOTICE</code>
文件并且内容正常</li><li>通过 gpg 命令确认每个文件的签名正常</li></ol><p><strong>注:</strong>
如果二进制包里面引入了第三方依赖, 则需要更新 LICENSE, 加入第三方依赖的 LICENSE; 若第三方依赖 LICENSE 是 Apache 2.0,
且对应的项目中包含了 NOTICE, 则还需要更新我们的 NOTICE 文件</p><h4 id=4-检查官网以及-github-等页面>4. 检查官网以及
github 等页面</h4><ol><li>确保官网至少满足 <a href=https://whimsy.apa [...]
+</span></span></code></pre></div><h5 id=b-binary-package>B. binary
package</h5><p>After decompressing <code>xxx-hugegraph.tar.gz</code>, perform
the following checks:</p><ol><li>folders with
<code>incubating</code></li><li><code>LICENSE</code> and <code>NOTICE</code>
file exists and the content is normal</li><li>Confirm that the signature of
each file is normal through the gpg command</li></ol><p><strong>Note:</strong>
If a third-party dependency is introduced in the binary package, you [...]
<script
src=https://cdn.jsdelivr.net/npm/[email protected]/dist/js/bootstrap.min.js
integrity="sha512-UR25UO94eTnCVwjbXozyeVd6ZqpaAE9naiEUBK/A+QDbfSTQFhPGj5lOR6d8tsgbBk84Ggb5A3EkjsOgPRPcKA=="
crossorigin=anonymous></script>
<script src=/js/tabpane-persist.js></script>
<script
src=/js/main.min.aa9f4c5dae6a98b2c46277f4c56f1673a2b000d1756ce4ffae93784cab25e6d5.js
integrity="sha256-qp9MXa5qmLLEYnf0xW8Wc6KwANF1bOT/rpN4TKsl5tU="
crossorigin=anonymous></script>
diff --git a/docs/index.xml b/docs/index.xml
index d1d3474f..a525c101 100644
--- a/docs/index.xml
+++ b/docs/index.xml
@@ -7329,53 +7329,53 @@ auth.user_tokens=[hugegraph1:token-value-1,
hugegraph2:token-value-2]
</li>
</ul></description></item><item><title>Docs: Validate Apache
Release</title><link>/docs/contribution-guidelines/validate-release/</link><pubDate>Mon,
01 Jan 0001 00:00:00
+0000</pubDate><guid>/docs/contribution-guidelines/validate-release/</guid><description>
<blockquote>
-<p>TODO: Translate this article to English!</p>
+<p>TODO: enhance this doc soon</p>
</blockquote>
-<h2 id="验证阶段">验证阶段</h2>
-<p>当内部的临时发布和打包工作完成后, 其他的社区开发者(尤其是 PMC)需要参与到<a
href="https://cwiki.apache.org/confluence/display/INCUBATOR/Incubator+Release+Checklist";>验证环节</a>确保某个人发布版本的&quot;正确性
+ 完整性&quot;, 这里需要<strong>每个人</strong>都尽量参与,
然后后序<strong>邮件回复</strong>的时候说明自己<strong>已检查</strong>了哪些项.
(下面是核心项)</p>
-<h4 id="1-检查-hash-值">1. 检查 hash 值</h4>
-<p>首先需要检查 <code>source + binary</code> 包的文件完整性, 通过
<code>shasum</code> 进行校验, 确保和发布到 apache/github 上的 hash 值一致 (一般是 sha512),
这里同0x02的最后一步检验.</p>
-<h4 id="2-检查-gpg-签名">2. 检查 gpg 签名</h4>
-<p>这个就是为了确保发布的包是由<strong>可信赖</strong>的人上传的, 假设 tom 签名后上传, 其他人应该下载 A
的<strong>公钥</strong>然后进行<strong>签名确认</strong>, 相关命令:</p>
-<div class="highlight"><pre tabindex="0"
style="background-color:#f8f8f8;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code
class="language-bash" data-lang="bash"><span
style="display:flex;"><span><span
style="color:#8f5902;font-style:italic"># 1. 下载项目可信赖公钥到本地 (首次需要)</span>
+<h2 id="verification">Verification</h2>
+<p>When the internal temporary release and packaging work is completed,
other community developers (especially PMC) need to participate in the <a
href="https://cwiki.apache.org/confluence/display/INCUBATOR/Incubator+Release+Checklist";>verification
link</a>To ensure the &ldquo;correctness + completeness&rdquo; of
someone&rsquo;s published version, here requires
<strong>everyone</strong> to participate as much as possible, and then
explain which items you have &l [...]
+<h4 id="1-check-hash-value">1. check hash value</h4>
+<p>First you need to check the file integrity of the <code>source +
binary</code> package, Verify by <code>shasum</code> to ensure that it
is consistent with the hash value published on apache/github (Usually sha512),
Here is the same as the last step of 0x02 inspection.</p>
+<h4 id="2-check-gpg-signature">2. check gpg signature</h4>
+<p>This is to ensure that the published package is uploaded by a
<strong>reliable</strong> person. Assuming tom signs and uploads, others
should download A’s <strong>public key</strong> and then perform
<strong>signature confirmation</strong>. Related commands:</p>
+<div class="highlight"><pre tabindex="0"
style="background-color:#f8f8f8;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code
class="language-bash" data-lang="bash"><span
style="display:flex;"><span><span
style="color:#8f5902;font-style:italic"># 1. Download the trusted public key of
the project to the local (required for the first time)</span>
</span></span><span style="display:flex;"><span>curl xxx
&gt;&gt; PK
</span></span><span style="display:flex;"><span>gpg --import PK
-</span></span><span style="display:flex;"><span><span
style="color:#8f5902;font-style:italic"># 1.2 等待响应后输入 trust 表示信任 tom 的公钥
(其他人名类似)</span>
+</span></span><span style="display:flex;"><span><span
style="color:#8f5902;font-style:italic"># 1.2 Enter trust after waiting for the
response to trust Tom&#39;s public key (other names are similar)</span>
</span></span><span style="display:flex;"><span>gpg -edit-key tom
</span></span><span style="display:flex;"><span>
-</span></span><span style="display:flex;"><span><span
style="color:#8f5902;font-style:italic"># 2. 检查签名 (可用 0x03 章节的第 ⑧ 步的 for
循环脚本批量遍历)</span>
+</span></span><span style="display:flex;"><span><span
style="color:#8f5902;font-style:italic"># 2. Check the signature (you can use
the for loop script in step ⑧ of Chapter 0x03 to traverse in batches)</span>
</span></span><span style="display:flex;"><span>gpg --verify
xx.asc xxx-source.tar.gz
-</span></span><span style="display:flex;"><span>gpg --verify
xx.asc xxx-binary.tar.gz <span style="color:#8f5902;font-style:italic"># 注:
我们目前没有 binary 后缀</span>
-</span></span></code></pre></div><p>先确认了整体的完整性/一致性,
然后接下来确认具体的内容 (<strong>关键</strong>)</p>
-<h4 id="3-检查压缩包内容">3. 检查压缩包内容</h4>
-<p>这里分源码包 + 二进制包两个方面, 源码包更为严格, 挑核心的部分说 (完整的列表参考官方 <a
href="https://cwiki.apache.org/confluence/display/INCUBATOR/Incubator+Release+Checklist";>Wiki</a>,
比较长)</p>
-<p>首先我们需要从 apache 官方的 <code>release-candidate</code> 地址下载包到本地 (地址:
<code>dist.apache.org/repos/dist/dev/hugegraph/</code>)</p>
-<h5 id="a-源码包">A. 源码包</h5>
-<p>解压 <code>xxx-hugegraph-source.tar.gz</code>后, 进行如下检查:</p>
+</span></span><span style="display:flex;"><span>gpg --verify
xx.asc xxx-binary.tar.gz <span style="color:#8f5902;font-style:italic">#
Note: We currently do not have a binary suffix</span>
+</span></span></code></pre></div><p>First confirm the
overall integrity/consistency, and then confirm the specific content
(<strong>key</strong>)</p>
+<h4 id="3-check-the-archive-contents">3. Check the archive contents</h4>
+<p>Here it is divided into two aspects: source code package + binary
package, The source code package is more strict, it can be said that the core
part (Because it is longer,For a complete list refer to the official <a
href="https://cwiki.apache.org/confluence/display/INCUBATOR/Incubator+Release+Checklist";>Wiki</a>)</p>
+<p>First of all, we need to download the package from the apache official
<code>release-candidate</code> URL to the local (URL:
<code>dist.apache.org/repos/dist/dev/hugegraph/</code>)</p>
+<h5 id="a-source-package">A. source package</h5>
+<p>After decompressing <code>xxx-hugegraph-source.tar.gz</code>, Do
the following checks:</p>
<ol>
-<li>文件夹都带有 <code>incubating</code>,
且不存在<strong>空的</strong>文件/文件夹</li>
-<li>存在<code>DISCLAIMER</code>文件</li>
-<li>存在 <code>LICENSE</code> + <code>NOTICE</code>
文件并且内容正常</li>
-<li><strong>不存在</strong>任何二进制文件</li>
-<li>源码文件都包含标准 <code>ASF License</code> 头 (这个用插件跑一下为主)</li>
-<li>检查每个父/子模块的 <code>pom.xml</code> 版本号是否一致 (且符合期望)</li>
-<li>检查前 3 ~ 5 个 commit 提交, 点进去看看是否修改处和源码文件一致</li>
-<li>最后, 确保源码可以正常/正确编译 (然后看看测试和规范)</li>
+<li>folders with <code>incubating</code>, and no
<strong>empty</strong> files/folders</li>
+<li><code>DISCLAIMER</code> file exists</li>
+<li><code>LICENSE</code> + <code>NOTICE</code> file exists and
the content is normal</li>
+<li>** does not exist ** any binaries</li>
+<li>The source code files all contain the standard <code>ASF
License</code> header ((this can be done using a plugin))</li>
+<li>Check whether the <code>pom.xml</code> version number of each
parent/child module is consistent (and meet expectations)</li>
+<li>Check the first 3 to 5 commits, click to see if the modification is
consistent with the source file</li>
+<li>Finally, make sure the source code works/compiles correctly (then look
at tests and specs)</li>
</ol>
-<div class="highlight"><pre tabindex="0"
style="background-color:#f8f8f8;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code
class="language-bash" data-lang="bash"><span
style="display:flex;"><span><span
style="color:#8f5902;font-style:italic"># 同时也可以检查一下代码风格是否符合规范,
不符合的可以放下一次调整</span>
+<div class="highlight"><pre tabindex="0"
style="background-color:#f8f8f8;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code
class="language-bash" data-lang="bash"><span
style="display:flex;"><span><span
style="color:#8f5902;font-style:italic"># At the same time, you can also check
whether the code style conforms to the specification, and if it does not
conform, you can put down an adjustment</span>
</span></span><span style="display:flex;"><span>mvn clean <span
style="color:#204a87">test</span> -Dcheckstyle.skip<span
style="color:#ce5c00;font-weight:bold">=</span><span
style="color:#204a87">false</span>
-</span></span></code></pre></div><h5 id="b-二进制包">B.
二进制包</h5>
-<p>解压 <code>xxx-hugegraph.tar.gz</code>后, 进行如下检查:</p>
+</span></span></code></pre></div><h5
id="b-binary-package">B. binary package</h5>
+<p>After decompressing <code>xxx-hugegraph.tar.gz</code>, perform the
following checks:</p>
<ol>
-<li>文件夹都带有 <code>incubating</code></li>
-<li>存在 <code>LICENSE</code> + <code>NOTICE</code>
文件并且内容正常</li>
-<li>通过 gpg 命令确认每个文件的签名正常</li>
+<li>folders with <code>incubating</code></li>
+<li><code>LICENSE</code> and <code>NOTICE</code> file exists
and the content is normal</li>
+<li>Confirm that the signature of each file is normal through the gpg
command</li>
</ol>
-<p><strong>注:</strong> 如果二进制包里面引入了第三方依赖, 则需要更新 LICENSE, 加入第三方依赖的
LICENSE; 若第三方依赖 LICENSE 是 Apache 2.0, 且对应的项目中包含了 NOTICE, 则还需要更新我们的 NOTICE
文件</p>
-<h4 id="4-检查官网以及-github-等页面">4. 检查官网以及 github 等页面</h4>
+<p><strong>Note:</strong> If a third-party dependency is introduced
in the binary package, you need to update the LICENSE and add the third-party
dependent LICENSE; if the third-party dependent LICENSE is Apache 2.0, and the
corresponding project contains NOTICE, you also need to update Our NOTICE
file</p>
+<h4 id="4-check-the-official-website-and-github-and-other-pages">4. Check
the official website and github and other pages</h4>
<ol>
-<li>确保官网至少满足 <a
href="https://whimsy.apache.org/pods/project/hugegraph";>apache website
check</a>, 以及没有死链等</li>
-<li>更新<strong>下载链接</strong>以及版本更新说明</li>
+<li>Make sure that the official website at least meets <a
href="https://whimsy.apache.org/pods/project/hugegraph";>apache website
check</a>, and no circular links etc.</li>
+<li>Update <strong>download link</strong> and version update
instructions</li>
<li>&hellip;</li>
</ol></description></item><item><title>Docs: VertexLabel
API</title><link>/docs/clients/restful-api/vertexlabel/</link><pubDate>Mon, 01
Jan 0001 00:00:00
+0000</pubDate><guid>/docs/clients/restful-api/vertexlabel/</guid><description>
<h3 id="13-vertexlabel">1.3 VertexLabel</h3>
diff --git a/en/sitemap.xml b/en/sitemap.xml
index 681a2112..30a64dc5 100644
--- a/en/sitemap.xml
+++ b/en/sitemap.xml
@@ -1 +1 @@
-<?xml version="1.0" encoding="utf-8" standalone="yes"?><urlset
xmlns="http://www.sitemaps.org/schemas/sitemap/0.9";
xmlns:xhtml="http://www.w3.org/1999/xhtml";><url><loc>/docs/guides/architectural/</loc><lastmod>2022-11-27T21:05:55+08:00</lastmod><xhtml:link
rel="alternate" hreflang="cn"
href="/cn/docs/guides/architectural/"/><xhtml:link rel="alternate"
hreflang="en"
href="/docs/guides/architectural/"/></url><url><loc>/docs/config/config-guide/</loc><lastmod>2022-04-17T11:36:55+08:00</last
[...]
\ No newline at end of file
+<?xml version="1.0" encoding="utf-8" standalone="yes"?><urlset
xmlns="http://www.sitemaps.org/schemas/sitemap/0.9";
xmlns:xhtml="http://www.w3.org/1999/xhtml";><url><loc>/docs/guides/architectural/</loc><lastmod>2022-11-27T21:05:55+08:00</lastmod><xhtml:link
rel="alternate" hreflang="cn"
href="/cn/docs/guides/architectural/"/><xhtml:link rel="alternate"
hreflang="en"
href="/docs/guides/architectural/"/></url><url><loc>/docs/config/config-guide/</loc><lastmod>2022-04-17T11:36:55+08:00</last
[...]
\ No newline at end of file
diff --git a/sitemap.xml b/sitemap.xml
index 30fa01dd..78d7e34d 100644
--- a/sitemap.xml
+++ b/sitemap.xml
@@ -1 +1 @@
-<?xml version="1.0" encoding="utf-8" standalone="yes"?><sitemapindex
xmlns="http://www.sitemaps.org/schemas/sitemap/0.9";><sitemap><loc>/en/sitemap.xml</loc><lastmod>2022-12-30T19:57:48+08:00</lastmod></sitemap><sitemap><loc>/cn/sitemap.xml</loc><lastmod>2022-12-30T19:57:48+08:00</lastmod></sitemap></sitemapindex>
\ No newline at end of file
+<?xml version="1.0" encoding="utf-8" standalone="yes"?><sitemapindex
xmlns="http://www.sitemaps.org/schemas/sitemap/0.9";><sitemap><loc>/en/sitemap.xml</loc><lastmod>2022-12-31T14:45:20+08:00</lastmod></sitemap><sitemap><loc>/cn/sitemap.xml</loc><lastmod>2022-12-30T19:57:48+08:00</lastmod></sitemap></sitemapindex>
\ No newline at end of file
