[
https://issues.apache.org/jira/browse/BEAM-5033?focusedWorklogId=135100&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-135100
]
ASF GitHub Bot logged work on BEAM-5033:
----------------------------------------
Author: ASF GitHub Bot
Created on: 15/Aug/18 18:06
Start Date: 15/Aug/18 18:06
Worklog Time Spent: 10m
Work Description: asfgit closed pull request #537: [BEAM-5033] Add long
term support release concept
URL: https://github.com/apache/beam-site/pull/537
This is a PR merged from a forked repository.
As GitHub hides the original diff on merge, it is displayed below for
the sake of provenance:
As this is a foreign pull request (from a fork), the diff is supplied
below (as it won't show otherwise due to GitHub magic):
diff --git a/src/community/policies.md b/src/community/policies.md
index 2b3d0e972..a553e76cc 100644
--- a/src/community/policies.md
+++ b/src/community/policies.md
@@ -24,4 +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. 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 deprecated immediately after the next following minor
release. We encourage you to update early and often; do not wait until the
deprecation date of the version you are using.
+
+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
[secur...@apache.org](mailto:secur...@apache.org). Apache Beam follows the
typical [Apache vulnerability handling
process](https://apache.org/security/committers.html#vulnerability-handling).
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
Issue Time Tracking
-------------------
Worklog Id: (was: 135100)
Time Spent: 40m (was: 0.5h)
> Define and publish support story for Beam releases
> --------------------------------------------------
>
> Key: BEAM-5033
> URL: https://issues.apache.org/jira/browse/BEAM-5033
> Project: Beam
> Issue Type: Task
> Components: website
> Reporter: Rafael Fernandez
> Assignee: Ahmet Altay
> Priority: Major
> Time Spent: 40m
> Remaining Estimate: 0h
>
> Propose, define, and publish a support story for Beam releases, clarifying
> how long a specific release is expected to be eligible for security or
> correctness patches.
>
> A user could naturally infer today that only the latest released version is
> eligible for such patches. Since we release every six weeks, this could be an
> opportunity to establish long-term support policies for selected releases.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
