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:27 UTC
[beam-site] branch mergebot updated (6802cdb -> a5efcd1)
This is an automated email from the ASF dual-hosted git repository.
mergebot-role pushed a change to branch mergebot
in repository https://gitbox.apache.org/repos/asf/beam-site.git.
from 6802cdb This closes #538
add 86b7d03 Prepare repository for deployment.
new ca0180d Add long term support release concept
new 22556e9 Edit suggestions
new a5efcd1 This closes #537
The 3 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/contribute/release-guide/index.html | 11 +++++++++++
src/community/policies.md | 9 ++++++++-
2 files changed, 19 insertions(+), 1 deletion(-)
[beam-site] 03/03: This closes #537
Posted by me...@apache.org.
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 a5efcd1fea8292096e9083c082156e1cef270994
Merge: 86b7d03 22556e9
Author: Mergebot <me...@apache.org>
AuthorDate: Wed Aug 15 18:03:48 2018 +0000
This closes #537
src/community/policies.md | 9 ++++++++-
1 file changed, 8 insertions(+), 1 deletion(-)
[beam-site] 01/03: Add long term support release concept
Posted by me...@apache.org.
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).
[beam-site] 02/03: Edit suggestions
Posted by me...@apache.org.
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 22556e9f5a3efa48c5f3edac44225df06e90869d
Author: Melissa Pashniak <me...@google.com>
AuthorDate: Wed Aug 15 10:18:06 2018 -0700
Edit suggestions
---
src/community/policies.md | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/src/community/policies.md b/src/community/policies.md
index 1c2a5f6..a553e76 100644
--- a/src/community/policies.md
+++ b/src/community/policies.md
@@ -24,11 +24,11 @@ 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 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. 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 [...]
+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 depr [...]
-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.
+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.
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).