Add a post to clarify EOL policy for 2.14 and 2.15
Also reword the sentence about EOL announcements in the support
section of the homepage to make it less strict.
Change-Id: Ifc0b7feda47fe7bcf2e4e739fe1a19d17c9baddd
diff --git a/_posts/2019-05-31-gerrit-end-of-life-update.md b/_posts/2019-05-31-gerrit-end-of-life-update.md
new file mode 100644
index 0000000..ade75dc
--- /dev/null
+++ b/_posts/2019-05-31-gerrit-end-of-life-update.md
@@ -0,0 +1,63 @@
+---
+title: Gerrit End of Life (EOL) Update
+tags: news
+keywords: news
+permalink: 2019-05-31-gerrit-end-of-life-update.html
+summary: "Update on the policy for bringing Gerrit releases to end of life (EOL)"
+hide_sidebar: true
+hide_navtoggle: true
+toc: true
+---
+
+Per the policy mentioned on the [project homepage](https://www.gerritcodereview.com/#support),
+only the last 2 releases are maintained on a best effort basis. Contrary to this,
+since releasing Gerrit 3.0.0 there are 4 stable branches that currently still have
+varying levels of activity: stable-3.0, stable-2.16, stable-2.15 and stable-2.14.
+
+This post clarifies the level of maintenance/support to be expected for the
+earlier branches.
+
+## Extended support for 2.15
+
+Support for 2.15 will be extended, due to the fact that moving forward to 2.16
+(and thus migrating to Note DB) is a large step that not all users are able to
+take so soon.
+
+## EOL for 2.14 and earlier
+
+Per the policy, we will bring 2.14 to end of life. This means we do not intend to
+make any further 2.14.x releases, and changes will not be accepted on the stable-2.14
+branch, with the following caveats:
+
+* Fixes for critical security issues may be accepted (and new releases made)
+after discussion among the steering committee and maintainers.
+
+* We want to keep the branch buildable with the latest version of Bazel, so
+related patches will be accepted. We may revisit this decision later depending on
+the volume of changes.
+
+Branches for earlier releases (stable-2.13 and older) are already inactive
+and are considered unmaintained. We do not intend to make any new releases
+from these branches, even for security fixes.
+
+## Support for non-core plugins
+
+* 2.15
+
+ Plugins will continue to be
+ [built for 2.15 on CI](https://gerrit-ci.gerritforge.com/view/Plugins-stable-2.15/),
+ and core maintainers will ensure that they still build, on a best-effort basis.
+
+* 2.14
+
+ Plugins will continue to be
+ [built for 2.14 on CI](https://gerrit-ci.gerritforge.com/view/Plugins-stable-2.14/),
+ but core maintainers will not put extra effort into keeping the builds working.
+
+* 2.13
+
+ Plugins will no longer be built on CI for 2.13 and earlier. Previously built
+ artifacts will be moved to the [CI archive](https://archive-ci.gerritforge.com/).
+
+A separate activity to identify actively used plugins and determine
+owners/maintainers will follow.
diff --git a/index.md b/index.md
index 7a36e2a..c3d6440 100644
--- a/index.md
+++ b/index.md
@@ -132,8 +132,8 @@
no guarantee for this. Which fixes are backported to these old
releases is decided on a case by case basis.
-End of life for old releases is not announced but happens implicitly
-when a new Gerrit version is released.
+End of life for old releases happens implicitly when a new Gerrit version
+is released, and is not necessarily announced.
For questions write to the mailing list (<a href="https://groups.google.com/group/repo-discuss">repo-discuss on Google Groups</a>),
join the IRC channel <a href="https://echelog.com/logs/browse/gerrit/">#gerrit</a>, or
