lsmith Tue Nov 4 23:00:58 2008 UTC
Modified files: (Branch: PHP_5_3)
/php-src README.RELEASE_PROCESS
Log:
MFH
http://cvs.php.net/viewvc.cgi/php-src/README.RELEASE_PROCESS?r1=1.1.2.11&r2=1.1.2.12&diff_format=u
Index: php-src/README.RELEASE_PROCESS
diff -u php-src/README.RELEASE_PROCESS:1.1.2.11
php-src/README.RELEASE_PROCESS:1.1.2.12
--- php-src/README.RELEASE_PROCESS:1.1.2.11 Wed Sep 3 17:08:05 2008
+++ php-src/README.RELEASE_PROCESS Tue Nov 4 23:00:57 2008
@@ -48,33 +48,36 @@
3. Commit those changes
-4. tag the repository with the version f.e. "``cvs tag php_4_4_1RC1``"
+4. run the "scripts/dev/credits" script in php-src and commit the changes in
the
+credits files in ext/standard.
+
+5. 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).
-5. Bump up the version numbers in ``main/php_version.h``, ``configure.in``
+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.
-6. Commit those changes
+7. Commit those changes
-7. Log in onto the snaps box and go into the correct tree (f.e. the PHP_4_4
+8. Log in onto the snaps box and go into the correct tree (f.e. the PHP_4_4
branch if you're rolling 4.4.x releases).
-8. You do not have to update the tree, but of course you can with "``cvs up
-dP``".
+9. You do not have to update the tree, but of course you can with "``cvs up
-dP``".
-9. run: ``./makedist php 4.4.1RC1``, this will export the tree, create
configure
+10. run: ``./makedist php 4.4.1RC1``, this will export the tree, create
configure
and build two tarballs (one gz and one bz2).
-10. Copy those two tarballs to www.php.net, in your homedir their should be a
+11. Copy those two tarballs to www.php.net, in your homedir their should be a
directory "downloads/". Copy them into there, so that the system can generate
MD5 sums. If you do not have this directory, talk to Derick.
-11. Now the RC can be found on http://downloads.php.net/yourname,
+12. Now the RC can be found on http://downloads.php.net/yourname,
f.e. http://downloads.php.net/derick/
-12. Once the release has been tagged, contact the PHP Windows development team
+13. Once the release has been tagged, contact the PHP Windows development team
([EMAIL PROTECTED]) so that Windows binaries can be created. Once
those are made, they should be placed into the same directory as the source
snapshots.
@@ -137,34 +140,37 @@
4. Commit those changes
-5. tag the repository with the version f.e. "``cvs tag php_4_4_1``"
+5. run the "scripts/dev/credits" script in php-src and commit the changes in
the
+credits files in ext/standard.
+
+6. tag the repository with the version f.e. "``cvs tag php_4_4_1``"
(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!!
-6. Bump up the version numbers in ``main/php_version.h``, ``configure.in`` and
+7. 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.
-7. Commit those changes
+8. Commit those changes
-8. Log in onto the snaps box and go into the correct tree (f.e. the PHP_4_4
+9. Log in onto the snaps box and go into the correct tree (f.e. the PHP_4_4
branch if you're rolling 4.4.x releases).
-9. You do not have to update the tree, but of course you can with "``cvs up
-dP``".
+10. You do not have to update the tree, but of course you can with "``cvs up
-dP``".
-10. run: ``./makedist php 4.4.1``, this will export the tree, create configure
+11. run: ``./makedist php 4.4.1``, this will export the tree, create configure
and build two tarballs (one gz and one bz2).
-11. Commit those two tarballs to CVS (phpweb/distributions)
+12. Commit those two tarballs to CVS (phpweb/distributions)
-12. Once the release has been tagged, contact the PHP Windows development team
+13. Once the release has been tagged, contact the PHP Windows development team
([EMAIL PROTECTED]) so that Windows binaries can be created. Once
those are made, they should be committed to CVS too.
-13. Check if the pear files are updated (phar for 5.1+ or run
pear/make-pear-bundle.php with 4.4)
+14. Check if the pear files are updated (phar for 5.1+ or run
pear/make-pear-bundle.php with 4.4)
-14. When making a final release, also remind the PHP Windows development team
+15. When making a final release, also remind the PHP Windows development team
([EMAIL PROTECTED]) to prepare the installer packages for Win32.
Getting the stable release announced
--
PHP CVS Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php
