lsmith          Sat Mar  1 23:25:29 2008 UTC

  Modified files:              
    /php-src    README.RELEASE_PROCESS 
  Log:
  typo fix (thx chris)
  
http://cvs.php.net/viewvc.cgi/php-src/README.RELEASE_PROCESS?r1=1.3&r2=1.4&diff_format=u
Index: php-src/README.RELEASE_PROCESS
diff -u php-src/README.RELEASE_PROCESS:1.3 php-src/README.RELEASE_PROCESS:1.4
--- php-src/README.RELEASE_PROCESS:1.3  Sat Mar  1 22:47:27 2008
+++ php-src/README.RELEASE_PROCESS      Sat Mar  1 23:25:28 2008
@@ -7,7 +7,7 @@
 
 1. Check windows snapshot builder logs 
(http://snaps.php.net/win32/snapshot-STABLE.log f.e.)
 
-2. Bumb the version numbers in ``main/php_version.h``, ``configure.in`` and 
possibly ``NEWS``.
+2. Bump the version numbers in ``main/php_version.h``, ``configure.in`` and 
possibly ``NEWS``.
 
 3. Commit those changes
 
@@ -15,7 +15,7 @@
 change that to the version you're rolling an RC for). When making 5.X release,
 you need to tag the Zend directory separately!!
 
-5. Bumb up the version numbers in ``main/php_version.h``, ``configure.in``
+5. 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
 candidate was "4.4.1RC1" then the new one should be "4.4.1RC2-dev" - regardless
 if we get a new RC or not. This is to make sure ``version_compare()`` can
@@ -91,7 +91,7 @@
 
 1. Check windows snapshot builder logs 
(http://snaps.php.net/win32/snapshot-STABLE.log f.e.)
 
-2. Bumb the version numbers in ``main/php_version.h``, ``configure.in`` and 
possibly ``NEWS``.
+2. Bump the version numbers in ``main/php_version.h``, ``configure.in`` and 
possibly ``NEWS``.
 
 3. **Merge** all related sections in NEWS (f.e. merge the 4.4.1RC1 and 4.4.0 
sections)
 
@@ -101,7 +101,7 @@
 change that to the version you're rolling an RC for). When making 5.X release,
 you need to tag the Zend directory separately!!
 
-6. Bumb up the version numbers in ``main/php_version.h``, ``configure.in`` and
+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 candidate
 was "4.4.1RC1" then the new one should be "4.4.1RC2-dev" - regardless if we get
 a new RC or not. This is to make sure ``version_compare()`` can correctly work.

-- 
PHP CVS Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php

Reply via email to