summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorChristoph M. Becker <cmbecker69@gmx.de>2019-01-24 12:41:53 +0100
committerChristoph M. Becker <cmbecker69@gmx.de>2019-01-24 12:41:53 +0100
commitd7480bda767e14ded6822849e1769afd7fd58c1c (patch)
tree4d90a8046fb268aa50d6f61cc40d757f917ea47a
parentfd41b99d58b5e1b2e7b7323b8e0744502c0f42bd (diff)
downloadphp-git-d7480bda767e14ded6822849e1769afd7fd58c1c.tar.gz
Fix README.RELEASE_PROCESS
According to current practice, and as discussed with other RMs.
-rw-r--r--README.RELEASE_PROCESS9
1 files changed, 6 insertions, 3 deletions
diff --git a/README.RELEASE_PROCESS b/README.RELEASE_PROCESS
index 58409f3e89..cff4686d26 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.