diff options
| author | Veres Lajos <vlajos@gmail.com> | 2014-02-14 14:51:10 +0200 |
|---|---|---|
| committer | Lior Kaplan <kaplanlior@gmail.com> | 2014-02-14 14:51:10 +0200 |
| commit | 35101e9ef4669bb076f6687f2fd1aa13f63695d0 (patch) | |
| tree | 2731d20c57cdf5909f677b1431ab209036a4dd0f /README.RELEASE_PROCESS | |
| parent | 6188674f1e10c8d72e0a27623ce9536f4706fe35 (diff) | |
| download | php-git-35101e9ef4669bb076f6687f2fd1aa13f63695d0.tar.gz | |
a few typofixes
Diffstat (limited to 'README.RELEASE_PROCESS')
| -rw-r--r-- | README.RELEASE_PROCESS | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/README.RELEASE_PROCESS b/README.RELEASE_PROCESS index 4343b6213c..21305f2993 100644 --- a/README.RELEASE_PROCESS +++ b/README.RELEASE_PROCESS @@ -139,7 +139,7 @@ Rolling a stable release 1. Checkout your release branch, you should have created when releasing previous RC and bump the version numbers in ``main/php_version.h``, ``configure.in`` and possibly ``NEWS``. -2. If a CVE commit needs to be merged to the release, then have it commited to +2. If a CVE commit needs to be merged to the release, then have it committed to the base branches and merged upwards as usual (f.e commit the CVE fix to 5.3, merge to 5.4, 5.5 etc...). Then you can cherry-pick it in your release branch. Don't forget to update NEWS manually in an extra commit then. |