com php-src: corrections to release process documentation: README.RELEASE_PROCESS

Commit:    1f588df2a47bebd221a48f72dbe7e25ce10a041c
Author:    Joe Watkins <[email protected]>         Thu, 30 Mar 2017 17:52:22 +0100
Parents:   e6f95532987c1efd2cb0fa1e42fe6e627ae970f7
Branches:  master

Link:       http://git.php.net/?p=php-src.git;a=commitdiff;h=1f588df2a47bebd221a48f72dbe7e25ce10a041c

Log:
corrections to release process documentation

Changed paths:
  M  README.RELEASE_PROCESS


Diff:
diff --git a/README.RELEASE_PROCESS b/README.RELEASE_PROCESS
index cf9715f..25c1a62 100644
--- a/README.RELEASE_PROCESS
+++ b/README.RELEASE_PROCESS
@@ -110,40 +110,40 @@ those are made, they should be placed into the same directory as the source snap
 Getting the non stable release (alpha/beta/RC) announced
 --------------------------------------------------------
 
-1. Send an email **To** ``[email protected]`` and ``[email protected]`` 
-lists pointing out "the location of the release" and "the possible release date of
-either the next RC, or the final release". Include in this information the verification
-information output by ``gen_verify_stub``.
-
-2. Send an email (see example here http://news.php.net/php.pear.qa/5201) **To**
-``[email protected]`` and ``[email protected]``.
-This email is to notify the selected projects about a new release so that they
-can make sure their projects keep working. Make sure that you have been setup
-as a moderator for ``[email protected]`` by having someone (Hannes, Dan,
-Derick) run the following commands for you:
-
-``ssh lists.php.net``
-
-``sudo -u ezmlm ezmlm-sub ~ezmlm/primary-qa-tester/mod moderator-email-address``
-
-3. Update ``qa.git/include/release-qa.php`` with the appropriate information.
+1. Update ``qa.git/include/release-qa.php`` with the appropriate information.
    See the documentation within release-qa.php for more information, but all releases
    and RCs are configured here. Only $QA_RELEASES needs to be edited.
 
    Example: When rolling an RC, set the 'rc' with appropriate information for the
    given version.
 
-   Note: Remember to update the MD5 checksum information.
+   Note: Remember to update the MD5 and sha256 checksum information.
 
-4. Update ``web/php.git/include/version.inc`` (x=major version number)
+2. Update ``web/php.git/include/version.inc`` (x=major version number)
 
  a. ``$PHP_x_RC`` = "5.4.0RC1"  (should be set to "false" before)
 
  b. ``$PHP_x_RC_DATE`` = "06 September 2007"
 
-5. Commit and push those changes:
+3. Commit and push changes to qa and web
 
- a. ``git commit -a && git push origin master``
+*Wait for web and qa sites to update with new information before sending announce*
+
+4. Send an email **To** ``[email protected]`` and ``[email protected]`` 
+lists pointing out "the location of the release" and "the possible release date of
+either the next RC, or the final release". Include in this information the verification
+information output by ``gen_verify_stub``.
+
+5. Send an email (see example here http://news.php.net/php.pear.qa/5201) **To**
+``[email protected]`` and ``[email protected]``.
+This email is to notify the selected projects about a new release so that they
+can make sure their projects keep working. Make sure that you have been setup
+as a moderator for ``[email protected]`` by having someone (Hannes, Dan,
+Derick) run the following commands for you:
+
+``ssh lists.php.net``
+
+``sudo -u ezmlm ezmlm-sub ~ezmlm/primary-qa-tester/mod moderator-email-address``
 
 6. For the first RC, write the doc team ([email protected]) about updating the
 INSTALL and win32/install.txt files which are generated from the PHP manual sources.