summaryrefslogtreecommitdiff
path: root/README.RELEASE_PROCESS
diff options
context:
space:
mode:
authorLukas Smith <lsmith@php.net>2008-03-01 23:25:34 +0000
committerLukas Smith <lsmith@php.net>2008-03-01 23:25:34 +0000
commit375b4c036a610eb316141cb32d3abf929fdbe828 (patch)
tree4f789d5cd042e4d4dd646d733550469472e89be7 /README.RELEASE_PROCESS
parent6a1d20ad1dbd40376fa4e3549f9a5e5591d86a9d (diff)
downloadphp-git-375b4c036a610eb316141cb32d3abf929fdbe828.tar.gz
MFH
Diffstat (limited to 'README.RELEASE_PROCESS')
-rw-r--r--README.RELEASE_PROCESS8
1 files changed, 4 insertions, 4 deletions
diff --git a/README.RELEASE_PROCESS b/README.RELEASE_PROCESS
index abac9684f3..ede5e403f9 100644
--- a/README.RELEASE_PROCESS
+++ b/README.RELEASE_PROCESS
@@ -7,7 +7,7 @@ Rolling a release candidate
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 @@ Rolling a release candidate
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 @@ Rolling a release
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 @@ Rolling a release
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.