diff options
| author | Lukas Smith <lsmith@php.net> | 2008-08-06 21:49:37 +0000 |
|---|---|---|
| committer | Lukas Smith <lsmith@php.net> | 2008-08-06 21:49:37 +0000 |
| commit | 13b5ad479ee6034706fafa2357a27625797f8e11 (patch) | |
| tree | 11cf106874e3b08200f91a0a939dac188188dcc4 /README.RELEASE_PROCESS | |
| parent | 7ca6f6685c435ff1e957b994996ef25cbe207bfb (diff) | |
| download | php-git-13b5ad479ee6034706fafa2357a27625797f8e11.tar.gz | |
separate tagging of the zend dir should not be necessary, fix reST formatting of titles
Diffstat (limited to 'README.RELEASE_PROCESS')
| -rw-r--r-- | README.RELEASE_PROCESS | 13 |
1 files changed, 7 insertions, 6 deletions
diff --git a/README.RELEASE_PROCESS b/README.RELEASE_PROCESS index 39f40e84d0..58aa4a02d5 100644 --- a/README.RELEASE_PROCESS +++ b/README.RELEASE_PROCESS @@ -3,7 +3,7 @@ ======================= General notes and tips ---------------------------- +---------------------- 1. Do not release on Fridays, Saturdays or Sundays because the sysadmins can not upgrade stuff then. @@ -18,8 +18,10 @@ before proceeding. Ideally make sure that for the first releases one of the previous RM's is around to answer questions. For the steps related to the php/QA/bug websites try to have someone from the webmaster team (Bjori) on hand. +5. Verify the tags to be extra sure everything was tagged properly. + Rolling a non stable release (alpha/beta/RC) ---------------------------- +-------------------------------------------- 1. Check windows snapshot builder logs (http://snaps.php.net/win32/snapshot-STABLE.log f.e.) @@ -30,7 +32,6 @@ Do not use abbreviations for alpha and beta. 4. tag the repository with the version f.e. "``cvs tag php_4_4_1RC1``" (of course, you need to 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. 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 @@ -60,7 +61,7 @@ f.e. http://downloads.php.net/derick/ those are made, they should be placed into the same directory as the source snapshots. Getting the non stable release announced ---------------------------------------- +---------------------------------------- 1. Send an email (see example here: http://news.php.net/php.internals/19486) **To** ``internals@lists.php.net`` and ``php-general@lists.php.net`` lists @@ -107,7 +108,7 @@ function to include the new RC and commit. a. ``cvs commit include/version.inc include/releases.inc`` Rolling a stable release ------------------ +------------------------ 1. Check windows snapshot builder logs (http://snaps.php.net/win32/snapshot-STABLE.log f.e.) @@ -148,7 +149,7 @@ those are made, they should be committed to CVS too. (internals-win@lists.php.net) to prepare the installer packages for Win32. Getting the stable release announced ------------------------------ +------------------------------------ 1. Run the bumpRelease script for phpweb on your local checkout |