Rewrite of some language on "Beta Information page"

Primarily, this is to help more clearly define what a release candidate
is and isn't, but also took the time to add more clarifying language
around the beta process, what to expect, and what the community needs.

diff --git a/templates/pages/developer/beta.html b/templates/pages/developer/beta.html
index 7284e31a1f0264b7cb16799543d6c3c77c460e80..d2c4d3c4edbe041f25d1bd970e1b2390f6998faa 100644 (file)
--- a/templates/pages/developer/beta.html
+++ b/templates/pages/developer/beta.html
@@ -3,24 +3,36 @@
 {%block contents%}
 <h1>Beta Information <i class="fa fa-code"></i></h1>
 
-<p>PostgreSQL beta and release candidate releases are pre-release testing versions, not meant for production use. They
-    are feature-frozen, and we release these to the public for testing before our final release.</p>
+<p>PostgreSQL beta and release candidate releases are pre-release testing
+    versions before the community makes a new release generally available. They
+    are feature-frozen (i.e. no new features are added), and we release these to
+    the public for testing before our final release. PostgreSQL beta and
+    release candidate release are <strong>not meant for use in production
+    systems</strong>.</p>
 
-<p>The PostgreSQL Global Development Group strongly advises against using beta versions of PostgreSQL in production
-    installations or active development projects. While the PostgreSQL code is continuously subject to a number of
-    automated and manual tests, beta releases might have serious bugs. Features are subject to changes that are
-    backwards incompatible at any time during the development of the betas, and could possibly be removed
-    altogether.</p>
+<p>Betas and release candidates are made available to the community in order to
+    perform testing before the initial release. They are especially helpful
+    for developers of platforms, drivers, tools, and utilities which depend upon
+    PostgreSQL in order to prepare for changes in the new version. A release
+    candidate should be identical to the initial release of a new major version
+    of PostgreSQL, though additional changes could be made before the release is
+    made generally available.</p>
 
-<p>Betas and release candidates are meant for everyone who uses PostgreSQL to test before the full release. The process
-    of testing these betas will help the community to identify and fix bugs prior to release.  They are especially
-    useful for developers of platforms, drivers, tools, and utilities which depend upon PostgreSQL in order to prepare
-    for changes in the new version.</p>
+<p>The stability of each PostgreSQL release greatly depends on the community to
+    test the upcoming version with your workloads and testing tools in order to
+    find bugs and regressions before the initial release. The quality of user
+    testing helps determine when we can make a final release.</p>
+
+<p>The PostgreSQL Global Development Group strongly advises against using beta
+    versions of PostgreSQL in production installations or active development
+    projects. While the PostgreSQL code is continuously subject to a number of
+    automated and manual tests, beta releases might have serious bugs. Features
+    are subject to changes that are backwards incompatible at any time during
+    the development of the betas, and could possibly be removed altogether.</p>
 
 <!-- <p>PostgreSQL 10 has been released. The first beta of version 11 is not yet available for testing. Beta testing of
     version 11 is likely to begin in mid 2018.</p> -->
 
-
 <p>The current beta release is <strong>PostgreSQL 11 Beta 4</strong>.  For more information on the current beta release and how
     to test, please view the links below.</p>