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 2edddcc995d Publishing website 2023/02/16 22:16:01 at commit 4e6d751
2edddcc995d is described below

commit 2edddcc995de0b4d3e4ea656ebe495286d321925
Author: jenkins <bui...@apache.org>
AuthorDate: Thu Feb 16 22:16:01 2023 +0000

    Publishing website 2023/02/16 22:16:01 at commit 4e6d751
---
 website/generated-content/contribute/index.xml                | 6 +++---
 website/generated-content/contribute/release-guide/index.html | 8 ++++----
 website/generated-content/sitemap.xml                         | 2 +-
 3 files changed, 8 insertions(+), 8 deletions(-)

diff --git a/website/generated-content/contribute/index.xml 
b/website/generated-content/contribute/index.xml
index 03774d92149..f39c598c398 100644
--- a/website/generated-content/contribute/index.xml
+++ b/website/generated-content/contribute/index.xml
@@ -711,10 +711,10 @@ limitations under the License.
 &lt;li>&lt;a href="#merge-website-pull-requests">Merge Website pull 
requests&lt;/a>&lt;/li>
 &lt;li>&lt;a href="#git-tag">Git tag&lt;/a>&lt;/li>
 &lt;li>&lt;a href="#publish-release-to-github">Publish release to 
Github&lt;/a>&lt;/li>
+&lt;li>&lt;a href="#mark-the-version-as-released-in-github">Mark the version 
as released in GitHub&lt;/a>&lt;/li>
 &lt;li>&lt;a href="#pmc-only-finalization">PMC-Only Finalization&lt;/a>
 &lt;ul>
 &lt;li>&lt;a href="#deploy-source-release-to-distapacheorg">Deploy source 
release to dist.apache.org&lt;/a>&lt;/li>
-&lt;li>&lt;a href="#mark-the-version-as-released-in-github">Mark the version 
as released in GitHub&lt;/a>&lt;/li>
 &lt;li>&lt;a href="#recordkeeping-with-asf">Recordkeeping with 
ASF&lt;/a>&lt;/li>
 &lt;/ul>
 &lt;/li>
@@ -1824,6 +1824,8 @@ git push https://github.com/apache/beam 
&amp;quot;$VERSION_TAG&amp;quot;
 
&lt;pre>&lt;code>./beam/release/src/main/scripts/publish_github_release_notes.sh
 &lt;/code>&lt;/pre>&lt;p>Note this script reads the release notes from the 
blog post, so you should make sure to run this from master &lt;em>after&lt;/em> 
merging the blog post PR.&lt;/p>
 &lt;p>After running the script, the release notes should be visible on 
Github&amp;rsquo;s &lt;a 
href="https://github.com/apache/beam/releases";>Releases&lt;/a> page.&lt;/p>
+&lt;h3 id="mark-the-version-as-released-in-github">Mark the version as 
released in GitHub&lt;/h3>
+&lt;p>In GitHub, in the &lt;a 
href="https://github.com/apache/beam/milestones";>milestone page&lt;/a>, click 
close on the current release.&lt;/p>
 &lt;h3 id="pmc-only-finalization">PMC-Only Finalization&lt;/h3>
 &lt;p>There are a few release finalization tasks that only PMC members have 
permissions to do.
 Ping &lt;a href="mailto:d...@beam.apache.org";>dev@&lt;/a> for assistance if 
you need it.&lt;/p>
@@ -1831,8 +1833,6 @@ Ping &lt;a href="mailto:d...@beam.apache.org";>dev@&lt;/a> 
for assistance if you n
 &lt;p>Copy the source release from the &lt;code>dev&lt;/code> repository to 
the &lt;code>release&lt;/code> repository at &lt;code>dist.apache.org&lt;/code> 
using Subversion.&lt;/p>
 &lt;p>Make sure the last release&amp;rsquo;s artifacts have been copied from 
&lt;code>dist.apache.org&lt;/code> to &lt;code>archive.apache.org&lt;/code>.
 This should happen automatically: &lt;a 
