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 6fc6a03 Publishing website 2021/03/31 18:03:48 at commit ec9e413
6fc6a03 is described below
commit 6fc6a03783640a15639757bc4a1f54dce6ee2df4
Author: jenkins <[email protected]>
AuthorDate: Wed Mar 31 18:03:48 2021 +0000
Publishing website 2021/03/31 18:03:48 at commit ec9e413
---
website/generated-content/contribute/index.xml | 36 ++++++++++++++++++++++
.../contribute/release-guide/index.html | 13 +++++---
website/generated-content/sitemap.xml | 2 +-
3 files changed, 46 insertions(+), 5 deletions(-)
diff --git a/website/generated-content/contribute/index.xml
b/website/generated-content/contribute/index.xml
index c91e2e5..651f32e 100644
--- a/website/generated-content/contribute/index.xml
+++ b/website/generated-content/contribute/index.xml
@@ -340,6 +340,7 @@ limitations under the License.
<li><a href="#tasks-you-need-to-do-manually">Tasks you need to do
manually</a></li>
</ul>
</li>
+<li><a href="#upload-release-candidate-to-pypi">Upload release candidate
to PyPi</a></li>
</ul>
</li>
<li><a href="#8-prepare-documents">8. Prepare documents</a>
@@ -961,6 +962,41 @@ Carefully review any new artifacts.</li>
</ol>
</li>
</ol>
+<h3 id="upload-release-candidate-to-pypi">Upload release candidate to
PyPi</h3>
+<ul>
+<li>
+<p><strong>Script:</strong> <a
href="https://github.com/apache/beam/blob/master/release/src/main/scripts/deploy_release_candidate_pypi.sh";>deploy_release_candidate_pypi.sh</a></p>
+</li>
+<li>
+<p><strong>Usage</strong></p>
+<pre><code> ./release/src/main/scripts/deploy_release_candidate_pypi.sh \
+--release &quot;${RELEASE_VERSION}&quot; \
+--rc &quot;${RC_NUM}&quot; \
+--user &quot;${GITHUB_USER}&quot; \
+--deploy
+</code></pre>
+</li>
+<li>
+<p><strong>The script will:</strong></p>
+<ol>
+<li>Download python binary artifacts</li>
+<li>Deploy release candidate to PyPI</li>
+</ol>
+</li>
+</ul>
+<p><strong>Attention:</strong> Verify that:</p>
+<ul>
+<li>The File names version include <code>rc-#</code> suffix</li>
+<li><a href="https://pypi.org/project/apache-beam/#files";>Download
Files</a> have:
+<ul>
+<li>All wheels uploaded as artifacts</li>
+<li>Release source&rsquo;s zip published</li>
+<li>Signatures and hashes do not need to be uploaded</li>
+</ul>
+</li>
+</ul>
+<p>You can do a dry run by omitting the <code>--deploy</code> flag.
Then it will only download the release candidate binaries. If it looks good,
rerun it with <code>--deploy</code>.</p>
+<p>See the source of the script for more details or to run commands
manually in case of a problem.</p>
<hr>
<h2 id="8-prepare-documents">8. Prepare documents</h2>
<h3 id="update-and-verify-javadoc">Update and Verify Javadoc</h3>
diff --git a/website/generated-content/contribute/release-guide/index.html
b/website/generated-content/contribute/release-guide/index.html
index 10412ce..6f3fa77 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.
@@ -140,7 +140,7 @@ Before building, the version must be set to a non-SNAPSHOT,
non-dev version.
The final state of the repository should match this diagram:</p><p><img
src=/images/tag-rc-commit.png alt="Set version to non-SNAPSHOT, non-dev, on
tagged RC commit" width=100%></p><ul><li>The release branch is
unchanged.</li><li>There is a commit not on the release branch with the version
adjusted.</li><li>The RC tag points to that
commit.</li></ul><ul><li><p><strong>Script:</strong> <a
href=https://github.com/apache/beam/blob/master/release/src/main/scripts/choose_rc_commit.sh>choose_r
[...]
--release "${RELEASE_VERSION}" \
--rc "${RC_NUM}" \
- --commit "${COMMIT_REF}" \
+--commit "${COMMIT_REF}" \
--clone \
--push-tag
</code></pre></li></ul><p>You can do a dry run by omitting the
<code>--push-tag</code> flag. Then it will only clone the repo,
@@ -156,7 +156,12 @@ 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 <a href=https://repos [...]
They should contain all relevant parts for each module, including
<code>pom.xml</code>, jar, test jar, javadoc, etc.
Artifact names should follow <a
href=https://search.maven.org/#search%7Cga%7C1%7Cg%3A%22org.apache.beam%22>the
existing format</a> in which artifact name mirrors directory structure, e.g.,
<code>beam-sdks-java-io-kafka</code>.
-Carefully review any new artifacts.</li></ol></li></ol><hr><h2
id=8-prepare-documents>8. Prepare documents</h2><h3
id=update-and-verify-javadoc>Update and Verify Javadoc</h3><p>The build with
<code>-PisRelease</code> creates the combined Javadoc for the release in
<code>sdks/java/javadoc</code>.</p><p>The file
<code>sdks/java/javadoc/build.gradle</code> contains a list of modules to
include and exclude, plus a list of offline URLs that populate links from
Beam’s Javadoc to the Java [...]
+Carefully review any new artifacts.</li></ol></li></ol><h3
id=upload-release-candidate-to-pypi>Upload release candidate to
PyPi</h3><ul><li><p><strong>Script:</strong> <a
href=https://github.com/apache/beam/blob/master/release/src/main/scripts/deploy_release_candidate_pypi.sh>deploy_release_candidate_pypi.sh</a></p></li><li><p><strong>Usage</strong></p><pre><code>
./release/src/main/scripts/deploy_release_candidate_pypi.sh \
+ --release "${RELEASE_VERSION}" \
+ --rc "${RC_NUM}" \
+ --user "${GITHUB_USER}" \
+ --deploy
+</code></pre></li><li><p><strong>The script will:</strong></p><ol><li>Download
python binary artifacts</li><li>Deploy release candidate to
PyPI</li></ol></li></ul><p><strong>Attention:</strong> Verify
that:</p><ul><li>The File names version include <code>rc-#</code>
suffix</li><li><a href=https://pypi.org/project/apache-beam/#files>Download
Files</a> have:<ul><li>All wheels uploaded as artifacts</li><li>Release
source’s zip published</li><li>Signatures and hashes do not need to be
[...]
If the version number has changed, download a new version of the corresponding
<code><module>-docs/package-list</code> file.</p></li></ul><h3
id=build-the-pydoc-api-reference>Build the Pydoc API reference</h3><p>Make sure
you have <code>tox</code> installed:</p><pre><code>pip install tox
</code></pre><p>Create the Python SDK documentation using sphinx by running a
helper script.</p><pre><code>cd sdks/python && pip install -r
build-requirements.txt && tox -e py37-docs
</code></pre><p>By default the Pydoc is generated in
<code>sdks/python/target/docs/_build</code>.
@@ -406,7 +411,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
2021/03/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:[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
2021/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 [...]
<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 71331a4..b1e7f05 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
