This is an automated email from the ASF dual-hosted git repository.

git-site-role pushed a commit to branch asf-site
in repository https://gitbox.apache.org/repos/asf/incubator-gluten-site.git


The following commit(s) were added to refs/heads/asf-site by this push:
     new 87b0a4e  Automatic Site Publish by Buildbot
87b0a4e is described below

commit 87b0a4e03c8921be5f9383747b0801526fcc0b90
Author: buildbot <[email protected]>
AuthorDate: Wed Dec 4 08:38:42 2024 +0000

    Automatic Site Publish by Buildbot
---
 output/archives/v1.1.1/developers/howtorelease/index.html | 8 ++++----
 output/assets/js/search-data.json                         | 4 ++--
 output/docs/developers/how-to-release/index.html          | 8 ++++----
 output/feed.xml                                           | 2 +-
 4 files changed, 11 insertions(+), 11 deletions(-)

diff --git a/output/archives/v1.1.1/developers/howtorelease/index.html 
b/output/archives/v1.1.1/developers/howtorelease/index.html
index 0ac0004..41f5043 100644
--- a/output/archives/v1.1.1/developers/howtorelease/index.html
+++ b/output/archives/v1.1.1/developers/howtorelease/index.html
@@ -10,7 +10,7 @@ $ gpg --keyserver keyserver.ubuntu.com --send-key xxx
 
 # append the GPG key to the KEYS file the svn repository
 # [IMPORTANT] Don't replace the KEYS file, just append the GPG key to the KEYS 
file. 
-$ svn co https://dist.apache.org/repos/dist/release/incubator/answer/
+$ svn co https://dist.apache.org/repos/dist/release/incubator/gluten/
 $ (gpg --list-sigs [email protected] &amp;&amp; gpg --export --armor 
[email protected]) &gt;&gt; KEYS 
 $ svn ci -m "add gpg key" 
 
@@ -21,7 +21,7 @@ $ for i in *.tar.gz; do echo $i; sha512sum  $i &gt; $i.sha512 
; done
 </code></pre></div></div> <h3 
