- add announce steps, s,cvs,svn, MFH

README.RELEASE_PROCESS

@@ -45,7 +45,7 @@ way round.
 Rolling a non stable release (alpha/beta/RC)
 --------------------------------------------
 
-1. Check windows snapshot builder logs (http://snaps.php.net/win32/snapshot-STABLE.log f.e.)
+1. Check windows snapshot builder logs (http://windows.php.net/downloads/snaps/ the last revision)
 
 2. run the "scripts/dev/credits" script in php-src and commit the changes in the
 credits files in ext/standard.
@@ -56,7 +56,7 @@ Do not use abbreviations for alpha and beta.
 4. Commit those changes and note the revision id.
 
 5. tag the repository with the version. To do the tag in a fast way do a svn copy on the server using full URLs. You should use the revision id from the above commit to prevent mistakes in case there was a commit in between. f.e. "``svn cp https://svn.php.net/repository/php/php-src/branches/PHP_5_3@308399  https://svn.php.net/repository/php/php-src/tags/php_5_3_6RC1``"
-(of course, you need to change that to the version you're rolling an RC for).
+(of course, you need to change that to the version you're rolling an RC for). Mail php-internals to announce the tag so tests/validation/check can be done prior to package it. It is especially important for RCs.
 
 6. Bump up the version numbers in ``main/php_version.h``, ``configure.in``
 and possibly ``NEWS`` again, to the **next** version. F.e. if the release
@@ -115,7 +115,7 @@ Derick) run the following commands for you:
 
 4. Update ``web/php/trunk/include/version.inc`` (x=major version number)
 
- a. ``$PHP_x_RC`` = "5.3.0RC1"
+ a. ``$PHP_x_RC`` = "5.4.0RC1"
 
  b. ``$PHP_x_RC_DATE`` = "06 September 2007"
 
@@ -126,6 +126,8 @@ Derick) run the following commands for you:
 6. 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.
 
+7. Publish the announce on www.php.net as well (for all releases, alpha, RCs or other)
+
 Rolling a stable release
 ------------------------
 
@@ -163,7 +165,7 @@ and build two tarballs (one gz and one bz2).
 
 13. Once the release has been tagged, contact the PHP Windows development team
 (internals-win@lists.php.net) so that Windows binaries can be created. Once
-those are made, they should be committed to CVS too.
+those are made, they should be committed to SVN too.
 
 14. Check if the pear files are updated (phar for 5.1+ or run pear/make-pear-bundle.php with 4.4)