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/beam.git
The following commit(s) were added to refs/heads/asf-site by this push:
new d250a24 Publishing website 2020/11/07 06:03:18 at commit 405204c
d250a24 is described below
commit d250a243674a92be424c22ff5138c3e923203c7b
Author: jenkins <[email protected]>
AuthorDate: Sat Nov 7 06:03:18 2020 +0000
Publishing website 2020/11/07 06:03:18 at commit 405204c
---
website/generated-content/contribute/index.xml | 9 +++++++--
website/generated-content/contribute/release-guide/index.html | 6 +++---
website/generated-content/sitemap.xml | 2 +-
3 files changed, 11 insertions(+), 6 deletions(-)
diff --git a/website/generated-content/contribute/index.xml
b/website/generated-content/contribute/index.xml
index e2e0828..c7ff395 100644
--- a/website/generated-content/contribute/index.xml
+++ b/website/generated-content/contribute/index.xml
@@ -315,6 +315,7 @@ limitations under the License.
<li><a href="#deploy-sdk-docker-images-to-dockerhub">Deploy SDK docker
images to DockerHub</a></li>
<li><a href="#merge-website-pull-requests">Merge Website pull
requests</a></li>
<li><a href="#git-tag">Git tag</a></li>
+<li><a href="#publish-release-to-github">Publish release to
Github</a></li>
<li><a href="#pmc-only-finalization">PMC-Only Finalization</a>
<ul>
<li><a href="#deploy-source-release-to-distapacheorg">Deploy source
release to dist.apache.org</a></li>
@@ -1367,9 +1368,12 @@ All wheels should be published, in addition to the zip
of the release source.
<pre><code>VERSION_TAG=&quot;v${RELEASE}&quot;
git tag -s &quot;$VERSION_TAG&quot; &quot;$RC_TAG&quot;
git push https://github.com/apache/beam &quot;$VERSION_TAG&quot;
-</code></pre><p>After the tag is uploaded, publish the release notes
to Github, as follows:</p>
+</code></pre><p>After pushing the tag, the tag should be visible on
Github&rsquo;s <a href="https://github.com/apache/beam/tags";>Tags</a>
page.</p>
+<h3 id="publish-release-to-github">Publish release to Github</h3>
+<p>Once the tag is uploaded, publish the release notes to Github, as
follows:</p>
<pre><code>cd beam/release/src/main/scripts &amp;&amp;
./publish_github_release_notes.sh
</code></pre><p>Note this script reads the release notes from the
blog post, so you should make sure to run this from master <em>after</em>
merging the blog post PR.</p>
+<p>After running the script, the release notes should be visible on
Github&rsquo;s <a
href="https://github.com/apache/beam/releases";>Releases</a> page.</p>
<h3 id="pmc-only-finalization">PMC-Only Finalization</h3>
<p>There are a few release finalization tasks that only PMC members have
permissions to do. Ping <a href="mailto:[email protected]";>dev@</a>
for assistance if you need it.</p>
<h4 id="deploy-source-release-to-distapacheorg">Deploy source release to
dist.apache.org</h4>
@@ -1385,7 +1389,8 @@ git push https://github.com/apache/beam
&quot;$VERSION_TAG&quot;
<li>Source distribution available in the release repository of <a
href="https://dist.apache.org/repos/dist/release/beam/";>dist.apache.org</a></li>
<li>Source distribution removed from the dev repository of <a
href="https://dist.apache.org/repos/dist/dev/beam/";>dist.apache.org</a></li>
<li>Website pull request to <a href="/get-started/downloads/">list the
release</a> and publish the <a
href="https://beam.apache.org/releases/javadoc/";>API reference manual</a>
merged</li>
-<li>Release tagged in the source code repository</li>
+<li>The release is tagged on Github&rsquo;s <a
href="https://github.com/apache/beam/tags";>Tags</a> page.</li>
+<li>The release notes are published on Github&rsquo;s <a
href="https://github.com/apache/beam/releases";>Releases</a> page.</li>
<li>Release version finalized in JIRA. (Note: Not all committers have
administrator access to JIRA. If you end up getting permissions errors ask on
the mailing list for assistance.)</li>
<li>Release version is listed at reporter.apache.org</li>
</ul>
diff --git a/website/generated-content/contribute/release-guide/index.html
b/website/generated-content/contribute/release-guide/index.html
index 44e6758..37e0c7c 100644
--- a/website/generated-content/contribute/release-guide/index.html
+++ b/website/generated-content/contribute/release-guide/index.html
@@ -1,7 +1,7 @@
<!doctype html><html lang=en class=no-js><head><meta charset=utf-8><meta
http-equiv=x-ua-compatible content="IE=edge"><meta name=viewport
content="width=device-width,initial-scale=1"><title>Beam Release
Guide</title><meta name=description content="Apache Beam is an open source,
unified model and set of language-specific SDKs for defining and executing data
processing workflows, and also data ingestion and integration flows, supporting
Enterprise Integration Patterns (EIPs) and Domain Spe [...]
<span class=sr-only>Toggle navigation</span>
<span class=icon-bar></span><span class=icon-bar></span><span
class=icon-bar></span></button>
-<a href=/ class=navbar-brand><img alt=Brand style=height:25px
src=/images/beam_logo_navbar.png></a></div><div class="navbar-mask
closed"></div><div id=navbar class="navbar-container closed"><ul class="nav
navbar-nav"><li><a href=/get-started/beam-overview/>Get Started</a></li><li><a
href=/documentation/>Documentation</a></li><li><a
href=/documentation/sdks/java/>Languages</a></li><li><a
href=/documentation/runners/capability-matrix/>RUNNERS</a></li><li><a
href=/roadmap/>Roadmap</a></li>< [...]
+<a href=/ class=navbar-brand><img alt=Brand style=height:25px
src=/images/beam_logo_navbar.png></a></div><div class="navbar-mask
closed"></div><div id=navbar class="navbar-container closed"><ul class="nav
navbar-nav"><li><a href=/get-started/beam-overview/>Get Started</a></li><li><a
href=/documentation/>Documentation</a></li><li><a
href=/documentation/sdks/java/>Languages</a></li><li><a
href=/documentation/runners/capability-matrix/>RUNNERS</a></li><li><a
href=/roadmap/>Roadmap</a></li>< [...]
please follow <a
href=https://help.github.com/articles/creating-a-personal-access-token-for-the-command-line/>the
guide</a> to configure command line access.</p><h3
id=accounts>Accounts</h3><p>Please have these credentials ready at hand, you
will likely need to enter them multiple times:</p><ul><li>GPG pass phrase (see
the next section);</li><li>Apache ID and Password;</li><li>GitHub ID and
Password.</li><li>DockerHub ID and Password. (You should be a member of
maintainer team; email at [...]
or running all commands manually.</p><h5
id=use-preparation_before_releasesh-to-setup-gpg>Use
preparation_before_release.sh to setup GPG</h5><ul><li><p>Script: <a
href=https://github.com/apache/beam/blob/master/release/src/main/scripts/preparation_before_release.sh>preparation_before_release.sh</a></p></li><li><p>Usage</p><pre><code>./beam/release/src/main/scripts/preparation_before_release.sh
</code></pre></li><li><p>Tasks included</p><ol><li><p>Help you create a new
GPG key if you want.</p></li><li><p>Configure <code>git user.signingkey</code>
with chosen pubkey.</p></li><li><p>Add chosen pubkey into <a
href=https://dist.apache.org/repos/dist/dev/beam/KEYS>dev KEYS</a> and <a
href=https://dist.apache.org/repos/dist/release/beam/KEYS>release
KEYS</a></p><p><strong>NOTES</strong>: Only PMC can write into <a
href=https://dist.apache.org/repos/dist/release/beam/>release repo</a> [...]
@@ -343,8 +343,8 @@ All wheels should be published, in addition to the zip of
the release source.
</code></pre><p>Verify that:</p><ul><li>Images are published at <a
href="https://hub.docker.com/search?q=apache%2Fbeam&type=image";>DockerHub</a>
with tags {RELEASE} and <em>latest</em>.</li><li>Images with <em>latest</em>
tag are pointing to current release by confirming<ol><li>Digest of the image
with <em>latest</em> tag is the same as the one with {RELEASE}
tag.</li></ol></li></ul><h3 id=merge-website-pull-requests>Merge Website pull
requests</h3><p>Merge all of the website pull reques [...]
git tag -s "$VERSION_TAG" "$RC_TAG"
git push https://github.com/apache/beam "$VERSION_TAG"
-</code></pre><p>After the tag is uploaded, publish the release notes to
Github, as follows:</p><pre><code>cd beam/release/src/main/scripts &&
./publish_github_release_notes.sh
-</code></pre><p>Note this script reads the release notes from the blog post,
so you should make sure to run this from master <em>after</em> merging the blog
post PR.</p><h3 id=pmc-only-finalization>PMC-Only Finalization</h3><p>There are
a few release finalization tasks that only PMC members have permissions to do.
Ping <a href=mailto:[email protected]>dev@</a> for assistance if you need
it.</p><h4 id=deploy-source-release-to-distapacheorg>Deploy source release to
dist.apache.org</h4><p [...]
+</code></pre><p>After pushing the tag, the tag should be visible on
Github’s <a href=https://github.com/apache/beam/tags>Tags</a>
page.</p><h3 id=publish-release-to-github>Publish release to Github</h3><p>Once
the tag is uploaded, publish the release notes to Github, as
follows:</p><pre><code>cd beam/release/src/main/scripts &&
./publish_github_release_notes.sh
+</code></pre><p>Note this script reads the release notes from the blog post,
so you should make sure to run this from master <em>after</em> merging the blog
post PR.</p><p>After running the script, the release notes should be visible on
Github’s <a href=https://github.com/apache/beam/releases>Releases</a>
page.</p><h3 id=pmc-only-finalization>PMC-Only Finalization</h3><p>There are a
few release finalization tasks that only PMC members have permissions to do.
Ping <a href=mailto:dev [...]
<strong>NOTE</strong>: This can only be done from <code>@apache.org</code>
email address.</p><h3 id=social-media>Social media</h3><p>Tweet, post on
Facebook, LinkedIn, and other platforms. Ask other contributors to do the
same.</p><p>Also, update <a href=https://en.wikipedia.org/wiki/Apache_Beam>the
Wikipedia article on Apache Beam</a>.</p><h3
id=checklist-to-declare-the-process-completed>Checklist to declare the process
completed</h3><ol><li>Release announced on the user@ mailing list.< [...]
<a href=http://www.apache.org>The Apache Software Foundation</a>
| <a href=/privacy_policy>Privacy Policy</a>
diff --git a/website/generated-content/sitemap.xml
b/website/generated-content/sitemap.xml
index 56688a7..ce1afb0 100644
--- a/website/generated-content/sitemap.xml
+++ b/website/generated-content/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>/blog/beam-2.25.0/</loc><lastmod>2020-10-29T14:08:19-07:00</lastmod></url><url><loc>/categories/blog/</loc><lastmod>2020-10-29T14:08:19-07:00</lastmod></url><url><loc>/blog/</loc><lastmod>2020-10-29T14:08:19-07:00</lastmod></url><url><loc>/categories/</loc><lastmod>2020-10-29T14:08:19-07:00</lastmod></url><url><loc>/blog/b
[...]
\ 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>/blog/beam-2.25.0/</loc><lastmod>2020-10-29T14:08:19-07:00</lastmod></url><url><loc>/categories/blog/</loc><lastmod>2020-10-29T14:08:19-07:00</lastmod></url><url><loc>/blog/</loc><lastmod>2020-10-29T14:08:19-07:00</lastmod></url><url><loc>/categories/</loc><lastmod>2020-10-29T14:08:19-07:00</lastmod></url><url><loc>/blog/b
[...]
\ No newline at end of file
