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 2ae6b53 Publishing website 2020/03/11 21:34:34 at commit e0a0041
2ae6b53 is described below
commit 2ae6b53eb14bb1099cb660f77209ea258fd2ca6e
Author: jenkins <bui...@apache.org>
AuthorDate: Wed Mar 11 21:34:34 2020 +0000
Publishing website 2020/03/11 21:34:34 at commit e0a0041
---
website/generated-content/roadmap/python-sdk/index.html | 13 ++++++++++---
1 file changed, 10 insertions(+), 3 deletions(-)
diff --git a/website/generated-content/roadmap/python-sdk/index.html
b/website/generated-content/roadmap/python-sdk/index.html
index 3b65828..0901cc7 100644
--- a/website/generated-content/roadmap/python-sdk/index.html
+++ b/website/generated-content/roadmap/python-sdk/index.html
@@ -227,6 +227,7 @@
<ul class="nav">
+ <li><a href="#sunsetting-python-2-support">Sunsetting Python 2
Support</a></li>
<li><a href="#python-3-support">Python 3 Support</a></li>
</ul>
@@ -250,9 +251,13 @@ limitations under the License.
<h1 id="python-sdk-roadmap">Python SDK Roadmap</h1>
+<h2 id="sunsetting-python-2-support">Sunsetting Python 2 Support</h2>
+
+<p>The Apache Beam community voted to join <a
href="https://python3statement.org/";>the pledge</a> to sunset Python 2 support
in 2020. The Beam community will discontinue Python 2 support in 2020 and
cannot guarantee long-term functional support or maintenance of Beam on Python
2. To ensure minimal disruption to your service, we strongly recommend that you
upgrade to Python 3 as soon as possible.</p>
+
<h2 id="python-3-support">Python 3 Support</h2>
-<p>Apache Beam 2.14.0 and higher support Python 3.5, 3.6, and 3.7. We continue
to <a
href="https://issues.apache.org/jira/browse/BEAM-1251?focusedCommentId=16890504&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-1689050";>improve</a>
the experience for Python 3 users and phase out Python 2 support (<a
href="https://issues.apache.org/jira/browse/BEAM-8371";>BEAM-8371</a>):</p>
+<p>Apache Beam 2.14.0 and higher support Python 3.5, 3.6, and 3.7. We’re
continuing to <a
href="https://issues.apache.org/jira/browse/BEAM-1251?focusedCommentId=16890504&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-1689050";>improve</a>
the experience for Python 3 users and add support for Python 3.x minor
versions (<a
href="https://issues.apache.org/jira/browse/BEAM-8494";>BEAM-8494</a>):</p>
<ul>
<li><a
href="https://issues.apache.org/jira/secure/RapidBoard.jspa?rapidView=245&view=detail";>Kanban
Board</a></li>
@@ -263,9 +268,11 @@ limitations under the License.
<p>Contributions and feedback are welcome!</p>
-<p>If you are interested to help, you can select an unassigned issue in the
Kanban board and assign it to yourself. Comment on the issue if you cannot
assign it yourself. When submitting a new PR, please tag <a
href="https://github.com/aaltay";>@aaltay</a>, and <a
href="https://github.com/tvalentyn";>@tvalentyn</a>.</p>
+<p>If you are interested in helping, you can select an unassigned issue on the
Kanban board and assign it to yourself. If you cannot assign the issue to
yourself, comment on the issue. When submitting a new PR, please tag <a
href="https://github.com/aaltay";>@aaltay</a>, and <a
href="https://github.com/tvalentyn";>@tvalentyn</a>.</p>
+
+<p>To report a Python 3 related issue, create a subtask in <a
href="https://issues.apache.org/jira/browse/BEAM-1251";>BEAM-1251</a> and cc:
[~altay] and [~tvalentyn] in a JIRA comment. The best way to help us identify
and investigate the issue is with a minimal pipeline that reproduces the
issue.</p>
-<p>To report a Python3-related issue, it is best to create a subtask to <a
href="https://issues.apache.org/jira/browse/BEAM-1251";>BEAM-1251</a> , and cc:
[~altay] and [~tvalentyn] in JIRA comment. You can also discuss encountered
issues on user@ or dev@ mailing lists as appropriate.</p>
+<p>You can also discuss encountered issues on user@ or dev@ mailing lists as
appropriate.</p>
</div>
</div>
