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 924a7c7 Publishing website 2021/11/30 00:03:25 at commit 33bcdf6
924a7c7 is described below
commit 924a7c77db1c79a5f8ccb07cfbd318fc2d5a100b
Author: jenkins <bui...@apache.org>
AuthorDate: Tue Nov 30 00:03:26 2021 +0000
Publishing website 2021/11/30 00:03:25 at commit 33bcdf6
---
website/generated-content/contribute/index.xml | 18 +++++++++++-------
.../contribute/release-guide/index.html | 16 ++++++++--------
website/generated-content/sitemap.xml | 2 +-
3 files changed, 20 insertions(+), 16 deletions(-)
diff --git a/website/generated-content/contribute/index.xml
b/website/generated-content/contribute/index.xml
index 44366ae..4da81a2 100644
--- a/website/generated-content/contribute/index.xml
+++ b/website/generated-content/contribute/index.xml
@@ -498,11 +498,11 @@ If you don’t have a GPG key associated with your Apache
account, please create
</code></pre>
<p>This will list your GPG keys. One of these should reflect your Apache
account, for example:</p>
<pre><code>--------------------------------------------------
-pub 2048R/845E6689 2016-02-23
+pub rsa4096/845E6689845E6689 2016-02-23
uid Nomen Nescio &lt;anonym...@apache.org&gt;
-sub 2048R/BA4D50BE 2016-02-23
+sub rsa4096/BA4D50BEBA4D50BE 2016-02-23
</code></pre>
-<p>Here, the key ID is the 8-digit hex string in the <code>pub</code>
line: <code>845E6689</code>.</p>
+<p>Here, the key ID is the 16-digit hex string in the
<code>pub</code> line: <code>845E6689845E6689</code>.</p>
</li>
</ul>
<h4 id="access-to-apache-nexus-repository">Access to Apache Nexus
repository</h4>
@@ -911,7 +911,7 @@ is perfectly safe since the script does not depend on the
current working tree.&
</li>
<li>
<p><strong>Usage</strong></p>
-<pre><code>./beam/release/src/main/scripts/build_release_candidate.sh
+<pre><code>./beam/release/src/main/scripts/build_release_candidate.sh
--release &quot;${RELEASE_VERSION}&quot; --rc
&quot;${RC_NUM}&quot; --github-user &quot;${GITHUB_USER}&quot;
</code></pre>
</li>
<li>
@@ -1164,8 +1164,6 @@ versions to run all of the tests. See Python installation
tips in <a href="ht
<li>
<p><strong>Tasks included</strong></p>
<ol>
-<li>Run Java quickstart with Direct Runner, Flink local runner, Spark local
runner and Dataflow runner.</li>
-<li>Run Java Mobile Games(UserScore, HourlyTeamScore, Leaderboard) with
Dataflow runner.</li>
<li>Create a PR to trigger python validation job, including
<ul>
<li>Python quickstart in batch and streaming mode with direct runner and
Dataflow runner.</li>
@@ -1188,6 +1186,12 @@ versions to run all of the tests. See Python
installation tips in <a href="ht
<ol>
<li>Check whether validations succeed by following console output
instructions.</li>
<li>Terminate streaming jobs and java injector.</li>
+<li>Run Java quickstart (wordcount) and mobile game examples with the
staged artifacts. The easiest way to do this is by running the tests on
Jenkins.</li>
+<li>Log in to Jenkins.</li>
+<li>Go to <a
href="https://ci-beam.apache.org/job/beam_PostRelease_NightlySnapshot/";>https://ci-beam.apache.org/job/beam_PostRelease_NightlySnapshot/</a>.</li>
+<li>Click &ldquo;Build with Parameters&rdquo;.</li>
+<li>Set <code>snapshot_version</code> to <code>2.xx.0</code>,
and set <code>snapshot_url</code> to point to the staged artifacts in
Maven central (<a
href="https://repository.apache.org/content/repositories/orgapachebeam-NNNN/)">https://repository.apache.org/content/repositories/orgapachebeam-NNNN/)</a>.</li>
+<li>Click &ldquo;Build&rdquo;.</li>
<li>Sign up <a
href="https://s.apache.org/beam-release-validation";>spreadsheet</a>.</li>
<li>Vote in the release thread.</li>
</ol>
@@ -1482,7 +1486,7 @@ git push https://github.com/apache/beam
&quot;$VERSION_TAG&quot;
</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
+<pre><code>./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&rsquo;s <a
href="https://github.com/apache/beam/releases";>Releases</a> page.</p>
<h3 id="pmc-only-finalization">PMC-Only Finalization</h3>
diff --git a/website/generated-content/contribute/release-guide/index.html
b/website/generated-content/contribute/release-guide/index.html
index 81bf642..5cff981 100644
--- a/website/generated-content/contribute/release-guide/index.html
+++ b/website/generated-content/contribute/release-guide/index.html
@@ -36,10 +36,10 @@ Please be aware of the ASF-wide <a
href=https://www.apache.org/dev/release-signi
If you don’t have a GPG key associated with your Apache account, please create
one according to the guidelines.</p><p>There are 2 ways to configure your GPG
key for release, either using release automation script(which is recommended),
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><strong>Script:</strong> <a
href=https://github.com/apache/beam/blob/master/release/src/main/scripts/pre
[...]
</code></pre></li><li><p><strong>Tasks included</strong></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/ [...]
</code></pre><p>This will list your GPG keys. One of these should reflect your
Apache account, for
example:</p><pre><code>--------------------------------------------------
-pub 2048R/845E6689 2016-02-23
+pub rsa4096/845E6689845E6689 2016-02-23
uid Nomen Nescio <anonym...@apache.org>
-sub 2048R/BA4D50BE 2016-02-23
-</code></pre><p>Here, the key ID is the 8-digit hex string in the
<code>pub</code> line: <code>845E6689</code>.</p></li></ul><h4
id=access-to-apache-nexus-repository>Access to Apache Nexus
repository</h4><p>Configure access to the <a
href=https://repository.apache.org/>Apache Nexus repository</a>, which enables
final deployment of releases to the Maven Central Repository.</p><ol><li><p>You
log in with your Apache account.</p></li><li><p>Confirm you have appropriate
access by finding <cod [...]
+sub rsa4096/BA4D50BEBA4D50BE 2016-02-23
+</code></pre><p>Here, the key ID is the 16-digit hex string in the
<code>pub</code> line: <code>845E6689845E6689</code>.</p></li></ul><h4
id=access-to-apache-nexus-repository>Access to Apache Nexus
repository</h4><p>Configure access to the <a
href=https://repository.apache.org/>Apache Nexus repository</a>, which enables
final deployment of releases to the Maven Central Repository.</p><ol><li><p>You
log in with your Apache account.</p></li><li><p>Confirm you have appropriate
access by fin [...]
<settings>
<servers>
<server>
@@ -145,14 +145,14 @@ Before building, the version must be set to a
non-SNAPSHOT, non-dev version.
The final state of the repository should match this diagram:</p><p><img
src=/images/tag-rc-commit.png alt="Set version to non-SNAPSHOT, non-dev, on
tagged RC commit" width=100%></p><ul><li>The release branch is
unchanged.</li><li>There is a commit not on the release branch with the version
adjusted.</li><li>The RC tag points to that
commit.</li></ul><ul><li><p><strong>Script:</strong> <a
href=https://github.com/apache/beam/blob/master/release/src/main/scripts/choose_rc_commit.sh>choose_r
[...]
--release "${RELEASE_VERSION}" \
--rc "${RC_NUM}" \
---commit "${COMMIT_REF}" \
+ --commit "${COMMIT_REF}" \
--clone \
--push-tag
</code></pre></li></ul><p>You can do a dry run by omitting the
<code>--push-tag</code> flag. Then it will only clone the repo,
adjust the version, and add the tag locally. If it looks good, run it again
with <code>--push-tag</code>.
If you already have a clone that includes the <code>${COMMIT_REF}</code> then
you can omit <code>--clone</code>. This
is perfectly safe since the script does not depend on the current working
tree.</p><p>See the source of the script for more details, or to run commands
manually in case of a problem.</p><h3
id=run-build_release_candidatesh-to-create-a-release-candidate>Run
build_release_candidate.sh to create a release candidate</h3><p>Before you
start, run this command to make sure you’ll be using the latest docker
images:</p><pre><code> docker system prune -a
-</code></pre><ul><li><p><strong>Script:</strong> <a
href=https://github.com/apache/beam/blob/master/release/src/main/scripts/build_release_candidate.sh>build_release_candidate.sh</a></p></li><li><p><strong>Usage</strong></p><pre><code>./beam/release/src/main/scripts/build_release_candidate.sh
+</code></pre><ul><li><p><strong>Script:</strong> <a
href=https://github.com/apache/beam/blob/master/release/src/main/scripts/build_release_candidate.sh>build_release_candidate.sh</a></p></li><li><p><strong>Usage</strong></p><pre><code>./beam/release/src/main/scripts/build_release_candidate.sh
--release "${RELEASE_VERSION}" --rc "${RC_NUM}"
--github-user "${GITHUB_USER}"
</code></pre></li><li><p><strong>The script will:</strong></p><ol><li>Clone
the repo at the selected RC tag.</li><li>Run gradle publish to push java
artifacts into Maven staging repo.</li><li>Stage source release into
dist.apache.org dev <a
href=https://dist.apache.org/repos/dist/dev/beam/>repo</a>.</li><li>Stage, sign
and hash python source distribution and wheels into dist.apache.org dev repo
python dir</li><li>Stage SDK docker images to <a
href="https://hub.docker.com/search?q=apache% [...]
Please note that dependencies for the SDKs with different Python versions vary.
Need to verify all Python images by replacing <code>${ver}</code> with each
supported Python version <code>X.Y</code>.</li></ul><pre><code>docker run -it
--entrypoint=/bin/bash apache/beam_python${ver}_sdk:${RELEASE}_rc{RC_NUM}
@@ -278,7 +278,7 @@ For example, if an issue is found in the website pull
request, just correct it o
In case of script failure, you can still run all of them manually.</p><p>You
may need to have Python interpreters for all supported Python minor
versions to run all of the tests. See Python installation tips in <a
href=https://cwiki.apache.org/confluence/display/BEAM/Python+Tips#PythonTips-InstallingPythoninterpreters>Developer
Wiki</a>.</p><h4 id=run-validations-using-run_rc_validationsh>Run validations
using run_rc_validation.sh</h4><ul><li><p><strong>Script:</strong> <a
href=https://github.com/apache/beam/blob/master/release/src/main/scripts/run_rc_validation.sh>run_rc_validation.sh</a></p></li><li><p><strong>Usage</strong></p
[...]
<a
href=https://github.com/apache/beam/blob/master/release/src/main/scripts/script.config>script.config</a></li><li>Then
run<pre><code>./beam/release/src/main/scripts/run_rc_validation.sh
-</code></pre></li></ol></li><li><p><strong>Tasks
included</strong></p><ol><li>Run Java quickstart with Direct Runner, Flink
local runner, Spark local runner and Dataflow runner.</li><li>Run Java Mobile
Games(UserScore, HourlyTeamScore, Leaderboard) with Dataflow
runner.</li><li>Create a PR to trigger python validation job,
including<ul><li>Python quickstart in batch and streaming mode with direct
runner and Dataflow runner.</li><li>Python Mobile Games(UserScore,
HourlyTeamScore) with dir [...]
+</code></pre></li></ol></li><li><p><strong>Tasks
included</strong></p><ol><li>Create a PR to trigger python validation job,
including<ul><li>Python quickstart in batch and streaming mode with direct
runner and Dataflow runner.</li><li>Python Mobile Games(UserScore,
HourlyTeamScore) with direct runner and Dataflow runner.</li></ul></li><li>Run
Python Streaming MobileGames, includes<ul><li>Start a new terminal to run Java
Pubsub injector.</li><li>Start a new terminal to run python LeaderBo [...]
-Prepourl=https://repository.apache.org/content/repositories/orgapachebeam-${KEY}
\
-Pver=${RELEASE_VERSION}
</code></pre><p><strong>Flink Local Runner</strong></p><pre><code>./gradlew
:runners:flink:1.13:runQuickstartJavaFlinkLocal \
@@ -412,7 +412,7 @@ git push https://github.com/apache/beam
"sdks/$VERSION_TAG"
# Tag for repo root.
git tag -s "$VERSION_TAG" "$RC_TAG"
git push https://github.com/apache/beam "$VERSION_TAG"
-</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>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>./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:d...@beam.apache.org>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>Copy the source release from the <code>dev</code>
repository to the <code>release</code> repository at
<code>dist.apache.org</code> using Subversion.</p><p>Make sure the last
release’s artifacts have been copied from <code>dist.apache.org</code> to
<code>archive.apache.org</code>.
This should happen automatically: <a
href=https://lists.apache.org/thread.html/39c26c57c5125a7ca06c3c9315b4917b86cd0e4567b7174f4bc4d63b%40%3Cdev.beam.apache.org%3E>dev@
thread</a> with context.
@@ -424,7 +424,7 @@ If you end up getting permissions errors ask on the mailing
list for assistance.
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.</li><li>Blog post published, if applicable.</li><li>Release
recorded in reporter.apache.org.</li><li>Release announced on social
media.</li><li>Completion declared on the dev@ mailing list. [...]
Once you’ve finished the release, please take a step back and look what areas
of this process and be improved. Perhaps some part of the process can be
simplified.
Perhaps parts of this guide can be clarified.</p><p>If we have specific ideas,
please start a discussion on the dev@ mailing list and/or propose a pull
request to update this guide.
-Thanks!</p><div class=feedback><p class=update>Last updated on
2021/11/17</p><h3>Have you found everything you were looking for?</h3><p
class=description>Was it all useful and clear? Is there anything that you would
like to change? Let us know!</p><button class=load-button><a
href="mailto:d...@beam.apache.org?subject=Beam Website Feedback">SEND
FEEDBACK</a></button></div></div></div><footer class=footer><div
class=footer__contained><div class=footer__cols><div class="footer__cols__col
foo [...]
+Thanks!</p><div class=feedback><p class=update>Last updated on
2021/11/24</p><h3>Have you found everything you were looking for?</h3><p
class=description>Was it all useful and clear? Is there anything that you would
like to change? Let us know!</p><button class=load-button><a
href="mailto:d...@beam.apache.org?subject=Beam Website Feedback">SEND
FEEDBACK</a></button></div></div></div><footer class=footer><div
class=footer__contained><div class=footer__cols><div class="footer__cols__col
foo [...]
<a href=http://www.apache.org>The Apache Software Foundation</a>
| <a href=/privacy_policy>Privacy Policy</a>
| <a href=/feed.xml>RSS Feed</a><br><br>Apache Beam, Apache, Beam, the Beam
logo, and the Apache feather logo are either registered trademarks or
trademarks of The Apache Software Foundation. All other products or name brands
are trademarks of their respective holders, including The Apache Software
Foundation.</div></div></div></div></footer></body></html>
\ No newline at end of file
diff --git a/website/generated-content/sitemap.xml
b/website/generated-content/sitemap.xml
index 3e3e6cc..bd4d515 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.34.0/</loc><lastmod>2021-11-11T11:07:06-08:00</lastmod></url><url><loc>/categories/blog/</loc><lastmod>2021-11-11T11:07:06-08:00</lastmod></url><url><loc>/blog/</loc><lastmod>2021-11-11T11:07:06-08:00</lastmod></url><url><loc>/categories/</loc><lastmod>2021-11-11T11:07:06-08:00</lastmod></url><url><loc>/blog/g
[...]
\ 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.34.0/</loc><lastmod>2021-11-11T11:07:06-08:00</lastmod></url><url><loc>/categories/blog/</loc><lastmod>2021-11-11T11:07:06-08:00</lastmod></url><url><loc>/blog/</loc><lastmod>2021-11-11T11:07:06-08:00</lastmod></url><url><loc>/categories/</loc><lastmod>2021-11-11T11:07:06-08:00</lastmod></url><url><loc>/blog/g
[...]
\ No newline at end of file
