diff options
Diffstat (limited to 'README.RELEASE_PROCESS')
| -rw-r--r-- | README.RELEASE_PROCESS | 14 |
1 files changed, 7 insertions, 7 deletions
diff --git a/README.RELEASE_PROCESS b/README.RELEASE_PROCESS index 1be2ac4b18..824fe833ac 100644 --- a/README.RELEASE_PROCESS +++ b/README.RELEASE_PROCESS @@ -32,7 +32,7 @@ team (Bjori) on hand. 6. Verify the tags to be extra sure everything was tagged properly. 7. Moving extensions from/to PECL requires write access to the destination. -Most developers should have this. +Most developers should have this. Moving extensions from php-src to PECL - Checkout the pecl directory, most likely you want a sparse-root checkout @@ -125,7 +125,7 @@ Getting the non stable release (alpha/beta/RC) announced b. ``$PHP_x_RC_DATE`` = "06 September 2007" -3. Add a short notice to phpweb stating that there is a new release, and +3. Add a short notice to phpweb stating that there is a new release, and highlight the major important things (security fixes) and when it is important to upgrade. @@ -140,7 +140,7 @@ to upgrade. *Wait for web and qa sites to update with new information before sending announce* -5. Send **separate** emails **To** ``internals@lists.php.net`` and ``php-general@lists.php.net`` +5. Send **separate** emails **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". Include in this information the verification information output by ``gen_verify_stub``. @@ -194,7 +194,7 @@ can be influenced by defining the environment variable TAR_OPTIONS='--format=gnu ``gpg -u YOUREMAIL --armor --detach-sign php-X.Y.Z.tar.xxx`` 11. Commit and push all the tarballs and signature files to web/php-distributions.git, - then update the git submodule reference in web/php.git: + then update the git submodule reference in web/php.git: ``git submodule init; git submodule update; cd distributions; @@ -266,7 +266,7 @@ f.e. ``ChangeLog-5.php`` from the NEWS file IV. ``s/Fixed PECL bug #\([0-9]\+\)/<?php peclbugfix(\1); ?>/`` V. ``s/FR #\([0-9]\+\)/FR <?php bugl(\1); ?>/`` - + e. You may want to try php-web/bin/news2html to automate this task 6. Add a short notice to phpweb stating that there is a new release, and @@ -340,7 +340,7 @@ Forking a new release branch 2. Just prior to cutting X.Y.0beta1, create the new branch locally. Add a commit on master after the branch point clearing the NEWS, UPGRADING - and UPGRADING.INTERNALS files, updating the version in configure.ac (run + and UPGRADING.INTERNALS files, updating the version in configure.ac (run ./configure to automatically update main/php_versions.h, too) and Zend/zend.h. Also list the new branch in README.GIT-RULES. Example: http://git.php.net/?p=php-src.git;a=commit;h=a63c99b @@ -365,7 +365,7 @@ New Release Manager Checklist one or more of the previous RMs sign your key. Publish your public key to pgp.mit.edu with: `gpg --keyserver pgp.mit.edu --send-keys $KEYID` -3. Request karma to edit main/php_version.h. Possibly karma for other restricted parts of +3. Request karma to edit main/php_version.h. Possibly karma for other restricted parts of php-src might come in question. 4. Request karma for web/qa.git and web/php.git for publishing release announcements. |