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 cc2d1f0 Publishing website 2020/12/24 00:01:30 at commit fbeb28e
cc2d1f0 is described below
commit cc2d1f0138025b6a7c8fc05e9fc406ce72d1c700
Author: jenkins <builds@apache.org>
AuthorDate: Thu Dec 24 00:01:30 2020 +0000
Publishing website 2020/12/24 00:01:30 at commit fbeb28e
---
website/generated-content/contribute/index.xml | 3 ++-
website/generated-content/contribute/release-guide/index.html | 4 ++--
website/generated-content/sitemap.xml | 2 +-
3 files changed, 5 insertions(+), 4 deletions(-)
diff --git a/website/generated-content/contribute/index.xml b/website/generated-content/contribute/index.xml
index e3f4098..3a22dca 100644
--- a/website/generated-content/contribute/index.xml
+++ b/website/generated-content/contribute/index.xml
@@ -525,6 +525,7 @@ oversees these just like any other JIRA issue marked with the &lsquo;Fix
Ver
<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_release_branchsh-to-cut-a-release-branch">Use cut_release_branch.sh
to cut a release branch</h4>
<ul>
<li>
@@ -954,8 +955,8 @@ It is created by <code>build_release_candidate.sh</code>
(see above).</
<h3 id="blog-post">Blog post</h3>
<p>Write a blog post similar to <a href="https://github.com/apache/beam/commit/b976e7be0744a32e99c841ad790c54920c8737f5#diff-8b1c3fd0d4a6765c16dfd18509182f9d">beam-2.23.0.md</a>.</p>
<ul>
-<li>Update <code>CHANGES.md</code> by adding a new section
for the next release.</li>
<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</strong>: Use git log to find contributors to
the releases. (e.g: <code>git log --pretty='%aN' ^v2.10.0 v2.11.0 | sort | uniq</code>).
Make sure to clean it up, as there may be duplicate or incorrect user names.</p>
diff --git a/website/generated-content/contribute/release-guide/index.html b/website/generated-content/contribute/release-guide/index.html
index dfbc334..185decf 100644
--- a/website/generated-content/contribute/release-guide/index.html
+++ b/website/generated-content/contribute/release-guide/index.html
@@ -45,7 +45,7 @@ authorization info cannot be found from ~/.docker/config.json file.</p><pre><cod
}
</code></pre><p>Release managers should have push permission; request membership
in the <a href=https://hub.docker.com/orgs/apache/teams/beammaintainers><code>beammaintainers</code>
team</a> by filing a JIRA with the Apache Infrastructure team, like <a href=https://issues.apache.org/jira/browse/INFRA-20900>INFRA-20900</a>.</p><h3
id=create-a-new-version-in-jira>Create a new version in JIRA</h3><p>When contributors
resolve an issue in JIRA, they are tagging it with a release that will con [...]
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 prep [...]
+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 prep [...]
./beam/release/src/main/scripts/cut_release_branch.sh \
--release=${RELEASE_VERSION} \
--next_release=${NEXT_VERSION}
@@ -134,7 +134,7 @@ redirects for the ‘current’ version, merge these PRs
in the order li
the PR is merged, the new contents will get picked up automatically and served
to the Beam website, usually within an hour.</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/11727>example</a>).</p><ul><li>Update
release version in <code>website/www/site/config.toml</code>.</li><li>Add
new release in <code>website/www/site/content/en/get-started/downloads.md</code>.<ul><li>Download
links will not work un [...]
+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/11727>example</a>).</p><ul><li>Update
release version in <code>website/www/site/config.toml</code>.</li><li>Add
new release in <code>website/www/site/content/en/get-started/downloads.md</code>.<ul><li>Download
links will not work un [...]
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>Template:</p>e><h4
id=checklist-to-proceed-to-the-next-step-1>Checklist to proceed to the next step</h4><ol><li>Maven
artifacts deployed to the staging repository of <a href=https://repository.apache.org/content/repositories/>repository.apache.org</a></li><li>Source
distribution deployed to the dev repository of <a href=https://dist.apache.org/repos/dist/dev/beam/>dist.apache.org</a></li><li>Website
pull request proposed to li [...]
docker pull apache/beam_python3.5_sdk:2.16.0_rc1
diff --git a/website/generated-content/sitemap.xml b/website/generated-content/sitemap.xml
index 3b0468e..96528e8 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>/categories/blog/</loc><lastmod>2020-12-23T09:07:16-08:00</lastmod></url><url><loc>/blog/</loc><lastmod>2020-12-23T09:07:16-08:00</lastmod></url><url><loc>/categories/</loc><lastmod>2020-12-23T09:07:16-08:00</lastmod></url><url><loc>/blog/dataframe-api-preview-available/</loc><lastmod>2020-12-17T16:58:23-08:00</lastmod></u
[...]
\ 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>/categories/blog/</loc><lastmod>2020-12-23T09:07:16-08:00</lastmod></url><url><loc>/blog/</loc><lastmod>2020-12-23T09:07:16-08:00</lastmod></url><url><loc>/categories/</loc><lastmod>2020-12-23T09:07:16-08:00</lastmod></url><url><loc>/blog/dataframe-api-preview-available/</loc><lastmod>2020-12-17T16:58:23-08:00</lastmod></u
[...]
\ No newline at end of file
|