You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@beam.apache.org by gi...@apache.org on 2023/05/09 22:18:35 UTC
[beam] branch asf-site updated: Publishing website 2023/05/09 22:18:29 at commit 60ac868
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 1354257a57e Publishing website 2023/05/09 22:18:29 at commit 60ac868
1354257a57e is described below
commit 1354257a57e5852d67db76954dcc3282b40fd47c
Author: jenkins <bu...@apache.org>
AuthorDate: Tue May 9 22:18:29 2023 +0000
Publishing website 2023/05/09 22:18:29 at commit 60ac868
---
website/generated-content/contribute/index.xml | 10 +++++-----
website/generated-content/contribute/release-guide/index.html | 10 +++++-----
website/generated-content/documentation/index.xml | 6 ++++++
.../documentation/programming-guide/index.html | 8 ++++++--
website/generated-content/sitemap.xml | 2 +-
5 files changed, 23 insertions(+), 13 deletions(-)
diff --git a/website/generated-content/contribute/index.xml b/website/generated-content/contribute/index.xml
index 60f7c0e38e5..263b1ca4291 100644
--- a/website/generated-content/contribute/index.xml
+++ b/website/generated-content/contribute/index.xml
@@ -872,8 +872,7 @@ sub rsa4096/BA4D50BEBA4D50BE 2016-02-23
</ol>
<h4 id="submit-your-gpg-public-key-into-mit-pgp-public-key-server">Submit your GPG public key into MIT PGP Public Key Server</h4>
<p>In order to make yourself have right permission to stage java artifacts in Apache Nexus staging repository,
-please submit your GPG public key into <a href="http://pgp.mit.edu:11371/">MIT PGP Public Key Server</a>.</p>
-<p>If MIT doesn&rsquo;t work for you (it probably won&rsquo;t, it&rsquo;s slow, returns 502 a lot, Nexus might error out not being able to find the keys), use a keyserver at <code>ubuntu.com</code> instead: <a href="https://keyserver.ubuntu.com/">https://keyserver.ubuntu.com/</a>.</p>
+please submit your GPG public key into the <a href="https://keyserver.ubuntu.com/">Ubuntu OpenPGP Key Server</a>.</p>
<p>You will need to use an ascii-armored version of your key.
This can be obtained by running <code>gpg --export --armor</code> and copying the whole block
(including <code>-----&lt;START/END&gt; PGP PUBLIC KEY BLOCK-----</code>).</p>
@@ -1201,6 +1200,7 @@ help with this step. Please email <code>dev@</code> and ask a member of th
<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 &ldquo;Finalize the Release&rdquo;).</li>
</ul>
</li>
</ol>
@@ -1224,12 +1224,12 @@ help with this step. Please email <code>dev@</code> and ask a member of th
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}
+<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}
+<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>
@@ -1389,7 +1389,7 @@ ${CONTRIBUTORS}
<li>Pull docker images to make sure they are pullable.</li>
</ol>
<pre><code>docker pull {image_name}
-docker pull apache/beam_python3.7_sdk:2.39.0_rc1
+docker pull apache/beam_python3.7_sdk:2.39.0rc1
</code></pre><hr>
<h2 id="10-vote-and-validate-release-candidate">10. Vote and validate release candidate</h2>
<p>Once you have built and individually reviewed the release candidate, please share it for the community-wide review.
diff --git a/website/generated-content/contribute/release-guide/index.html b/website/generated-content/contribute/release-guide/index.html
index d8187b4a378..b8b9ccd7111 100644
--- a/website/generated-content/contribute/release-guide/index.html
+++ b/website/generated-content/contribute/release-guide/index.html
@@ -57,7 +57,7 @@ sub rsa4096/BA4D50BEBA4D50BE 2016-02-23
</servers>
</settings>
</code></pre></li></ol><h4 id=submit-your-gpg-public-key-into-mit-pgp-public-key-server>Submit your GPG public key into MIT PGP Public Key Server</h4><p>In order to make yourself have right permission to stage java artifacts in Apache Nexus staging repository,
-please submit your GPG public key into <a href=http://pgp.mit.edu:11371/>MIT PGP Public Key Server</a>.</p><p>If MIT doesn’t work for you (it probably won’t, it’s slow, returns 502 a lot, Nexus might error out not being able to find the keys), use a keyserver at <code>ubuntu.com</code> instead: <a href=https://keyserver.ubuntu.com/>https://keyserver.ubuntu.com/</a>.</p><p>You will need to use an ascii-armored version of your key.
+please submit your GPG public key into the <a href=https://keyserver.ubuntu.com/>Ubuntu OpenPGP Key Server</a>.</p><p>You will need to use an ascii-armored version of your key.
This can be obtained by running <code>gpg --export --armor</code> and copying the whole block
(including <code>-----<START/END> PGP PUBLIC KEY BLOCK-----</code>).</p><h4 id=website-development-setup>Website development setup</h4><p>Updating the Beam website requires submitting PRs to both the main <code>apache/beam</code> repo and the <code>apache/beam-site</code> repo.
The first contains reference manuals generated from SDK code, while the second updates the current release version number.</p><p>You should already have setup a local clone of <code>apache/beam</code>.
@@ -142,11 +142,11 @@ If you already have a clone that includes the <code>${COMMIT_REF}</code> then yo
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% [...]
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></ul></li></ol></li></ul><h4 id=tasks-you-need-to-do-manually>Tasks you need to do manually</h4><ol><li>Verify the script worked.<ol><li>Verify that the source and Python binaries are present in <a href=https://dist.apache.o [...]
+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 [...]
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}
+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}
+</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.
@@ -235,7 +235,7 @@ According to git shortlog, the following people contributed to the {$RELEASE_VER
${CONTRIBUTORS}
</code></pre><h4 id=checklist-to-proceed-to-the-next-step-1>Checklist to proceed to the next step</h4><ol><li>Maven artifacts deployed to the staging repository of <a href=https://repository.apache.org/content/repositories/>repository.apache.org</a></li><li>Source distribution deployed to the dev repository of <a href=https://dist.apache.org/repos/dist/dev/beam/>dist.apache.org</a></li><li>Website pull request proposed to list the <a href=/get-started/downloads/>release</a>, publish the [...]
-docker pull apache/beam_python3.7_sdk:2.39.0_rc1
+docker pull apache/beam_python3.7_sdk:2.39.0rc1
</code></pre><hr><h2 id=10-vote-and-validate-release-candidate>10. Vote and validate release candidate</h2><p>Once you have built and individually reviewed the release candidate, please share it for the community-wide review.
Please review foundation-wide <a href=https://www.apache.org/foundation/voting.html>voting guidelines</a> for more information.</p><p>Start the review-and-vote thread on the dev@ mailing list.
Here’s an email template; please adjust as you see fit.</p><pre><code>From: Release Manager
diff --git a/website/generated-content/documentation/index.xml b/website/generated-content/documentation/index.xml
index ad8ca80f2d1..adc3e24ecf8 100644
--- a/website/generated-content/documentation/index.xml
+++ b/website/generated-content/documentation/index.xml
@@ -5261,6 +5261,9 @@ with a single `root` object and is passed to a Runner's `run` method.
</code></pre></div>
</div>
</div>
+<p>For a more in-depth tutorial on creating basic pipelines
+in the Python SDK, please read and work through
+<a href="https://colab.sandbox.google.com/github/apache/beam/blob/master/examples/notebooks/get-started/learn_beam_basics_by_doing.ipynb">this colab notebook</a>.</p>
<h3 id="configuring-pipeline-options">2.1. Configuring pipeline options</h3>
<p>Use the pipeline options to configure different aspects of your pipeline, such
as the pipeline runner that will execute your pipeline and any runner-specific
@@ -5753,6 +5756,9 @@ such as <a href="#pardo">ParDo</a> or <a href="#combine">Combine</a>
combine one or more of the core transforms in a useful processing pattern, such
as counting or combining elements in a collection. You can also define your own
more complex composite transforms to fit your pipeline&rsquo;s exact use case.</p>
+<p>For a more in-depth tutorial of applying various transforms
+in the Python SDK, please read and work through
+<a href="https://colab.sandbox.google.com/github/liferoad/beam/blob/learn-transforms/examples/notebooks/get-started/learn_beam_transforms_by_doing.ipynb">this colab notebook</a>.</p>
<h3 id="applying-transforms">4.1. Applying transforms</h3>
<p>To invoke a transform, you must <strong>apply</strong> it to the input <code>PCollection</code>. Each
transform in the Beam SDKs has a generic <code>apply</code> method <span class="language-py">(or pipe operator <code>|</code>)</span>.
diff --git a/website/generated-content/documentation/programming-guide/index.html b/website/generated-content/documentation/programming-guide/index.html
index a1a42e9c5e4..e534dc41b87 100644
--- a/website/generated-content/documentation/programming-guide/index.html
+++ b/website/generated-content/documentation/programming-guide/index.html
@@ -97,7 +97,9 @@ with a single `root` object and is passed to a Runner's `run` method.</span><div
</span><span class=c1></span><span class=nx>pipeline</span><span class=p>,</span> <span class=nx>scope</span> <span class=o>:=</span> <span class=nx>beam</span><span class=p>.</span><span class=nf>NewPipelineWithRoot</span><span class=p>()</span></code></pre></div></div></div><div class="language-typescript snippet"><div class="notebook-skip code-snippet"><a class=copy type=button data-bs-toggle=tooltip data-bs-placement=bottom title="Copy to clipboard"><img src=/images/copy-icon.svg></a [...]
<span class=c1>// Use root to build a pipeline.
</span><span class=c1></span><span class=p>});</span>
-</code></pre></div></div></div><h3 id=configuring-pipeline-options>2.1. Configuring pipeline options</h3><p>Use the pipeline options to configure different aspects of your pipeline, such
+</code></pre></div></div></div><p>For a more in-depth tutorial on creating basic pipelines
+in the Python SDK, please read and work through
+<a href=https://colab.sandbox.google.com/github/apache/beam/blob/master/examples/notebooks/get-started/learn_beam_basics_by_doing.ipynb>this colab notebook</a>.</p><h3 id=configuring-pipeline-options>2.1. Configuring pipeline options</h3><p>Use the pipeline options to configure different aspects of your pipeline, such
as the pipeline runner that will execute your pipeline and any runner-specific
configuration required by the chosen runner. Your pipeline options will
potentially include information such as your project ID or a location for
@@ -366,7 +368,9 @@ such as <a href=#pardo>ParDo</a> or <a href=#combine>Combine</a>. There are also
<a href=#composite-transforms>composite transforms</a> included in the SDKs, which
combine one or more of the core transforms in a useful processing pattern, such
as counting or combining elements in a collection. You can also define your own
-more complex composite transforms to fit your pipeline’s exact use case.</p><h3 id=applying-transforms>4.1. Applying transforms</h3><p>To invoke a transform, you must <strong>apply</strong> it to the input <code>PCollection</code>. Each
+more complex composite transforms to fit your pipeline’s exact use case.</p><p>For a more in-depth tutorial of applying various transforms
+in the Python SDK, please read and work through
+<a href=https://colab.sandbox.google.com/github/liferoad/beam/blob/learn-transforms/examples/notebooks/get-started/learn_beam_transforms_by_doing.ipynb>this colab notebook</a>.</p><h3 id=applying-transforms>4.1. Applying transforms</h3><p>To invoke a transform, you must <strong>apply</strong> it to the input <code>PCollection</code>. Each
transform in the Beam SDKs has a generic <code>apply</code> method <span class=language-py>(or pipe operator <code>|</code>)</span>.
Invoking multiple Beam transforms is similar to <em>method chaining</em>, but with one
slight difference: You apply the transform to the input <code>PCollection</code>, passing
diff --git a/website/generated-content/sitemap.xml b/website/generated-content/sitemap.xml
index a5c0acc5810..d88a29fa134 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>/case-studies/booking/</loc><lastmod>2023-05-09T08:33:59-07:00</lastmod></url><url><loc>/blog/beam-2.46.0/</loc><lastmod>2023-05-09T08:33:59-07:00</lastmod></url><url><loc>/categories/blog/</loc><lastmod>2023-05-09T08:33:59-07:00</lastmod></url><url><loc>/blog/</loc><lastmod>2023-05-09T08:33:59-07:00</lastmod></url><url><l [...]
\ 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>/case-studies/booking/</loc><lastmod>2023-05-09T15:38:14-04:00</lastmod></url><url><loc>/blog/beam-2.46.0/</loc><lastmod>2023-05-09T15:38:14-04:00</lastmod></url><url><loc>/categories/blog/</loc><lastmod>2023-05-09T15:38:14-04:00</lastmod></url><url><loc>/blog/</loc><lastmod>2023-05-09T15:38:14-04:00</lastmod></url><url><l [...]
\ No newline at end of file