MFB primary testers list is now mailed for every release

diff --git a/README.RELEASE_PROCESS b/README.RELEASE_PROCESS
index 9805e7107d7cde928cc364cf8c8790200a73f3e7..24582ffe439079548aa0705d89a8830792c162bb 100644 (file)
--- a/README.RELEASE_PROCESS
+++ b/README.RELEASE_PROCESS
@@ -89,11 +89,10 @@ Getting the non stable release (alpha/beta/RC) announced
 pointing out "the location of the release" and "the possible release date of
 either the next RC, or the final release".
 
-2. Only for an RC release also send an email
-(see example here http://news.php.net/php.qa/26069) **To**
+2. Send an email (see example here http://news.php.net/php.qa/26069) **To**
 ``php-qa@lists.php.net`` and **CC** ``primary-qa-tests@lists.php.net``.
-This email is to notify the selected projects about a new RC so that they can
-make sure their projects keep working. Make sure that you have been setup
+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 ``primary-qa-tests@lists.php.net`` by having someone (Wez,
 Derick) run the following commands for you:
 
@@ -129,7 +128,7 @@ function to include the new RC and commit.
 
  a. ``cvs commit include/version.inc include/releases.inc``
 
-5. For the first RC, write the doc team (phpdoc@lists.php.net) about updating the 
+5. 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