From d7480bda767e14ded6822849e1769afd7fd58c1c Mon Sep 17 00:00:00 2001
From: "Christoph M. Becker" <cmbecker69@gmx.de>
Date: Thu, 24 Jan 2019 12:41:53 +0100
Subject: [PATCH] Fix README.RELEASE_PROCESS

According to current practice, and as discussed with other RMs.
---
 README.RELEASE_PROCESS | 9 ++++++---
 1 file changed, 6 insertions(+), 3 deletions(-)

diff --git a/README.RELEASE_PROCESS b/README.RELEASE_PROCESS
index 58409f3e89c..cff4686d264 100644
--- a/README.RELEASE_PROCESS
+++ b/README.RELEASE_PROCESS
@@ -124,9 +124,12 @@ Getting the non stable release (alpha/beta/RC) announced
 
  b. ``$PHP_x_RC_DATE`` = "06 September 2007"
 
-3. Add a short notice to phpweb stating that there is a new release, and
-highlight the major important things (security fixes) and when it is important
-to upgrade.
+3. Skip this step for non stable releases after GA of minor or major versions
+   (e.g. announce 7.3.0RC1, but not 7.3.1RC1):
+
+   Add a short notice to phpweb stating that there is a new release, and
+   highlight the major important things (security fixes) and when it is
+   important to upgrade.
 
  a. Call php bin/createNewsEntry in your local phpweb checkout
     Use category "frontpage" *and* "releases" for all stable releases.