href="https://lists.apache.org/thread.html/39c26c57c5125a7ca06c3c9315b4917b86cd0e4567b7174f4bc4d63b%40%3Cdev.beam.apache.org%3E";>dev@
 thread&lt;/a> with context.&lt;/p>
-&lt;h4 id="mark-the-version-as-released-in-github">Mark the version as 
released in GitHub&lt;/h4>
-&lt;p>In GitHub, in the &lt;a 
href="https://github.com/apache/beam/milestones";>milestone page&lt;/a>, click 
close on the current release.&lt;/p>
 &lt;h4 id="recordkeeping-with-asf">Recordkeeping with ASF&lt;/h4>
 &lt;p>Use &lt;a 
href="https://reporter.apache.org/addrelease.html?beam";>reporter.apache.org&lt;/a>
 to seed the information about the release into future project reports.&lt;/p>
 &lt;h3 id="checklist-to-proceed-to-the-next-step-3">Checklist to proceed to 
the next step&lt;/h3>
diff --git a/website/generated-content/contribute/release-guide/index.html 
b/website/generated-content/contribute/release-guide/index.html
index 596f25c24c6..3882aab0e79 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.
@@ -425,14 +425,14 @@ git push https://github.com/apache/beam 
&quot;sdks/$VERSION_TAG&quot;
 git tag -s &quot;$VERSION_TAG&quot; &quot;$RC_TAG&quot;
 git push https://github.com/apache/beam &quot;$VERSION_TAG&quot;
 </code></pre><p>After pushing the tag, the tag should be visible on 
Github&rsquo;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&rsquo;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.
+</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&rsquo;s <a href=https://github.com/apache/beam/releases>Releases</a> 
page.</p><h3 id=mark-the-version-as-released-in-github>Mark the version as 
released in GitHub</h3><p>In GitHub, in the <a 
href=https://github.com/apache/beam/milestones>milestone  [...]
 Ping <a href=mailto:d...@beam.apache.org>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&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.</p><h4 id=mark-the-version-as-released-in-github>Mark 
the version as released in GitHub</h4><p>In GitHub, in the <a 
href=https://github.com/apache/beam/milestones>milestone page</a>, click close 
on the current release.</p><h4 id=recordkeeping-with-asf>Recordkeeping with 
ASF</h4><p>Use <a href=http [...]
+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=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 n [...]
 <strong>NOTE</strong>: This can only be done from <code>@apache.org</code> 
email address. This email has to be in plain text (no HTML tags).</p><h3 
id=social-media>Social media</h3><p>Tweet, post on Facebook, LinkedIn, and 
other platforms.
 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/12/21</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=footer__cols><div class="footer__cols__col 
foo [...]
+Thanks!</p><div class=feedback><p class=update>Last updated on 
2023/02/16</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=footer__cols><div class="footer__cols__col 
foo [...]
 <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/sitemap.xml 
b/website/generated-content/sitemap.xml
index fad58ab9325..2a14d9dfb4b 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.45.0/</loc><lastmod>2023-02-15T16:50:59-05:00</lastmod></url><url><loc>/categories/blog/</loc><lastmod>2023-02-15T16:50:59-05:00</lastmod></url><url><loc>/blog/</loc><lastmod>2023-02-15T16:50:59-05:00</lastmod></url><url><loc>/categories/</loc><lastmod>2023-02-15T16:50:59-05: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.45.0/</loc><lastmod>2023-02-15T16:50:59-05:00</lastmod></url><url><loc>/categories/blog/</loc><lastmod>2023-02-15T16:50:59-05:00</lastmod></url><url><loc>/blog/</loc><lastmod>2023-02-15T16:50:59-05:00</lastmod></url><url><loc>/categories/</loc><lastmod>2023-02-15T16:50:59-05:00</lastmod></url><url><loc>/catego
 [...]
\ No newline at end of file

Reply via email to