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 5ef72d8 Publishing website 2021/03/18 00:01:26 at commit 8a91ca3
5ef72d8 is described below
commit 5ef72d84bc90d765d0042898dda3006b67ef8fa5
Author: jenkins <bui...@apache.org>
AuthorDate: Thu Mar 18 00:01:27 2021 +0000
Publishing website 2021/03/18 00:01:26 at commit 8a91ca3
---
website/generated-content/contribute/index.xml | 95 +++------------------
.../contribute/release-guide/index.html | 37 +-------
website/generated-content/get-started/index.xml | 17 +++-
.../get-started/tour-of-beam/index.html | 10 ++-
.../images/cut-release-branch.png | Bin 0 -> 34625 bytes
website/generated-content/sitemap.xml | 2 +-
6 files changed, 40 insertions(+), 121 deletions(-)
diff --git a/website/generated-content/contribute/index.xml
b/website/generated-content/contribute/index.xml
index 7e3b3e6..f48b7cf 100644
--- a/website/generated-content/contribute/index.xml
+++ b/website/generated-content/contribute/index.xml
@@ -303,7 +303,6 @@ limitations under the License.
<li>
<ul>
<li><a href="#use-cut_release_branchsh-to-cut-a-release-branch">Use
cut_release_branch.sh to cut a release branch</a></li>
-<li><a href="#alternative-run-all-steps-manually">(Alternative) Run all
steps manually</a></li>
</ul>
</li>
<li><a href="#start-a-snapshot-build">Start a snapshot build</a>
@@ -599,9 +598,18 @@ The release manager oversees these just like any other
JIRA issue marked with th
<h2 id="4-create-a-release-branch-in-apachebeam-repository">4. Create a
release branch in apache/beam repository</h2>
<p>Attention: Only committer has permission to create release branch in
apache/beam.</p>
<p>Release candidates are built from a release branch.
-As a final step in preparation for the release, you should create the release
branch, push it to the Apache code repository, and update version information
on the original branch.</p>
-<p>There are 2 ways to cut a release branch: either running automation
script(recommended), or running all commands manually.</p>
-<p>After following one of these processes you should manually update
<code>CHANGES.md</code> on <code>master</code> by adding a new
section for the next release.</p>
+As a final step in preparation for the release, you should create the release
branch, push it to the Apache code repository, and update version information
on the original branch.
+The final state of the repository should match this diagram:</p>
+<img src="/images/cut-release-branch.png" alt="Increment minor version on
master branch and set Dataflow container version on release branch"
width="100%">
+<p>The key points to know:</p>
+<ul>
+<li>The <code>master</code> branch has the SNAPSHOT/dev version
incremented.</li>
+<li>The release branch has the SNAPSHOT/dev version to be released.</li>
+<li>The Dataflow container image should be modified to the version to be
released.</li>
+</ul>
+<p>This will all be accomplished by the <a
href="https://github.com/apache/beam/blob/master/release/src/main/scripts/cut_release_branch.sh";>cut_release_branch.sh</a>
+script.</p>
+<p>After cutting the branch, you should manually update
<code>CHANGES.md</code> on <code>master</code> by adding a new
section for the next release.</p>
<h4 id="use-cut_release_branchsh-to-cut-a-release-branch">Use
cut_release_branch.sh to cut a release branch</h4>
<ul>
<li>
@@ -616,85 +624,6 @@ As a final step in preparation for the release, you should
create the release br
# Show help page
./beam/release/src/main/scripts/cut_release_branch.sh -h
</code></pre></li>
-<li>
-<p><strong>The script will:</strong></p>
-<ol>
-<li>
-<p>Create release-${RELEASE_VERSION} branch locally.</p>
-</li>
-<li>
-<p>Change and commit dev versoin number in master branch:</p>
-<p><a
href="https://github.com/apache/beam/blob/e8abafe360e126818fe80ae0f6075e71f0fc227d/buildSrc/src/main/groovy/org/apache/beam/gradle/BeamModulePlugin.groovy#L209";>BeamModulePlugin.groovy</a>,
-<a
href="https://github.com/apache/beam/blob/e8abafe360e126818fe80ae0f6075e71f0fc227d/gradle.properties#L25";>gradle.properties</a>,
-<a
href="https://github.com/apache/beam/blob/e8abafe360e126818fe80ae0f6075e71f0fc227d/sdks/python/apache_beam/version.py#L21";>version.py</a></p>
-</li>
-<li>
-<p>Change and commit version number in release branch:</p>
-<p><a
href="https://github.com/apache/beam/blob/release-2.6.0/sdks/python/apache_beam/version.py#L21";>version.py</a>,
-<a
href="https://github.com/apache/beam/blob/release-2.6.0/runners/google-cloud-dataflow-java/build.gradle#L39";>build.gradle</a>,
-<a
href="https://github.com/apache/beam/blob/release-2.16.0/gradle.properties#L27";>gradle.properties</a></p>
-</li>
-</ol>
-</li>
-</ul>
-<h4 id="alternative-run-all-steps-manually">(Alternative) Run all steps
manually</h4>
-<ul>
-<li>
-<p><strong>Checkout working branch</strong></p>
-<p>Check out the version of the codebase from which you start the release.
-For a new minor or major release, this may be <code>HEAD</code> of the
<code>master</code> branch.
-To build a hotfix/incremental release, instead of the
<code>master</code> branch, use the release tag of the release being
patched.
-(Please make sure your cloned repository is up-to-date before starting.)</p>
-<pre><code>git checkout &lt;master branch OR release tag&gt;
-</code></pre>
-<p><strong>NOTE</strong>: If you are doing an incremental/hotfix
release (e.g. 2.5.1), please check out the previous release tag, rather than
the master branch.</p>
-</li>
-<li>
-<p><strong>Set up environment variables</strong></p>
-<p>Set up a few environment variables to simplify Maven commands that
follow.
-(We use <code>bash</code> Unix syntax in this guide.)</p>
-<pre><code>RELEASE=2.5.0
-NEXT_VERSION_IN_BASE_BRANCH=2.6.0
-BRANCH=release-${RELEASE}
-</code></pre>
-<p>Version represents the release currently underway, while next version
specifies the anticipated next version to be released from that branch.
-Normally, 1.2.0 is followed by 1.3.0, while 1.2.3 is followed by 1.2.4.</p>
-<p><strong>NOTE</strong>: Only if you are doing an incremental/hotfix
release (e.g. 2.5.1), please check out the previous release tag, before running
the following instructions:</p>
-<pre><code>BASE_RELEASE=2.5.0
-RELEASE=2.5.1
-NEXT_VERSION_IN_BASE_BRANCH=2.6.0
-git checkout tags/${BASE_RELEASE}
-</code></pre>
-</li>
-<li>
-<p><strong>Create release branch locally</strong></p>
-<pre><code>git branch ${BRANCH}
-</code></pre>
-</li>
-<li>
-<p><strong>Update version files in the master branch</strong></p>
-<pre><code># Now change the version in existing gradle files, and Python
files
-sed -i -e
&quot;s/'${RELEASE}'/'${NEXT_VERSION_IN_BASE_BRANCH}'/g&quot;
build_rules.gradle
-sed -i -e &quot;s/${RELEASE}/${NEXT_VERSION_IN_BASE_BRANCH}/g&quot;
gradle.properties
-sed -i -e &quot;s/${RELEASE}/${NEXT_VERSION_IN_BASE_BRANCH}/g&quot;
sdks/python/apache_beam/version.py
-# Save changes in master branch
-git add gradle.properties build_rules.gradle sdks/python/apache_beam/version.py
-git commit -m &quot;Moving to ${NEXT_VERSION_IN_BASE_BRANCH}-SNAPSHOT on
master branch.&quot;
-</code></pre>
-</li>
-<li>
-<p><strong>Check out the release branch</strong></p>
-<pre><code>git checkout ${BRANCH}
-</code></pre>
-</li>
-<li>
-<p><strong>Update version files in release branch</strong></p>
-<pre><code>DEV=${RELEASE}.dev
-sed -i -e &quot;s/${DEV}/${RELEASE}/g&quot;
sdks/python/apache_beam/version.py
-sed -i -e &quot;s/${DEV}/${RELEASE}/g&quot; gradle.properties
-sed -i -e &quot;s/'beam-master-.*'/'beam-${RELEASE}'/g&quot;
runners/google-cloud-dataflow-java/build.gradle
-</code></pre>
-</li>
</ul>
<h3 id="start-a-snapshot-build">Start a snapshot build</h3>
<p>Start a build of <a
href="https://ci-beam.apache.org/job/beam_Release_NightlySnapshot/";>the nightly
snapshot</a> against master branch.
diff --git a/website/generated-content/contribute/release-guide/index.html
b/website/generated-content/contribute/release-guide/index.html
index 63dad25..36f9eb0 100644
--- a/website/generated-content/contribute/release-guide/index.html
+++ b/website/generated-content/contribute/release-guide/index.html
@@ -18,7 +18,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</a></li><li><a
href=/contribute/get-help/>Get Help</a></li><li><a href=/contrib [...]
+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</a></li><li><a
href=/contribute/get-help/>Get Help</a></li><li><a href=/contrib [...]
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.
@@ -79,44 +79,15 @@ If you are not a PMC, please ask for help in dev@ mailing
list.</p><ol><li>In JI
Measurements are available on <a
href=http://metrics.beam.apache.org>metrics.beam.apache.org</a>.</p><p>All
Runners which publish data should be checked for the following, in both
<em>batch</em> and <em>streaming</em> mode:</p><ul><li><a
href=http://metrics.beam.apache.org/d/MOi-kf3Zk/pardo-load-tests>ParDo</a> and
<a href=http://metrics.beam.apache.org/d/UYZ-oJ3Zk/gbk-load-test>GBK</a>:
Runtime, latency, checkpoint duration</li><li><a
href=http://metrics.beam.apache.org/d/ahuaA_zGz/nexm [...]
The role of the release manager is to file JIRA issues for each regression
with the ‘Fix Version’ set to the to-be-released version.
The release manager oversees these just like any other JIRA issue marked with
the ‘Fix Version’ of the release.</p><p>The mailing list should be
informed to allow fixing the regressions in the course of the release.</p><h2
id=4-create-a-release-branch-in-apachebeam-repository>4. Create a release
branch in apache/beam repository</h2><p>Attention: Only committer has
permission to create release branch in apache/beam.</p><p>Release candidates
are built from a release branch.
-As a final step in preparation for the release, you should create the release
branch, push it to the Apache code repository, and update version information
on the original branch.</p><p>There are 2 ways to cut a release branch: either
running automation script(recommended), or running all commands
manually.</p><p>After following one of these processes you should manually
update <code>CHANGES.md</code> on <code>master</code> by adding a new section
for the next release.</p><h4 id=use-cut_ [...]
+As a final step in preparation for the release, you should create the release
branch, push it to the Apache code repository, and update version information
on the original branch.
+The final state of the repository should match this diagram:</p><img
src=/images/cut-release-branch.png alt="Increment minor version on master
branch and set Dataflow container version on release branch" width=100%><p>The
key points to know:</p><ul><li>The <code>master</code> branch has the
SNAPSHOT/dev version incremented.</li><li>The release branch has the
SNAPSHOT/dev version to be released.</li><li>The Dataflow container image
should be modified to the version to be released.</li></u [...]
+script.</p><p>After cutting the branch, you should manually update
<code>CHANGES.md</code> on <code>master</code> by adding a new section for the
next release.</p><h4 id=use-cut_release_branchsh-to-cut-a-release-branch>Use
cut_release_branch.sh to cut a release
branch</h4><ul><li><p><strong>Script:</strong> <a
href=https://github.com/apache/beam/blob/master/release/src/main/scripts/cut_release_branch.sh>cut_release_branch.sh</a></p></li><li><p><strong>Usage</strong></p><pre><code>#
Cut a [...]
./beam/release/src/main/scripts/cut_release_branch.sh \
--release=${RELEASE_VERSION} \
--next_release=${NEXT_VERSION}
# Show help page
./beam/release/src/main/scripts/cut_release_branch.sh -h
-</code></pre></li><li><p><strong>The script
will:</strong></p><ol><li><p>Create release-${RELEASE_VERSION} branch
locally.</p></li><li><p>Change and commit dev versoin number in master
branch:</p><p><a
href=https://github.com/apache/beam/blob/e8abafe360e126818fe80ae0f6075e71f0fc227d/buildSrc/src/main/groovy/org/apache/beam/gradle/BeamModulePlugin.groovy#L209>BeamModulePlugin.groovy</a>,
-<a
href=https://github.com/apache/beam/blob/e8abafe360e126818fe80ae0f6075e71f0fc227d/gradle.properties#L25>gradle.properties</a>,
-<a
href=https://github.com/apache/beam/blob/e8abafe360e126818fe80ae0f6075e71f0fc227d/sdks/python/apache_beam/version.py#L21>version.py</a></p></li><li><p>Change
and commit version number in release branch:</p><p><a
href=https://github.com/apache/beam/blob/release-2.6.0/sdks/python/apache_beam/version.py#L21>version.py</a>,
-<a
href=https://github.com/apache/beam/blob/release-2.6.0/runners/google-cloud-dataflow-java/build.gradle#L39>build.gradle</a>,
-<a
href=https://github.com/apache/beam/blob/release-2.16.0/gradle.properties#L27>gradle.properties</a></p></li></ol></li></ul><h4
id=alternative-run-all-steps-manually>(Alternative) Run all steps
manually</h4><ul><li><p><strong>Checkout working branch</strong></p><p>Check
out the version of the codebase from which you start the release.
-For a new minor or major release, this may be <code>HEAD</code> of the
<code>master</code> branch.
-To build a hotfix/incremental release, instead of the <code>master</code>
branch, use the release tag of the release being patched.
-(Please make sure your cloned repository is up-to-date before
starting.)</p><pre><code>git checkout <master branch OR release tag>
-</code></pre><p><strong>NOTE</strong>: If you are doing an incremental/hotfix
release (e.g. 2.5.1), please check out the previous release tag, rather than
the master branch.</p></li><li><p><strong>Set up environment
variables</strong></p><p>Set up a few environment variables to simplify Maven
commands that follow.
-(We use <code>bash</code> Unix syntax in this
guide.)</p><pre><code>RELEASE=2.5.0
-NEXT_VERSION_IN_BASE_BRANCH=2.6.0
-BRANCH=release-${RELEASE}
-</code></pre><p>Version represents the release currently underway, while next
version specifies the anticipated next version to be released from that branch.
-Normally, 1.2.0 is followed by 1.3.0, while 1.2.3 is followed by
1.2.4.</p><p><strong>NOTE</strong>: Only if you are doing an incremental/hotfix
release (e.g. 2.5.1), please check out the previous release tag, before running
the following instructions:</p><pre><code>BASE_RELEASE=2.5.0
-RELEASE=2.5.1
-NEXT_VERSION_IN_BASE_BRANCH=2.6.0
-git checkout tags/${BASE_RELEASE}
-</code></pre></li><li><p><strong>Create release branch
locally</strong></p><pre><code>git branch ${BRANCH}
-</code></pre></li><li><p><strong>Update version files in the master
branch</strong></p><pre><code># Now change the version in existing gradle
files, and Python files
-sed -i -e "s/'${RELEASE}'/'${NEXT_VERSION_IN_BASE_BRANCH}'/g"
build_rules.gradle
-sed -i -e "s/${RELEASE}/${NEXT_VERSION_IN_BASE_BRANCH}/g"
gradle.properties
-sed -i -e "s/${RELEASE}/${NEXT_VERSION_IN_BASE_BRANCH}/g"
sdks/python/apache_beam/version.py
-
-# Save changes in master branch
-git add gradle.properties build_rules.gradle sdks/python/apache_beam/version.py
-git commit -m "Moving to ${NEXT_VERSION_IN_BASE_BRANCH}-SNAPSHOT on
master branch."
-</code></pre></li><li><p><strong>Check out the release
branch</strong></p><pre><code>git checkout ${BRANCH}
-</code></pre></li><li><p><strong>Update version files in release
branch</strong></p><pre><code>DEV=${RELEASE}.dev
-sed -i -e "s/${DEV}/${RELEASE}/g" sdks/python/apache_beam/version.py
-sed -i -e "s/${DEV}/${RELEASE}/g" gradle.properties
-sed -i -e "s/'beam-master-.*'/'beam-${RELEASE}'/g"
runners/google-cloud-dataflow-java/build.gradle
</code></pre></li></ul><h3 id=start-a-snapshot-build>Start a snapshot
build</h3><p>Start a build of <a
href=https://ci-beam.apache.org/job/beam_Release_NightlySnapshot/>the nightly
snapshot</a> against master branch.
Some processes, including our archetype tests, rely on having a live SNAPSHOT
of the current version from the <code>master</code> branch.
Once the release branch is cut, these SNAPSHOT versions are no longer found,
so builds will be broken until a new snapshot is available.</p><p>There are 2
ways to trigger a nightly build, either using automation script(recommended),
or perform all operations manually.</p><h4
id=run-start_snapshot_buildsh-to-trigger-build>Run start_snapshot_build.sh to
trigger build</h4><ul><li><p><strong>Script:</strong> <a
href=https://github.com/apache/beam/blob/master/release/src/main/scripts/start_sn
[...]
diff --git a/website/generated-content/get-started/index.xml
b/website/generated-content/get-started/index.xml
index 59b8c88..adfb8d0 100644
--- a/website/generated-content/get-started/index.xml
+++ b/website/generated-content/get-started/index.xml
@@ -4545,7 +4545,8 @@ You don&rsquo;t need to install anything or modify
your computer in any way
<p>You can also <a href="/get-started/try-apache-beam">try an Apache
Beam pipeline</a> using the Java, Python, and Go SDKs.</p>
<h2 id="get-started">Get started</h2>
<h3 id="learn-the-basics">Learn the basics</h3>
-<p>In this notebook we go through the basics of what is Apache Beam and how
to get started.</p>
+<p>In this notebook we go through the basics of what is Apache Beam and how
to get started.
+We learn what is a data pipeline, a PCollection, a PTransform, as well as some
basic transforms like <code>Map</code>, <code>FlatMap</code>,
<code>Filter</code>, <code>Combine</code>, and
<code>GroupByKey</code>.</p>
<table align="left">
<td>
<a class="button" target="_blank"
href="https://colab.research.google.com/github/apache/beam/blob/master/examples/notebooks/tour-of-beam/getting-started.ipynb";>
@@ -4556,6 +4557,20 @@ Run in Colab
</td>
</table>
<p><br><br><br><br></p>
+<h3 id="reading-and-writing-data">Reading and writing data</h3>
+<p>In this notebook we go through some examples on how to read and write
data to and from different data formats.
+We introduce the built-in <code>ReadFromText</code> and
<code>WriteToText</code> transforms.
+We also see how we can read from CSV files, read from a SQLite database, write
fixed-sized batches of elements, and write windows of elements.</p>
+<table align="left">
+<td>
+<a class="button" target="_blank"
href="https://colab.research.google.com/github/apache/beam/blob/master/examples/notebooks/tour-of-beam/reading-and-writing-data.ipynb";>
+<img alt="Run in Colab" width="32px" height="32px"
+src="https://github.com/googlecolab/open_in_colab/raw/master/images/icon32.png";
/>
+Run in Colab
+</a>
+</td>
+</table>
+<p><br><br><br><br></p>
<h2 id="transforms">Transforms</h2>
<p>Check the <a href="/documentation/transforms/python/overview/">Python
transform catalog</a>
for a complete list of the available transforms.</p>
diff --git a/website/generated-content/get-started/tour-of-beam/index.html
b/website/generated-content/get-started/tour-of-beam/index.html
index 5c3cd77..4a3ce09 100644
--- a/website/generated-content/get-started/tour-of-beam/index.html
+++ b/website/generated-content/get-started/tour-of-beam/index.html
@@ -18,17 +18,21 @@
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>Get
started</span></li><li><a href=/get-started/beam-overview/>Beam
Overview</a></li><li><a href=/get-started/tour-of-beam/>Tour of
Beam</a></li><li><s [...]
+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>Get
started</span></li><li><a href=/get-started/beam-overview/>Beam
Overview</a></li><li><a href=/get-started/tour-of-beam/>Tour of
Beam</a></li><li><s [...]
<a href=https://colab.research.google.com>Colab</a>.
The notebooks allow you to interactively play with the code and see how your
changes affect the pipeline.
-You don’t need to install anything or modify your computer in any way to
use these notebooks.</p><p>You can also <a
href=/get-started/try-apache-beam>try an Apache Beam pipeline</a> using the
Java, Python, and Go SDKs.</p><h2 id=get-started>Get started</h2><h3
id=learn-the-basics>Learn the basics</h3><p>In this notebook we go through the
basics of what is Apache Beam and how to get started.</p><table
align=left><td><a class=button target=_blank
href=https://colab.research.google.co [...]
+You don’t need to install anything or modify your computer in any way to
use these notebooks.</p><p>You can also <a
href=/get-started/try-apache-beam>try an Apache Beam pipeline</a> using the
Java, Python, and Go SDKs.</p><h2 id=get-started>Get started</h2><h3
id=learn-the-basics>Learn the basics</h3><p>In this notebook we go through the
basics of what is Apache Beam and how to get started.
+We learn what is a data pipeline, a PCollection, a PTransform, as well as some
basic transforms like <code>Map</code>, <code>FlatMap</code>,
<code>Filter</code>, <code>Combine</code>, and
<code>GroupByKey</code>.</p><table align=left><td><a class=button target=_blank
href=https://colab.research.google.com/github/apache/beam/blob/master/examples/notebooks/tour-of-beam/getting-started.ipynb><img
alt="Run in Colab" width=32px height=32px
src=https://github.com/googlecolab/open_in_colab/raw/ [...]
+Run in Colab</a></td></table><p><br><br><br><br></p><h3
id=reading-and-writing-data>Reading and writing data</h3><p>In this notebook we
go through some examples on how to read and write data to and from different
data formats.
+We introduce the built-in <code>ReadFromText</code> and
<code>WriteToText</code> transforms.
+We also see how we can read from CSV files, read from a SQLite database, write
fixed-sized batches of elements, and write windows of elements.</p><table
align=left><td><a class=button target=_blank
href=https://colab.research.google.com/github/apache/beam/blob/master/examples/notebooks/tour-of-beam/reading-and-writing-data.ipynb><img
alt="Run in Colab" width=32px height=32px
src=https://github.com/googlecolab/open_in_colab/raw/master/images/icon32.png>
Run in Colab</a></td></table><p><br><br><br><br></p><h2
id=transforms>Transforms</h2><p>Check the <a
href=/documentation/transforms/python/overview/>Python transform catalog</a>
for a complete list of the available transforms.</p><h3
id=element-wise-transforms>Element-wise transforms</h3><h4
id=map>Map</h4><p>Applies a simple one-to-one mapping function over each
element in the collection.</p><table align=left><td><a class=button
target=_blank
href=https://colab.research.google.com/github/apache/beam/blob/master/examples/notebooks/documentation/transforms/python/elementwise/map-py.ipynb><img
alt="Run in Colab" width=32px height=32px src=https://github.com/google [...]
Run in Colab</a></td></table><p><br><br><br><br></p><h4
id=flatmap>FlatMap</h4><p>Applies a simple one-to-many mapping function over
each element in the collection. The many elements are flattened into the
resulting collection.</p><table align=left><td><a class=button target=_blank
href=https://colab.research.google.com/github/apache/beam/blob/master/examples/notebooks/documentation/transforms/python/elementwise/flatmap-py.ipynb><img
alt="Run in Colab" width=32px height=32px src=https:// [...]
Run in Colab</a></td></table><p><br><br><br><br></p><h4
id=filter>Filter</h4><p>Given a predicate, filter out all elements that don’t
satisfy that predicate.</p><table align=left><td><a class=button target=_blank
href=https://colab.research.google.com/github/apache/beam/blob/master/examples/notebooks/documentation/transforms/python/elementwise/filter-py.ipynb><img
alt="Run in Colab" width=32px height=32px
src=https://github.com/googlecolab/open_in_colab/raw/master/images/icon32.png>
Run in Colab</a></td></table><p><br><br><br><br></p><h4
id=partition>Partition</h4><p>Separates elements in a collection into multiple
output collections.</p><table align=left><td><a class=button target=_blank
href=https://colab.research.google.com/github/apache/beam/blob/master/examples/notebooks/documentation/transforms/python/elementwise/partition-py.ipynb><img
alt="Run in Colab" width=32px height=32px
src=https://github.com/googlecolab/open_in_colab/raw/master/images/icon32.png>
Run in Colab</a></td></table><p><br><br><br><br></p><h4
id=pardo>ParDo</h4><p>A transform for generic parallel processing. It’s
recommended to use <code>Map</code>, <code>FlatMap</code>, <code>Filter</code>
or other more specific transforms when possible.</p><table align=left><td><a
class=button target=_blank
href=https://colab.research.google.com/github/apache/beam/blob/master/examples/notebooks/documentation/transforms/python/elementwise/pardo-py.ipynb><img
alt="Run in Colab" wid [...]
-Run in Colab</a></td></table><p><br><br><br><br></p><div class=feedback><p
class=update>Last updated on 2021/02/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=foote [...]
+Run in Colab</a></td></table><p><br><br><br><br></p><div class=feedback><p
class=update>Last updated on 2021/03/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=foote [...]
<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/images/cut-release-branch.png
b/website/generated-content/images/cut-release-branch.png
new file mode 100644
index 0000000..2d29eca
Binary files /dev/null and
b/website/generated-content/images/cut-release-branch.png differ
diff --git a/website/generated-content/sitemap.xml
b/website/generated-content/sitemap.xml
index 57642e0..4bda51a 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.28.0/</loc><lastmod>2021-02-22T11:40:20-08:00</lastmod></url><url><loc>/categories/blog/</loc><lastmod>2021-02-22T11:40:20-08:00</lastmod></url><url><loc>/blog/</loc><lastmod>2021-02-22T11:40:20-08:00</lastmod></url><url><loc>/categories/</loc><lastmod>2021-03-16T13:53:01+05:00</lastmod></url><url><loc>/blog/k
[...]
\ 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.28.0/</loc><lastmod>2021-02-22T11:40:20-08:00</lastmod></url><url><loc>/categories/blog/</loc><lastmod>2021-02-22T11:40:20-08:00</lastmod></url><url><loc>/blog/</loc><lastmod>2021-02-22T11:40:20-08:00</lastmod></url><url><loc>/categories/</loc><lastmod>2021-03-16T13:53:01+05:00</lastmod></url><url><loc>/blog/k
[...]
\ No newline at end of file
![https://github.com/googlecolab/open_in_colab/raw/master/images/icon32.png"](https://github.com/googlecolab/open_in_colab/raw/master/images/icon32.png"){kind=link}
