From 1bb9df8da137af66998f9719c0408af05baec0e4 Mon Sep 17 00:00:00 2001
From: "Jonathan S. Katz" <jonathan.katz@excoventures.com>
Date: Sat, 28 Oct 2017 17:19:02 -0400
Subject: [PATCH] Add clarifying language about how the EOL versioning policy
 works.

Language proposed by Noah Misch.
---
 templates/support/versioning.html | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/templates/support/versioning.html b/templates/support/versioning.html
index 69a09f5f..76342510 100644
--- a/templates/support/versioning.html
+++ b/templates/support/versioning.html
@@ -32,7 +32,7 @@ Upgrading to a minor release does not require a dump and restore; merely stop th
 <h2>PostgreSQL release support policy</h2>
 <p>
 The PostgreSQL project aims to fully support a major release for
-<b>five years</b>.
+<b>five years</b>. After its end-of-life (EOL) month ends, a major version receives one final <a href="/developer/roadmap/">minor release</a>. After that final minor release, bug fixing ceases for that major version.
 </p>
 
 <p>
-- 
2.39.5