Create announcement entry on web-php even for non-stable

Author: sgolemon

README.RELEASE_PROCESS

@@ -125,16 +125,26 @@ Getting the non stable release (alpha/beta/RC) announced
 
  b. ``$PHP_x_RC_DATE`` = "06 September 2007"
 
-3. Commit and push changes to qa and web
+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.
+
+ a. Call php bin/createNewsEntry in your local phpweb checkout
+    Use category "releases" only (not "frontpage")
+
+ b. Add the content for the news entry. Be sure to include the text:
+    "THIS IS A DEVELOPMENT PREVIEW - DO NOT USE IT IN PRODUCTION!"
+
+4. Commit and push changes to qa and web
 
 *Wait for web and qa sites to update with new information before sending announce*
 
-4. Send an email **To** ``internals@lists.php.net`` and ``php-general@lists.php.net`` 
+5. Send an email **To** ``internals@lists.php.net`` and ``php-general@lists.php.net`` 
 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**
+6. Send an email (see example here http://news.php.net/php.pear.qa/5201) **To**
 ``php-qa@lists.php.net`` and ``primary-qa-tester@lists.php.net``.
 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
@@ -145,7 +155,7 @@ Derick) run the following commands for you:
 
 ``sudo -u ezmlm ezmlm-sub ~ezmlm/primary-qa-tester/mod moderator-email-address``
 
-6. For the first RC, write the doc team (phpdoc@lists.php.net) about updating the
+7. For the first RC, write the doc team (phpdoc@lists.php.net) about updating the
 INSTALL and win32/install.txt files which are generated from the PHP manual sources.
 
 Rolling a stable release