cvs: php-src / README.RELEASE_PROCESS

lsmith Wed Sep 3 17:08:00 2008 UTC Modified files: /php-src README.RELEASE_PROCESS Log: - made it clear which steps are relevant for RCs only http://cvs.php.net/viewvc.cgi/php-src/README.RELEASE_PROCESS?r1=1.10&r2=1.11&diff_format=u Index: php-src/README.RELEASE_PROCESS diff -u php-src/README.RELEASE_PROCESS:1.10 php-src/README.RELEASE_PROCESS:1.11 --- php-src/README.RELEASE_PROCESS:1.10 Sun Aug 31 10:34:56 2008 +++ php-src/README.RELEASE_PROCESS Wed Sep 3 17:08:00 2008 @@ -78,15 +78,16 @@ (internals-win@lists.php.net) so that Windows binaries can be created. Once those are made, they should be placed into the same directory as the source snapshots. -Getting the non stable release announced ----------------------------------------- +Getting the non stable release (alpha/beta/RC) announced +-------------------------------------------------------- 1. Send an email (see example here: http://news.php.net/php.internals/19486) **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". -2. Send an email (see example here http://news.php.net/php.qa/26069) **To** +2. Only for an RC release also 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 @@ -97,7 +98,7 @@ `sudo -u ezmlm ezmlm-sub ~ezmlm/primary-qa-tester/mod moderator-email-address` -3. Update the MD5 sums in `qaweb/include/rc-md5sums.txt`. +3. Update the MD5 sums in `qaweb/include/rc-md5sums.txt` (no empty lines). 4. Update in `qaweb/include/release-qa.php` constants with the new RC and commit this.