From 9fe1e9cb3e3c900c431b613bbf8bb26580d1d78c Mon Sep 17 00:00:00 2001
From: Ian Barwick <ian@2ndquadrant.com>
Date: Wed, 24 Oct 2018 15:03:57 +0900
Subject: [PATCH] doc: update 4.2 release notes

---
 HISTORY                         |  2 +-
 doc/appendix-release-notes.sgml | 12 +++++++++++-
 doc/upgrading-repmgr.sgml       |  5 +++--
 3 files changed, 15 insertions(+), 4 deletions(-)

diff --git a/HISTORY b/HISTORY
index 9ca408ab..2c594d27 100644
--- a/HISTORY
+++ b/HISTORY
@@ -1,4 +1,4 @@
-4.2.0   2018-??-??
+4.2     2018-10-24
         repmgr: add parameter "shutdown_check_timeout" for use by "standby switchover";
           GitHub #504 (Ian)
         repmgr: add "--node-id" option to "repmgr cluster cleanup"; GitHub #493 (Ian)
diff --git a/doc/appendix-release-notes.sgml b/doc/appendix-release-notes.sgml
index 7f2465d5..dea097c3 100644
--- a/doc/appendix-release-notes.sgml
+++ b/doc/appendix-release-notes.sgml
@@ -17,8 +17,18 @@
 
   <sect1 id="release-4.2">
     <title>Release 4.2</title>
-    <para><emphasis>???, 2018</emphasis></para>
+    <para><emphasis>Wed October 24, 2018</emphasis></para>
+
     <para>
+      &repmgr; 4.2 is a major release, with the main new feature being the
+      ability to <link linkend="repmgrd-pausing">pause repmgrd</link>, e.g. during planned maintenance
+      operations. Various other usability enhancements and a couple of bug fixes are also included;
+      see notes below for details.
+    </para>
+    <para>
+      A restart of the PostgreSQL server <emphasis>is</emphasis> required
+      for this release. For detailed upgrade instructions, see
+      <link linkend="upgrading-major-version">Upgrading a major version release</link>.
     </para>
 
     <sect2>
diff --git a/doc/upgrading-repmgr.sgml b/doc/upgrading-repmgr.sgml
index f177d7a3..36c567a5 100644
--- a/doc/upgrading-repmgr.sgml
+++ b/doc/upgrading-repmgr.sgml
@@ -188,7 +188,8 @@ ALTER EXTENSION repmgr UPDATE</programlisting>
 
 		<listitem>
           <simpara>
-			Reenable the <application>repmgrd</application> service on all nodes where it is in use.
+			Reenable the <application>repmgrd</application> service on all nodes where it is in use, and
+            ensure it is running.
           </simpara>
 		</listitem>
 
@@ -210,7 +211,7 @@ ALTER EXTENSION repmgr UPDATE</programlisting>
 	</indexterm>
 	<title>Checking repmgrd status after an upgrade</title>
 	<para>
-      From &repmgr; 4.2, once the upgrade is complete, execute the <command><link linkend="repmgr-daemon-status">repmgr daemon status</link></command>
+      From <link linkend="release-4.2">repmgr 4.2</link>, once the upgrade is complete, execute the <command><link linkend="repmgr-daemon-status">repmgr daemon status</link></command>
       command (on any node) to show an overview of the status of <application>repmgrd</application> on all nodes.
     </para>
   </sect2>