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 3b654401558 Publishing website 2022/04/21 04:21:10 at commit 2f0aaea
3b654401558 is described below
commit 3b6544015589424e37ee05d3b209020ced04988f
Author: jenkins <[email protected]>
AuthorDate: Thu Apr 21 04:21:10 2022 +0000
Publishing website 2022/04/21 04:21:10 at commit 2f0aaea
---
website/generated-content/contribute/index.xml | 7 ++++---
website/generated-content/contribute/release-guide/index.html | 8 ++++----
website/generated-content/sitemap.xml | 2 +-
3 files changed, 9 insertions(+), 8 deletions(-)
diff --git a/website/generated-content/contribute/index.xml
b/website/generated-content/contribute/index.xml
index ff333dceb63..5a47278c767 100644
--- a/website/generated-content/contribute/index.xml
+++ b/website/generated-content/contribute/index.xml
@@ -1339,7 +1339,7 @@ A committer can manually trigger the <a
href="https://ci-beam.apache.org/job/
<p>This pull request is against the <code>apache/beam-site</code>
repo, on the <code>release-docs</code> branch (<a
href="https://github.com/apache/beam-site/pull/603";>example</a>).
It is created by <code>build_release_candidate.sh</code> (see
above).</p>
<p><strong>PR 2: apache/beam</strong></p>
-<p>This pull request is against the <code>apache/beam</code> repo, on
the <code>master</code> branch (<a
href="https://github.com/apache/beam/pull/15068";>example</a>).</p>
+<p>This pull request is against the <code>apache/beam</code> repo, on
the <code>master</code> branch (<a
href="https://github.com/apache/beam/pull/17378";>example</a>).</p>
<ul>
<li>Update <code>CHANGES.md</code> to update release date and remove
template.</li>
<li>Update release version in
<code>website/www/site/config.toml</code>.</li>
@@ -1348,6 +1348,8 @@ It is created by
<code>build_release_candidate.sh</code> (see above).</
<li>Download links will not work until the release is finalized.</li>
</ul>
</li>
+<li>Update links to prior releases to point to <a
href="https://archive.apache.org";>https://archive.apache.org</a> (see
+example PR).</li>
<li>Update <code>website/www/site/static/.htaccess</code> to redirect
to the new version.</li>
<li>Create the Blog post:</li>
</ul>
@@ -1811,8 +1813,7 @@ Ping <a href="mailto:[email protected]";>dev@</a>
for assistance if you n
<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&rsquo;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.
-The release manager should also make sure to update these links on the website
(<a href="https://github.com/apache/beam/pull/11727";>example</a>).</p>
+This should happen automatically: <a
href="https://lists.apache.org/thread.html/39c26c57c5125a7ca06c3c9315b4917b86cd0e4567b7174f4bc4d63b%40%3Cdev.beam.apache.org%3E";>dev@
thread</a> with context.</p>
<h4 id="mark-the-version-as-released-in-jira">Mark the version as released
in JIRA</h4>
<p>In JIRA, inside <a
href="https://issues.apache.org/jira/plugins/servlet/project-config/BEAM/versions";>version
management</a>, hover over the current release and a settings menu will
appear.
Click <code>Release</code>, and select today’s date.</p>
diff --git a/website/generated-content/contribute/release-guide/index.html
b/website/generated-content/contribute/release-guide/index.html
index 271a46ab5df..876578269e6 100644
--- a/website/generated-content/contribute/release-guide/index.html
+++ b/website/generated-content/contribute/release-guide/index.html
@@ -163,7 +163,8 @@ The final step of building the candidate is to propose
website pull requests tha
To avoid invalid redirects for the ‘current’ version, merge these
PRs in the order listed.
Once the PR is merged, the new contents will get picked up automatically and
served to the Beam website, usually within an hour.
A committer can manually trigger the <a
href=https://ci-beam.apache.org/job/beam_PostCommit_Website_Publish/>beam_PostCommit_Website_Publish</a>
task in Jenkins to avoid waiting.</p><p><strong>PR 1:
apache/beam-site</strong></p><p>This pull request is against the
<code>apache/beam-site</code> repo, on the <code>release-docs</code> branch (<a
href=https://github.com/apache/beam-site/pull/603>example</a>).
-It is created by <code>build_release_candidate.sh</code> (see
above).</p><p><strong>PR 2: apache/beam</strong></p><p>This pull request is
against the <code>apache/beam</code> repo, on the <code>master</code> branch
(<a
href=https://github.com/apache/beam/pull/15068>example</a>).</p><ul><li>Update
<code>CHANGES.md</code> to update release date and remove
template.</li><li>Update release version in
<code>website/www/site/config.toml</code>.</li><li>Add new release in
<code>website/www/site [...]
+It is created by <code>build_release_candidate.sh</code> (see
above).</p><p><strong>PR 2: apache/beam</strong></p><p>This pull request is
against the <code>apache/beam</code> repo, on the <code>master</code> branch
(<a
href=https://github.com/apache/beam/pull/17378>example</a>).</p><ul><li>Update
<code>CHANGES.md</code> to update release date and remove
template.</li><li>Update release version in
<code>website/www/site/config.toml</code>.</li><li>Add new release in
<code>website/www/site [...]
+example PR).</li><li>Update <code>website/www/site/static/.htaccess</code> to
redirect to the new version.</li><li>Create the Blog post:</li></ul><h4
id=blog-post>Blog post</h4><p>Use the template below to write a blog post for
the release.
See <a
href=https://github.com/apache/beam/commit/a32a75ed0657c122c6625aee1ace27994e7df195#diff-1e2b83a4f61dce8014a1989869b6d31eb3f80cb0d6dade42fb8df5d9407b4748>beam-2.31.0.md</a>
as an example.</p><ul><li>Copy the changes for the current release from
<code>CHANGES.md</code> to the blog post and edit as necessary.</li><li>Be sure
to add yourself to <a
href=https://github.com/apache/beam/blob/master/website/www/site/data/authors.yml>authors.yml</a>
if necessary.</li></ul><p><strong>Tip</s [...]
Make sure to clean it up, as there may be duplicate or incorrect user
names.</p><p><strong>NOTE</strong>: Make sure to include any breaking changes,
even to <code>@Experimental</code> features,
all major features and bug fixes, and all known
issues.</p><p><strong>Template:</strong></p><pre><code>We are happy to present
the new {$RELEASE_VERSION} release of Beam.
@@ -404,8 +405,7 @@ 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>./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:[email protected]>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.
-The release manager should also make sure to update these links on the website
(<a href=https://github.com/apache/beam/pull/11727>example</a>).</p><h4
id=mark-the-version-as-released-in-jira>Mark the version as released in
JIRA</h4><p>In JIRA, inside <a
href=https://issues.apache.org/jira/plugins/servlet/project-config/BEAM/versions>version
management</a>, hover over the current release and a settings menu will appear.
+This should happen automatically: <a
href=https://lists.apache.org/thread.html/39c26c57c5125a7ca06c3c9315b4917b86cd0e4567b7174f4bc4d63b%40%3Cdev.beam.apache.org%3E>dev@
thread</a> with context.</p><h4 id=mark-the-version-as-released-in-jira>Mark
the version as released in JIRA</h4><p>In JIRA, inside <a
href=https://issues.apache.org/jira/plugins/servlet/project-config/BEAM/versions>version
management</a>, hover over the current release and a settings menu will appear.
Click <code>Release</code>, and select today’s date.</p><h4
id=recordkeeping-with-asf>Recordkeeping with ASF</h4><p>Use <a
href=https://reporter.apache.org/addrelease.html?beam>reporter.apache.org</a>
to seed the information about the release into future project reports.</p><h3
id=checklist-to-proceed-to-the-next-step-3>Checklist to proceed to the next
step</h3><ul><li>Maven artifacts released and indexed in the <a
href=https://search.maven.org/#search%7Cga%7C1%7Cg%3A%22org.apache.beam%2 [...]
(Note: Not all committers have administrator access to JIRA.
If you end up getting permissions errors ask on the mailing list for
assistance.)</li><li>Release version is listed at
reporter.apache.org</li></ul><hr><h2 id=12-promote-the-release>12. Promote the
release</h2><p>Once the release has been finalized, the last step of the
process is to promote the release within the project and beyond.</p><h3
id=apache-mailing-lists>Apache mailing lists</h3><p>Announce on the dev@
mailing list that the release has been finished.</p><p>Announce on the relea
[...]
@@ -413,7 +413,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
2022/03/31</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:[email protected]?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
2022/04/20</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:[email protected]?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 aa381417b27..903c4c31ef9 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.38.0/</loc><lastmod>2022-04-20T15:48:18-07:00</lastmod></url><url><loc>/categories/blog/</loc><lastmod>2022-04-20T15:48:18-07:00</lastmod></url><url><loc>/blog/</loc><lastmod>2022-04-20T15:48:18-07:00</lastmod></url><url><loc>/categories/</loc><lastmod>2022-04-20T15:48:18-07:00</lastmod></url><url><loc>/blog/b
[...]
\ 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.38.0/</loc><lastmod>2022-04-20T15:48:18-07:00</lastmod></url><url><loc>/categories/blog/</loc><lastmod>2022-04-20T15:48:18-07:00</lastmod></url><url><loc>/blog/</loc><lastmod>2022-04-20T15:48:18-07:00</lastmod></url><url><loc>/categories/</loc><lastmod>2022-04-20T15:48:18-07:00</lastmod></url><url><loc>/blog/b
[...]
\ No newline at end of file
