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/20 22:05:34 UTC
[beam-site] branch asf-site updated (7bb066d -> d3a72da)
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 7bb066d Prepare repository for deployment.
add a4a7929 Update to LTS wording to remove every Nth release clause.
add 2a4d399 Edit suggestions
add 3604bc0 This closes #539
new d3a72da 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 | 2 +-
src/community/policies.md | 2 +-
2 files changed, 2 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 d3a72da435f1e18b8b4bc5546263d35e956e5942
Author: Mergebot <me...@apache.org>
AuthorDate: Mon Aug 20 22:05:32 2018 +0000
Prepare repository for deployment.
---
content/community/policies/index.html | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/content/community/policies/index.html b/content/community/policies/index.html
index 16bd65e..bf74714 100644
--- a/content/community/policies/index.html
+++ b/content/community/policies/index.html
@@ -202,7 +202,7 @@ limitations under the License.
<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>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 [...]
<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>