You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@beam.apache.org by me...@apache.org on 2018/08/15 18:06:43 UTC
[beam-site] branch asf-site updated (86b7d03 -> 7981cfc)
This is an automated email from the ASF dual-hosted git repository.
mergebot-role pushed a change to branch asf-site
in repository https://gitbox.apache.org/repos/asf/beam-site.git.
from 86b7d03 Prepare repository for deployment.
add ca0180d Add long term support release concept
add 22556e9 Edit suggestions
add a5efcd1 This closes #537
new 7981cfc Prepare repository for deployment.
The 1 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails. The revisions
listed as "add" were already present in the repository and have only
been added to this reference.
Summary of changes:
content/community/policies/index.html | 8 +++++++-
src/community/policies.md | 9 ++++++++-
2 files changed, 15 insertions(+), 2 deletions(-)
[beam-site] 01/01: Prepare repository for deployment.
Posted by me...@apache.org.
This is an automated email from the ASF dual-hosted git repository.
mergebot-role pushed a commit to branch asf-site
in repository https://gitbox.apache.org/repos/asf/beam-site.git
commit 7981cfc4e0656d3ecff68bb99a6908e8ae584cf9
Author: Mergebot <me...@apache.org>
AuthorDate: Wed Aug 15 18:06:41 2018 +0000
Prepare repository for deployment.
---
content/community/policies/index.html | 8 +++++++-
1 file changed, 7 insertions(+), 1 deletion(-)
diff --git a/content/community/policies/index.html b/content/community/policies/index.html
index 50b19d6..16bd65e 100644
--- a/content/community/policies/index.html
+++ b/content/community/policies/index.html
@@ -200,7 +200,13 @@ limitations under the License.
<h2 id="releases">Releases</h2>
-<p>Apache Beam makes minor releases every 6 weeks. Apache Beam has a <a href="https://calendar.google.com/calendar/embed?src=0p73sl034k80oob7seouanigd0%40group.calendar.google.com">calendar</a> for cutting the next release branch. Once a release branch is cut, the community works quickly to finalize that release.</p>
+<p>Apache Beam makes minor releases every 6 weeks. Apache Beam has a <a href="https://calendar.google.com/calendar/embed?src=0p73sl034k80oob7seouanigd0%40group.calendar.google.com">calendar</a> for cutting the next release branch. After a release branch is cut, the community works quickly to finalize that release.</p>
+
+<p>Apache Beam aims to make 8 releases in a 12 month period. To accommodate users with longer upgrade cycles, some of these releases will be tagged as long term support (LTS) releases. Starting with the 2.7.0 release, every fourth release will be a LTS release. LTS releases receive patches to fix major issues for 12 months, starting from the release’s initial release date. LTS releases are considered deprecated after 12 months. Non-LTS releases do not receive patches and are considered d [...]
+
+<p>It is up to the Apache Beam community to decide whether an identified issue is a major issue that warrants a patch release. Some examples of major issues are high severity security issues and high risk data integrity issues.</p>
+
+<p>If you wish to report a security vulnerability, please contact <a href="mailto:security@apache.org">security@apache.org</a>. Apache Beam follows the typical <a href="https://apache.org/security/committers.html#vulnerability-handling">Apache vulnerability handling process</a>.</p>
</div>
</div>