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 d61301880f87ad4cc72bee41b77d133458e67f21
Author: Melissa Pashniak <[email protected]>
AuthorDate: Thu Aug 16 13:23:35 2018 -0700

    Edit suggestions
---
 src/community/policies.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/src/community/policies.md b/src/community/policies.md
index 9674c31..2b96a7f 100644
--- a/src/community/policies.md
+++ b/src/community/policies.md
@@ -26,7 +26,7 @@ This page contains a list of major policies agreed upon by 
the Apache Beam commu
 
 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. After 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. To accommodate users 
with longer upgrade cycles, some of these releases will be tagged as long term 
support (LTS) releases. The community will mark some releases as LTS releases 
(based on the factors such as the number of LTS releases currently in flight, 
and whether the accumulated feature set from the last LTS provides significant 
value to upgrade). There will be at least one new LTS release in a 12 month 
period. LTS releases re [...]
+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. LTS releases receive patches to fix major issues for 12 
months, starting from the release's initial release date. There will be at 
least one new LTS release in a 12 month period, and LTS releases are considered 
deprecated after 12 months. The community will mark a release as a LTS release 
based on various fac [...]
 
 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.
 

Reply via email to