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:04:28 UTC
[beam-site] 01/03: Add long term support release concept
This is an automated email from the ASF dual-hosted git repository.
mergebot-role pushed a commit to branch mergebot
in repository https://gitbox.apache.org/repos/asf/beam-site.git
commit ca0180d485d710d914bb0c4038d6fb4628e1e585
Author: Ahmet Altay <al...@google.com>
AuthorDate: Mon Aug 13 10:45:11 2018 -0700
Add long term support release concept
---
src/community/policies.md | 7 +++++++
1 file changed, 7 insertions(+)
diff --git a/src/community/policies.md b/src/community/policies.md
index 2b3d0e9..1c2a5f6 100644
--- a/src/community/policies.md
+++ b/src/community/policies.md
@@ -25,3 +25,10 @@ This page contains a list of major policies agreed upon by the Apache Beam commu
## Releases
Apache Beam makes minor releases every 6 weeks. Apache Beam has a [calendar](https://calendar.google.com/calendar/embed?src=0p73sl034k80oob7seouanigd0%40group.calendar.google.com) for cutting the next release branch. Once a release branch is cut, the community works quickly to finalize that release.
+
+Apache Beam aims to make 8 releases in a 12 month period. In order to accommodate users with longer upgrade cycles some of these release will be tagged long term support (LTS) releases. Every fourth release starting from the 2.7.0 release will be a LTS release. LTS releases will receive patches for 12 months starting from their initial release dates for major issues. LTS releases will be considered deprecated after 12 months. Non-LTS releases will never receive patches and they will be c [...]
+
+It is up to the Apache Beam community to decide whether an identified issue is a major issue or not that will warrant a patch release. Some example major issues are high severity security issues and high risk data integrity issues.
+
+
+If you wish to report a security vulnerability, please contact [security@apache.org](mailto:security@apache.org). Apache Beam follows the typical [Apache vulnerability handling process](https://apache.org/security/committers.html#vulnerability-handling).