cvs: php-src / README.RELEASE_PROCESS

lsmith Sun Feb 8 20:24:44 2009 UTC Modified files: /php-src README.RELEASE_PROCESS Log: MFB primary testers list is now mailed for every release http://cvs.php.net/viewvc.cgi/php-src/README.RELEASE_PROCESS?r1=1.14&r2=1.15&diff_format=u Index: php-src/README.RELEASE_PROCESS diff -u php-src/README.RELEASE_PROCESS:1.14 php-src/README.RELEASE_PROCESS:1.15 --- php-src/README.RELEASE_PROCESS:1.14 Thu Nov 6 21:38:12 2008 +++ php-src/README.RELEASE_PROCESS Sun Feb 8 20:24:44 2009 @@ -89,11 +89,10 @@ 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 @@ 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