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 655e5daaa33 Publishing website 2023/04/26 22:16:33 at commit 3440ae5
655e5daaa33 is described below
commit 655e5daaa33fd50d365dfbe6d736cde77205e1fc
Author: jenkins <bui...@apache.org>
AuthorDate: Wed Apr 26 22:16:34 2023 +0000
Publishing website 2023/04/26 22:16:33 at commit 3440ae5
---
website/generated-content/contribute/index.xml | 60 ++++------------------
.../contribute/release-guide/index.html | 18 +++----
website/generated-content/sitemap.xml | 2 +-
3 files changed, 16 insertions(+), 64 deletions(-)
diff --git a/website/generated-content/contribute/index.xml
b/website/generated-content/contribute/index.xml
index c807b0585e1..18a1f86ba0b 100644
--- a/website/generated-content/contribute/index.xml
+++ b/website/generated-content/contribute/index.xml
@@ -642,12 +642,6 @@ limitations under the License.
<li><a href="#use-cut_release_branchsh-to-cut-a-release-branch">Use
cut_release_branch.sh to cut a release branch</a></li>
</ul>
</li>
-<li><a href="#start-a-snapshot-build">Start a snapshot build</a>
-<ul>
-<li><a href="#run-start_snapshot_buildsh-to-trigger-build">Run
start_snapshot_build.sh to trigger build</a></li>
-<li><a href="#alternative-do-all-operations-manually">(Alternative) Do
all operations manually</a></li>
-</ul>
-</li>
</ul>
</li>
<li><a href="#6-verify-release-branch">6. Verify release branch</a>
@@ -951,63 +945,27 @@ The final state of the repository should match this
diagram:</p>
<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>
-<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>
-</li>
-</ul>
-<p><code>RELEASE_VERSION</code> and <code>NEXT_VERSION</code>
should be formatted like <code>{major}.{minor}.{patch}</code> (e.g.
<code>2.46.0</code>)</p>
-<pre><code># Cut a release branch
-./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><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.
+<p>This will all be accomplished by the <a
href="https://github.com/apache/beam/actions/workflows/cut_release_branch.yml";>cut_release_branch</a>
+workflow.</p>
+<p>After updating the master branch, the workflow will also 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>
+Once the release branch is cut, these SNAPSHOT versions are no longer found,
so builds will be broken until a new snapshot is available.
+The workflow starts the nightly snapshot by creating an empty PR against
apache:master (which will be linked to in the logs).</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/start_snapshot_build.sh";>start_snapshot_build.sh</a></p>
-</li>
-<li>
-<p><strong>Usage</strong></p>
-<pre><code>./beam/release/src/main/scripts/start_snapshot_build.sh
-</code></pre>
-</li>
-<li>
-<p><strong>The script will:</strong></p>
-<ol>
-<li>Ask for the url of your personal clone of Beam (e.g.
<code>https://github.com/&lt;user&gt;/beam</code>).</li>
-<li>Install <a href="https://github.com/github/hub";>hub</a> with your
agreement.</li>
-<li>Touch an empty txt file and commit changes into <code>${your remote
beam repo}/snapshot_build</code></li>
-<li>Use hub to create a PR against apache:master, which triggers a Jenkins
job to build snapshot.</li>
-</ol>
+<p><strong>Action:</strong> <a
href="https://github.com/apache/beam/actions/workflows/cut_release_branch.yml";>cut_release_branch</a>
(click <code>run workflow</code>)</p>
</li>
<li>
<p>Tasks you need to do manually to <strong>verify the SNAPSHOT
build</strong></p>
<ol>
<li>Check whether the Jenkins job gets triggered. If not, please comment
<code>Run Gradle Publish</code> into the generated PR.</li>
<li>After verifying build succeeded, you need to close PR manually.</li>
+<li>Manually update <code>CHANGES.md</code> on
<code>master</code> by adding a new section for the next release (<a
href="https://github.com/apache/beam/commit/96ab1fb3fe07acf7f7dc9d8c829ae36890d1535c";>example</a>).</li>
</ol>
</li>
</ul>
-<h4 id="alternative-do-all-operations-manually">(Alternative) Do all
operations manually</h4>
-<ul>
-<li>Find one PR against apache:master in beam.</li>
-<li>Comment <code>Run Gradle Publish</code> in this pull request to
trigger build.</li>
-<li>Verify that build succeeds.</li>
-</ul>
<hr>
<h2 id="6-verify-release-branch">6. Verify release branch</h2>
<p>After the release branch is cut you need to make sure it builds and has
no significant issues that would block the creation of the release candidate.
diff --git a/website/generated-content/contribute/release-guide/index.html
b/website/generated-content/contribute/release-guide/index.html
index 82c780a1a6a..35a7cbf5933 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.
@@ -85,18 +85,12 @@ Measurements are available on <a
href=http://metrics.beam.apache.org>metrics.bea
The role of the release manager is to file GitHub issues for each regression
with the milestone set to the to-be-released version.
The release manager oversees these just like any other issue marked with the
milestone 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=5-create-a-release-branch-in-apachebeam-repository>5. 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.
-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></li></ul><p><code
[...]
-./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><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.
+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 [...]
+workflow.</p><p>After updating the master branch, the workflow will also 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
[...]
-</code></pre></li><li><p><strong>The script will:</strong></p><ol><li>Ask for
the url of your personal clone of Beam (e.g.
<code>https://github.com/<user>/beam</code>).</li><li>Install <a
href=https://github.com/github/hub>hub</a> with your agreement.</li><li>Touch
an empty txt file and commit changes into <code>${your remote beam
repo}/snapshot_build</code></li><li>Use hub to create a PR against
apache:master, which triggers a Jenkins job to build
snapshot.</li></ol></li><li><p>Tasks [...]
+Once the release branch is cut, these SNAPSHOT versions are no longer found,
so builds will be broken until a new snapshot is available.
+The workflow starts the nightly snapshot by creating an empty PR against
apache:master (which will be linked to in the logs).</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>Action:</strong> <a
href=https://github.com/apache/beam/actions/workflows/cut_release_branch.yml>cut_release_branch</a>
(click <code>run workflow</code>)</p></li><li><p>Tasks you need to do manually
to <strong>verify the SNAPSHOT buil [...]
There are 2 ways to perform this verification, either running automation
script(recommended), or running all commands manually.</p><p>! Dataflow tests
will fail if Dataflow worker container is not created and published by this
time. (Should be done by Google)</p><h4
id=run-automation-script-verify_release_buildsh>Run automation script
(verify_release_build.sh)</h4><ul><li><p><strong>Script:</strong> <a
href=https://github.com/apache/beam/blob/master/release/src/main/scripts/verify_releas
[...]
See instruction <a
href=https://help.github.com/en/articles/creating-a-personal-access-token-for-the-command-line>here</a>.
It’ll be used by the script for accessing Github API.
diff --git a/website/generated-content/sitemap.xml
b/website/generated-content/sitemap.xml
index c245891297a..1b128d6b9c8 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-04-26T10:28:46-04:00</lastmod></url><url><loc>/blog/beam-2.46.0/</loc><lastmod>2023-04-26T10:28:46-04:00</lastmod></url><url><loc>/categories/blog/</loc><lastmod>2023-04-26T10:28:46-04:00</lastmod></url><url><loc>/blog/</loc><lastmod>2023-04-26T10:28:46-04: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-04-26T14:52:10-04:00</lastmod></url><url><loc>/blog/beam-2.46.0/</loc><lastmod>2023-04-26T14:52:10-04:00</lastmod></url><url><loc>/categories/blog/</loc><lastmod>2023-04-26T14:52:10-04:00</lastmod></url><url><loc>/blog/</loc><lastmod>2023-04-26T14:52:10-04:00</lastmod></url><url><l
[...]
\ No newline at end of file