id="upload-the-release-artifacts-to-the-svn-repository"> <a 
href="#upload-the-release-artifacts-to-the-svn-repository" 
class="anchor-heading" 
aria-labelledby="upload-the-release-artifacts-to-the-svn-repository"><svg 
viewBox="0 0 16 16" aria-hidden="true"><use 
xlink:href="#svg-link"></use></svg></a> Upload the release artifacts to the SVN 
repository. </h3> <ol> <li> <p>Create a project directory in the SVN repository 
(1st time only). <code class="language-pla [...]
 $ cp /path/to/release/artifacts/* ./{release-version}/
 $ svn add ./{release-version}/*
-$ svn commit -m "add Apache Answer release artifacts for {release-version}"
+$ svn commit -m "add Apache Gluten release artifacts for {release-version}"
 </code></pre></div> </div> </li> <li>After the upload, please visit the link 
<code class="language-plaintext 
highlighter-rouge">https://dist.apache.org/repos/dist/dev/incubator/gluten/{release-version}</code>
 to verify if the file upload is successful or not. The upload release 
artifacts should be include <div class="language-plaintext 
highlighter-rouge"><div class="highlight"><pre class="highlight"><code>* 
apache-gluten-#.#.#-incubating-src.tar.gz
 * apache-gluten-#.#.#-incubating-src.tar.gz.asc
 * apache-gluten-#.#.#-incubating-src.tar.gz.sha512
@@ -85,7 +85,7 @@ Hello,
     [ ] Download links are valid.
     [ ] Checksums and PGP signatures are valid.
     [ ] Source code distributions have correct names matching the current 
release.
-    [ ] LICENSE and NOTICE files are correct for each Apache Answer repo.
+    [ ] LICENSE and NOTICE files are correct for each Apache Gluten repo.
     [ ] All files have license headers if necessary.
     [ ] No unlicensed compiled archives bundled in source archive.
 
@@ -100,7 +100,7 @@ Thanks,
 The Apache Gluten (Incubating) {release-version} has been released!
 
 Apache Gluten is a Q&amp;A platform software for teams at any scale.
-Whether it's a community forum, help center, or knowledge management platform, 
you can always count on Apache Answer.
+Whether it's a community forum, help center, or knowledge management platform, 
you can always count on Apache Gluten.
 
 Download Links: https://downloads.apache.org/incubator/gluten/
 
diff --git a/output/assets/js/search-data.json 
b/output/assets/js/search-data.json
index be07356..16eb3c4 100644
--- a/output/assets/js/search-data.json
+++ b/output/assets/js/search-data.json
@@ -757,7 +757,7 @@
   },"108": {
     "doc": "v1.1.1/How To Release",
     "title": "Release Process",
-    "content": ". | Prepare the release artifacts. | Upload the release 
artifacts to the SVN repository. | Verify the release artifacts. | Initiate a 
release vote. | Announce the results and the release. | . Prepare the release 
artifacts. | Create a branch from the target git repository. | Tag a RC and 
draft the release notes. | Build and Sign the release artifacts (including 
source archives, binaries, …etc). | Generate checksums for the artifacts. | . 
How to Sign the release artifacts.  [...]
+    "content": ". | Prepare the release artifacts. | Upload the release 
artifacts to the SVN repository. | Verify the release artifacts. | Initiate a 
release vote. | Announce the results and the release. | . Prepare the release 
artifacts. | Create a branch from the target git repository. | Tag a RC and 
draft the release notes. | Build and Sign the release artifacts (including 
source archives, binaries, …etc). | Generate checksums for the artifacts. | . 
How to Sign the release artifacts.  [...]
     "url": "/archives/v1.1.1/developers/howtorelease/#release-process",
     
     "relUrl": "/archives/v1.1.1/developers/howtorelease/#release-process"
@@ -778,7 +778,7 @@
   },"111": {
     "doc": "How To Release",
     "title": "Release Process",
-    "content": ". | Prepare the release artifacts. | Upload the release 
artifacts to the SVN repository. | Verify the release artifacts. | Initiate a 
release vote. | Announce the results and the release. | . Prepare the release 
artifacts. | Create a branch from the target git repository. | Tag a RC and 
draft the release notes. | Build and Sign the release artifacts (including 
source archives, binaries, …etc). | Generate checksums for the artifacts. | . 
How to Sign the release artifacts.  [...]
+    "content": ". | Prepare the release artifacts. | Upload the release 
artifacts to the SVN repository. | Verify the release artifacts. | Initiate a 
release vote. | Announce the results and the release. | . Prepare the release 
artifacts. | Create a branch from the target git repository. | Tag a RC and 
draft the release notes. | Build and Sign the release artifacts (including 
source archives, binaries, …etc). | Generate checksums for the artifacts. | . 
How to Sign the release artifacts.  [...]
     "url": "/docs/developers/how-to-release/#release-process",
     
     "relUrl": "/docs/developers/how-to-release/#release-process"
diff --git a/output/docs/developers/how-to-release/index.html 
b/output/docs/developers/how-to-release/index.html
index 2a074a8..01ea496 100644
--- a/output/docs/developers/how-to-release/index.html
+++ b/output/docs/developers/how-to-release/index.html
@@ -10,7 +10,7 @@
 
 <span class="c"># append the GPG key to the KEYS file the svn repository</span>
 <span class="c"># [IMPORTANT] Don't replace the KEYS file, just append the GPG 
key to the KEYS file. </span>
-<span class="nv">$ </span>svn co 
https://dist.apache.org/repos/dist/release/incubator/answer/
+<span class="nv">$ </span>svn co 
https://dist.apache.org/repos/dist/release/incubator/gluten/
 <span class="nv">$ </span><span class="o">(</span>gpg <span 
class="nt">--list-sigs</span> [email protected] <span class="o">&amp;&amp;</span> 
gpg <span class="nt">--export</span> <span class="nt">--armor</span> 
[email protected]<span class="o">)</span> <span class="o">&gt;&gt;</span> KEYS 
 <span class="nv">$ </span>svn ci <span class="nt">-m</span> <span 
class="s2">"add gpg key"</span> 
 
@@ -21,7 +21,7 @@
 </code></pre></div></div> <h3 
id="upload-the-release-artifacts-to-the-svn-repository"> <a 
href="#upload-the-release-artifacts-to-the-svn-repository" 
class="anchor-heading" 
aria-labelledby="upload-the-release-artifacts-to-the-svn-repository"><svg 
viewBox="0 0 16 16" aria-hidden="true"><use 
xlink:href="#svg-link"></use></svg></a> Upload the release artifacts to the SVN 
repository. </h3> <ol> <li> <p>Create a project directory in the SVN repository 
(1st time only). <code class="language-pla [...]
 <span class="nv">$ </span><span class="nb">cp</span> 
/path/to/release/artifacts/<span class="k">*</span> ./<span 
class="o">{</span>release-version<span class="o">}</span>/
 <span class="nv">$ </span>svn add ./<span 
class="o">{</span>release-version<span class="o">}</span>/<span 
class="k">*</span>
-<span class="nv">$ </span>svn commit <span class="nt">-m</span> <span 
class="s2">"add Apache Answer release artifacts for {release-version}"</span>
+<span class="nv">$ </span>svn commit <span class="nt">-m</span> <span 
class="s2">"add Apache Gluten release artifacts for {release-version}"</span>
 </code></pre></div> </div> </li> <li>After the upload, please visit the link 
<code class="language-plaintext 
highlighter-rouge">https://dist.apache.org/repos/dist/dev/incubator/gluten/{release-version}</code>
 to verify if the file upload is successful or not. The upload release 
artifacts should be include <div class="language-bash highlighter-rouge"><div 
class="highlight"><pre class="highlight"><code><span class="k">*</span> 
apache-gluten-#.#.#-incubating-src.tar.gz
 <span class="k">*</span> apache-gluten-#.#.#-incubating-src.tar.gz.asc
 <span class="k">*</span> apache-gluten-#.#.#-incubating-src.tar.gz.sha512
@@ -85,7 +85,7 @@ Hello,
     [ ] Download links are valid.
     [ ] Checksums and PGP signatures are valid.
     [ ] Source code distributions have correct names matching the current 
release.
-    [ ] LICENSE and NOTICE files are correct for each Apache Answer repo.
+    [ ] LICENSE and NOTICE files are correct for each Apache Gluten repo.
     [ ] All files have license headers if necessary.
     [ ] No unlicensed compiled archives bundled in source archive.
 
@@ -100,7 +100,7 @@ Thanks,
 The Apache Gluten (Incubating) {release-version} has been released!
 
 Apache Gluten is a Q&amp;A platform software for teams at any scale.
-Whether it's a community forum, help center, or knowledge management platform, 
you can always count on Apache Answer.
+Whether it's a community forum, help center, or knowledge management platform, 
you can always count on Apache Gluten.
 
 Download Links: https://downloads.apache.org/incubator/gluten/
 
diff --git a/output/feed.xml b/output/feed.xml
index ca93f8e..f9e7ec1 100644
--- a/output/feed.xml
+++ b/output/feed.xml
@@ -1,4 +1,4 @@
-<?xml version="1.0" encoding="utf-8"?><feed 
xmlns="http://www.w3.org/2005/Atom"; ><generator uri="https://jekyllrb.com/"; 
version="3.9.3">Jekyll</generator><link 
href="https://gluten.apache.org/feed.xml"; rel="self" 
type="application/atom+xml" /><link href="https://gluten.apache.org/"; 
rel="alternate" type="text/html" 
/><updated>2024-11-28T06:37:51+00:00</updated><id>https://gluten.apache.org/feed.xml</id><title
 type="html">Apache Gluten incubating</title><subtitle>Gluten is a middle layer 
r [...]
+<?xml version="1.0" encoding="utf-8"?><feed 
xmlns="http://www.w3.org/2005/Atom"; ><generator uri="https://jekyllrb.com/"; 
version="3.9.3">Jekyll</generator><link 
href="https://gluten.apache.org/feed.xml"; rel="self" 
type="application/atom+xml" /><link href="https://gluten.apache.org/"; 
rel="alternate" type="text/html" 
/><updated>2024-12-04T08:38:32+00:00</updated><id>https://gluten.apache.org/feed.xml</id><title
 type="html">Apache Gluten incubating</title><subtitle>Gluten is a middle layer 
r [...]
 
 &lt;p&gt;What’s new in Gluten 1.2.0&lt;/p&gt;
 


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to