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 f0cc692dccd Publishing website 2023/05/12 22:17:27 at commit fe9ec30
f0cc692dccd is described below
commit f0cc692dccd8c1900ea153104b777bd4c8c42cc0
Author: jenkins <bui...@apache.org>
AuthorDate: Fri May 12 22:17:29 2023 +0000
Publishing website 2023/05/12 22:17:27 at commit fe9ec30
---
.../contribute/committer-guide/index.html | 6 ++-
website/generated-content/contribute/index.xml | 62 ++++++++++++++++------
.../contribute/release-guide/index.html | 18 ++++---
website/generated-content/sitemap.xml | 2 +-
4 files changed, 60 insertions(+), 28 deletions(-)
diff --git a/website/generated-content/contribute/committer-guide/index.html
b/website/generated-content/contribute/committer-guide/index.html
index 2b529fff253..c02aed9f23e 100644
--- a/website/generated-content/contribute/committer-guide/index.html
+++ b/website/generated-content/contribute/committer-guide/index.html
@@ -20,7 +20,7 @@
function addPlaceholder(){$('input:text').attr('placeholder',"What are you
looking for?");}
function endSearch(){var
search=document.querySelector(".searchBar");search.classList.add("disappear");var
icons=document.querySelector("#iconsBar");icons.classList.remove("disappear");}
function blockScroll(){$("body").toggleClass("fixedPosition");}
-function openMenu(){addPlaceholder();blockScroll();}</script><div
class="clearfix container-main-content"><div class="section-nav closed"
data-offset-top=90 data-offset-bottom=500><span class="section-nav-back
glyphicon glyphicon-menu-left"></span><nav><ul class=section-nav-list
data-section-nav><li><span
class=section-nav-list-main-title>Contribute</span></li><li><a
href=/contribute/get-started-contributing>Code contribution
guide</a></li><li><a href=/contribute/get-help/>Get help</a></ [...]
+function openMenu(){addPlaceholder();blockScroll();}</script><div
class="clearfix container-main-content"><div class="section-nav closed"
data-offset-top=90 data-offset-bottom=500><span class="section-nav-back
glyphicon glyphicon-menu-left"></span><nav><ul class=section-nav-list
data-section-nav><li><span
class=section-nav-list-main-title>Contribute</span></li><li><a
href=/contribute/get-started-contributing>Code contribution
guide</a></li><li><a href=/contribute/get-help/>Get help</a></ [...]
<a
href=https://www.apache.org/foundation/how-it-works.html#committers>committers</a>
and covers Beam’s guidelines for reviewing and merging code.</p><h2
id=pull-request-review-objectives>Pull request review objectives</h2><p>The
review process aims for:</p><ul><li>Review iterations should be efficient,
timely and of quality (avoid tiny or out-of-context changes or huge
mega-changes)</li><li>Support efficiency of authoring (don’t want to wait
on a review for a tiny bit because GitHub makes it very hard to stack up
reviews in sequence / don’t want to have [...]
but committer may absorb some extra effort for new contributors)</li><li>Pull
requests and commit messages establish a clear history with purpose and origin
of changes</li><li>Ability to perform a granular rollback, if necessary (also
see <a
href=/contribute/postcommits-policies/>policies</a>)</li></ul><p>Granularity of
changes:</p><ul><li>We prefer small independent, incremental PRs with
descriptive, isolated commits. Each commit is a single clear change</li><li>It
is OK to keep separat [...]
@@ -70,7 +70,9 @@ commit, so be sure the commit history has been curated
appropriately.</p><p>Do <
[BEAM-7873] Fix the foo bizzle bazzle
</code></pre><p>Instead, pull it all into the subject
line:</p><pre><code>Merge pull request #1234: [BEAM-7873] Fix the foo bizzle
bazzle
-</code></pre><p>If you have comments to add, put them in the body of the
commit message.</p><div class=feedback><p class=update>Last updated on
2023/05/12</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 [...]
+</code></pre><p>If you have comments to add, put them in the body of the
commit message.</p><h2 id=seed-jobs>Seed jobs</h2><p>As a committer, you can
now run seed jobs! These are used to update our Jenkins configuration
+and can be run to test PRs modifying Groovy files before they are
merged.</p><p>To make sure you have these permissions, put up a PR adding
yourself to
+<a
href=https://github.com/apache/beam/blob/master/.test-infra/jenkins/Committers.groovy>https://github.com/apache/beam/blob/master/.test-infra/jenkins/Committers.groovy</a></p><div
class=feedback><p class=update>Last updated on 2023/05/12</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 Web [...]
<a href=https://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 class="footer__cols__col
footer__cols__col__logos"><div class=footer__cols__col--group><div
class=footer__cols__col__logo><a href=https://github.com/apache/beam><im [...]
\ No newline at end of file
diff --git a/website/generated-content/contribute/index.xml
b/website/generated-content/contribute/index.xml
index 70ca49e76f3..4fbc1982ebd 100644
--- a/website/generated-content/contribute/index.xml
+++ b/website/generated-content/contribute/index.xml
@@ -167,7 +167,12 @@ commit, so be sure the commit history has been curated
appropriately.</p>
<p>Instead, pull it all into the subject line:</p>
<pre><code>Merge pull request #1234: [BEAM-7873] Fix the foo bizzle
bazzle
</code></pre>
-<p>If you have comments to add, put them in the body of the commit
message.</p></description></item><item><title>Contribute: Beam Contribution
Guide</title><link>/contribute/get-started-contributing/</link><pubDate>Mon, 01
Jan 0001 00:00:00
+0000</pubDate><guid>/contribute/get-started-contributing/</guid><description>
+<p>If you have comments to add, put them in the body of the commit
message.</p>
+<h2 id="seed-jobs">Seed jobs</h2>
+<p>As a committer, you can now run seed jobs! These are used to update our
Jenkins configuration
+and can be run to test PRs modifying Groovy files before they are
merged.</p>
+<p>To make sure you have these permissions, put up a PR adding yourself to
+<a
href="https://github.com/apache/beam/blob/master/.test-infra/jenkins/Committers.groovy";>https://github.com/apache/beam/blob/master/.test-infra/jenkins/Committers.groovy</a></p></description></item><item><title>Contribute:
Beam Contribution
Guide</title><link>/contribute/get-started-contributing/</link><pubDate>Mon, 01
Jan 0001 00:00:00
+0000</pubDate><guid>/contribute/get-started-contributing/</guid><description>
<!--
Licensed under the Apache License, Version 2.0 (the "License");
you may not use this file except in compliance with the License.
@@ -666,11 +671,16 @@ limitations under the License.
<ul>
<li><a href="#checklist-before-proceeding">Checklist before
proceeding</a></li>
<li><a href="#tag-a-chosen-commit-for-the-rc">Tag a chosen commit for
the RC</a></li>
-<li><a
href="#run-build_release_candidatesh-to-create-a-release-candidate">Run
build_release_candidate.sh to create a release candidate</a>
+<li><a
href="#run-build_release_candidate-github-action-to-create-a-release-candidate">Run
build_release_candidate GitHub Action to create a release candidate</a>
<ul>
<li><a href="#tasks-you-need-to-do-manually">Tasks you need to do
manually</a></li>
</ul>
</li>
+<li><a
href="#run-build_release_candidatesh-to-create-a-release-candidate">Run
build_release_candidate.sh to create a release candidate</a>
+<ul>
+<li><a href="#tasks-you-need-to-do-manually-1">Tasks you need to do
manually</a></li>
+</ul>
+</li>
<li><a href="#upload-release-candidate-to-pypi">Upload release candidate
to PyPi</a></li>
</ul>
</li>
@@ -1176,6 +1186,38 @@ adjust the version, and add the tag locally. If it looks
good, run it again with
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_candidate-github-action-to-create-a-release-candidate">Run
build_release_candidate GitHub Action to create a release candidate</h3>
+<p>Note: This step is partially automated (in progress), so part of the rc
creation is done by GitHub Actions and the rest is done by a script.
+You don&rsquo;t need to wait for the action to complete to start running
the script.</p>
+<ul>
+<li>
+<p><strong>Action</strong> <a
href="https://github.com/damccorm/beam/actions/workflows/build_release_candidate.yml";>build_release_candidate</a>
(click <code>run workflow</code>)</p>
+</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>
+</ol>
+</li>
+</ul>
+<h4 id="tasks-you-need-to-do-manually">Tasks you need to do manually</h4>
+<ol>
+<li>Publish staging artifacts
+<ol>
+<li>Log in to the <a
href="https://repository.apache.org/#stagingRepositories";>Apache Nexus</a>
website.</li>
+<li>Navigate to Build Promotion -&gt; Staging Repositories (in the left
sidebar).</li>
+<li>Select repository <code>orgapachebeam-NNNN</code>.</li>
+<li>Click the Close button.</li>
+<li>When prompted for a description, enter “Apache Beam, version X, release
candidate Y”.</li>
+<li>Review all staged artifacts on
<code>https://repository.apache.org/content/repositories/orgapachebeam-NNNN/</code>.
+They should contain all relevant parts for each module, including
<code>pom.xml</code>, jar, test jar, javadoc, etc.
+Artifact names should follow <a
href="https://search.maven.org/#search%7Cga%7C1%7Cg%3A%22org.apache.beam%22";>the
existing format</a> in which artifact name mirrors directory structure,
e.g., <code>beam-sdks-java-io-kafka</code>.
+Carefully review any new artifacts.
+Some additional validation should be done during the rc validation
step.</li>
+</ol>
+</li>
+</ol>
<h3 id="run-build_release_candidatesh-to-create-a-release-candidate">Run
build_release_candidate.sh to create a release candidate</h3>
<ul>
<li>
@@ -1190,7 +1232,6 @@ is perfectly safe since the script does not depend on the
current working tree.&
<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%2Fbeam&amp;type=image";>docker
hub Apache organization</a>.
@@ -1206,7 +1247,7 @@ help with this step. Please email <code>dev@</code>
and ask a member of th
</ol>
</li>
</ul>
-<h4 id="tasks-you-need-to-do-manually">Tasks you need to do manually</h4>
+<h4 id="tasks-you-need-to-do-manually-1">Tasks you need to do
manually</h4>
<ol>
<li>Verify the script worked.
<ol>
@@ -1234,19 +1275,6 @@ ls -al /opt/apache/beam/third_party_licenses/ | wc -l
</code></pre></li>
</ol>
</li>
-<li>Publish staging artifacts
-<ol>
-<li>Log in to the <a
href="https://repository.apache.org/#stagingRepositories";>Apache Nexus</a>
website.</li>
-<li>Navigate to Build Promotion -&gt; Staging Repositories (in the left
sidebar).</li>
-<li>Select repository <code>orgapachebeam-NNNN</code>.</li>
-<li>Click the Close button.</li>
-<li>When prompted for a description, enter “Apache Beam, version X, release
candidate Y”.</li>
-<li>Review all staged artifacts on
<code>https://repository.apache.org/content/repositories/orgapachebeam-NNNN/</code>.
-They should contain all relevant parts for each module, including
<code>pom.xml</code>, jar, test jar, javadoc, etc.
-Artifact names should follow <a
href="https://search.maven.org/#search%7Cga%7C1%7Cg%3A%22org.apache.beam%22";>the
existing format</a> in which artifact name mirrors directory structure,
e.g., <code>beam-sdks-java-io-kafka</code>.
-Carefully review any new artifacts.</li>
-</ol>
-</li>
</ol>
<h3 id="upload-release-candidate-to-pypi">Upload release candidate to
PyPi</h3>
<ul>
diff --git a/website/generated-content/contribute/release-guide/index.html
b/website/generated-content/contribute/release-guide/index.html
index 2c9b75e4749..9bf4d57bb06 100644
--- a/website/generated-content/contribute/release-guide/index.html
+++ b/website/generated-content/contribute/release-guide/index.html
@@ -20,7 +20,7 @@
function addPlaceholder(){$('input:text').attr('placeholder',"What are you
looking for?");}
function endSearch(){var
search=document.querySelector(".searchBar");search.classList.add("disappear");var
icons=document.querySelector("#iconsBar");icons.classList.remove("disappear");}
function blockScroll(){$("body").toggleClass("fixedPosition");}
-function openMenu(){addPlaceholder();blockScroll();}</script><div
class="clearfix container-main-content"><div class="section-nav closed"
data-offset-top=90 data-offset-bottom=500><span class="section-nav-back
glyphicon glyphicon-menu-left"></span><nav><ul class=section-nav-list
data-section-nav><li><span
class=section-nav-list-main-title>Contribute</span></li><li><a
href=/contribute/get-started-contributing>Code contribution
guide</a></li><li><a href=/contribute/get-help/>Get help</a></ [...]
+function openMenu(){addPlaceholder();blockScroll();}</script><div
class="clearfix container-main-content"><div class="section-nav closed"
data-offset-top=90 data-offset-bottom=500><span class="section-nav-back
glyphicon glyphicon-menu-left"></span><nav><ul class=section-nav-list
data-section-nav><li><span
class=section-nav-list-main-title>Contribute</span></li><li><a
href=/contribute/get-started-contributing>Code contribution
guide</a></li><li><a href=/contribute/get-help/>Get help</a></ [...]
A release is one or more packages of the project artifact(s) that are approved
for general public distribution and use.
They may come with various degrees of caveat regarding their perceived quality
and potential for change, such as “alpha”, “beta”, “incubating”, “stable”,
etc.</p><p>The Beam community treats releases with great importance.
They are a public face of the project and most users interact with the project
only through the releases. Releases are signed off by the entire Beam community
in a public vote.</p><p>Each release is executed by a <em>Release Manager</em>,
who is selected among the Beam committers.
@@ -139,19 +139,21 @@ The final state of the repository should match this
diagram:</p><p><img src=/ima
</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><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><
[...]
-</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% [...]
+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_candidate-github-action-to-create-a-release-candidate>Run
build_release_candidate GitHub Action to create a release
candidate</h3><p>Note: This step is partially automated (in progress), so part
of the rc creation is done by GitHub Actions and the rest is done by a script.
+You don’t need to wait for the action to complete to start running the
script.</p><ul><li><p><strong>Action</strong> <a
href=https://github.com/damccorm/beam/actions/workflows/build_release_candidate.yml>build_release_candidate</a>
(click <code>run workflow</code>)</p></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></ol></li></ul><h4 id=tasks-you-need-to-do [...]
+They should contain all relevant parts for each module, including
<code>pom.xml</code>, jar, test jar, javadoc, etc.
+Artifact names should follow <a
href=https://search.maven.org/#search%7Cga%7C1%7Cg%3A%22org.apache.beam%22>the
existing format</a> in which artifact name mirrors directory structure, e.g.,
<code>beam-sdks-java-io-kafka</code>.
+Carefully review any new artifacts.
+Some additional validation should be done during the rc validation
step.</li></ol></li></ol><h3
id=run-build_release_candidatesh-to-create-a-release-candidate>Run
build_release_candidate.sh to create a release
candidate</h3><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_
[...]
+</code></pre></li><li><p><strong>The script will:</strong></p><ol><li>Clone
the repo at the selected RC tag.</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%2Fbeam&type=image";>docker hub
Apache organization</a>.
Note: if you are not a member of the <a
href=https://hub.docker.com/orgs/apache/teams/beammaintainers><code>beammaintainers</code>
DockerHub team</a> you will need
-help with this step. Please email <code>dev@</code> and ask a member of the
<code>beammaintainers</code> DockerHub team for help.</li><li>Create a PR to
update beam-site, changes includes:<ul><li>Copy python doc into
beam-site</li><li>Copy java doc into beam-site</li><li><strong>NOTE</strong>:
Do not merge this PR until after an RC has been approved (see “Finalize
the Release”).</li></ul></li></ol></li></ul><h4
id=tasks-you-need-to-do-manually>Tasks you need to do manually</h [...]
+help with this step. Please email <code>dev@</code> and ask a member of the
<code>beammaintainers</code> DockerHub team for help.</li><li>Create a PR to
update beam-site, changes includes:<ul><li>Copy python doc into
beam-site</li><li>Copy java doc into beam-site</li><li><strong>NOTE</strong>:
Do not merge this PR until after an RC has been approved (see “Finalize
the Release”).</li></ul></li></ol></li></ul><h4
id=tasks-you-need-to-do-manually-1>Tasks you need to do manually< [...]
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 --rm
-it --entrypoint=/bin/bash
apache/beam_python${ver}_sdk:${RELEASE_VERSION}rc${RC_NUM}
ls -al /opt/apache/beam/third_party_licenses/ | wc -l
</code></pre><ul><li>For Java SDK images, there should be around 200
dependencies.</li></ul><pre><code>docker run --rm -it --entrypoint=/bin/bash
apache/beam_java${ver}_sdk:${RELEASE_VERSION}rc${RC_NUM}
ls -al /opt/apache/beam/third_party_licenses/ | wc -l
-</code></pre></li></ol></li><li>Publish staging artifacts<ol><li>Log in to the
<a href=https://repository.apache.org/#stagingRepositories>Apache Nexus</a>
website.</li><li>Navigate to Build Promotion -> Staging Repositories (in the
left sidebar).</li><li>Select repository
<code>orgapachebeam-NNNN</code>.</li><li>Click the Close button.</li><li>When
prompted for a description, enter “Apache Beam, version X, release candidate
Y”.</li><li>Review all staged artifacts on <code>https://reposit [...]
-They should contain all relevant parts for each module, including
<code>pom.xml</code>, jar, test jar, javadoc, etc.
-Artifact names should follow <a
href=https://search.maven.org/#search%7Cga%7C1%7Cg%3A%22org.apache.beam%22>the
existing format</a> in which artifact name mirrors directory structure, e.g.,
<code>beam-sdks-java-io-kafka</code>.
-Carefully review any new artifacts.</li></ol></li></ol><h3
id=upload-release-candidate-to-pypi>Upload release candidate to
PyPi</h3><ul><li><p><strong>Script:</strong> <a
href=https://github.com/apache/beam/blob/master/release/src/main/scripts/deploy_release_candidate_pypi.sh>deploy_release_candidate_pypi.sh</a></p></li><li><p><strong>Usage</strong></p><pre><code>
./release/src/main/scripts/deploy_release_candidate_pypi.sh \
+</code></pre></li></ol></li></ol><h3
id=upload-release-candidate-to-pypi>Upload release candidate to
PyPi</h3><ul><li><p><strong>Script:</strong> <a
href=https://github.com/apache/beam/blob/master/release/src/main/scripts/deploy_release_candidate_pypi.sh>deploy_release_candidate_pypi.sh</a></p></li><li><p><strong>Usage</strong></p><pre><code>
./release/src/main/scripts/deploy_release_candidate_pypi.sh \
--release "${RELEASE_VERSION}" \
--rc "${RC_NUM}" \
--user "${GITHUB_USER}" \
diff --git a/website/generated-content/sitemap.xml
b/website/generated-content/sitemap.xml
index 6856c1669ff..3840951f051 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.47.0/</loc><lastmod>2023-05-12T15:52:45+02:00</lastmod></url><url><loc>/categories/blog/</loc><lastmod>2023-05-12T15:52:45+02:00</lastmod></url><url><loc>/blog/</loc><lastmod>2023-05-12T15:52:45+02:00</lastmod></url><url><loc>/categories/</loc><lastmod>2023-05-12T15:52:45+02:00</lastmod></url><url><loc>/catego
[...]
\ 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.47.0/</loc><lastmod>2023-05-12T16:06:47-04:00</lastmod></url><url><loc>/categories/blog/</loc><lastmod>2023-05-12T16:06:47-04:00</lastmod></url><url><loc>/blog/</loc><lastmod>2023-05-12T16:06:47-04:00</lastmod></url><url><loc>/categories/</loc><lastmod>2023-05-12T16:06:47-04:00</lastmod></url><url><loc>/catego
[...]
\ No newline at end of file
