[PHP-CVS] svn: /php/php-src/ branches/PHP_5_3/README.RELEASE_PROCESS branches/PHP_5_4/README.RELEASE_PROCESS trunk/README.RELEASE_PROCESS
dsp Fri, 03 Feb 2012 08:14:39 + Revision: http://svn.php.net/viewvc?view=revisionrevision=323040 Log: mention git Changed paths: U php/php-src/branches/PHP_5_3/README.RELEASE_PROCESS U php/php-src/branches/PHP_5_4/README.RELEASE_PROCESS U php/php-src/trunk/README.RELEASE_PROCESS Modified: php/php-src/branches/PHP_5_3/README.RELEASE_PROCESS === --- php/php-src/branches/PHP_5_3/README.RELEASE_PROCESS 2012-02-03 08:13:39 UTC (rev 323039) +++ php/php-src/branches/PHP_5_3/README.RELEASE_PROCESS 2012-02-03 08:14:39 UTC (rev 323040) @@ -104,7 +104,7 @@ ``sudo -u ezmlm ezmlm-sub ~ezmlm/primary-qa-tester/mod moderator-email-address`` -3. Update ``web/qa/trunk/include/release-qa.php`` with the appropriate information. +3. Update ``qa.git/include/release-qa.php`` with the appropriate information. See the documentation within release-qa.php for more information, but all releases and RCs are configured here. Only $QA_RELEASES needs to be edited. @@ -113,15 +113,15 @@ Note: Remember to update the MD5 checksum information. -4. Update ``web/php/trunk/include/version.inc`` (x=major version number) +4. Update ``php.git/include/version.inc`` (x=major version number) a. ``$PHP_x_RC`` = 5.3.0RC1 b. ``$PHP_x_RC_DATE`` = 06 September 2007 -5. Commit those changes: +5. Commit and push those changes: - a. ``svn commit web/qa/trunk web/php-bugs/trunk web/php/trunk`` + a. ``git commit -a git push origin master`` 6. For the first RC, write the doc team (php...@lists.php.net) about updating the INSTALL and win32/install.txt files which are generated from the PHP manual sources. Modified: php/php-src/branches/PHP_5_4/README.RELEASE_PROCESS === --- php/php-src/branches/PHP_5_4/README.RELEASE_PROCESS 2012-02-03 08:13:39 UTC (rev 323039) +++ php/php-src/branches/PHP_5_4/README.RELEASE_PROCESS 2012-02-03 08:14:39 UTC (rev 323040) @@ -104,7 +104,7 @@ ``sudo -u ezmlm ezmlm-sub ~ezmlm/primary-qa-tester/mod moderator-email-address`` -3. Update ``web/qa/trunk/include/release-qa.php`` with the appropriate information. +3. Update ``qa.git/include/release-qa.php`` with the appropriate information. See the documentation within release-qa.php for more information, but all releases and RCs are configured here. Only $QA_RELEASES needs to be edited. @@ -113,15 +113,15 @@ Note: Remember to update the MD5 checksum information. -4. Update ``web/php/trunk/include/version.inc`` (x=major version number) +4. Update ``php.git/include/version.inc`` (x=major version number) a. ``$PHP_x_RC`` = 5.4.0RC1 b. ``$PHP_x_RC_DATE`` = 06 September 2007 -5. Commit those changes: +5. Commit and push those changes: - a. ``svn commit web/qa/trunk web/php-bugs/trunk web/php/trunk`` + a. ``git commit -a git push origin master`` 6. For the first RC, write the doc team (php...@lists.php.net) about updating the INSTALL and win32/install.txt files which are generated from the PHP manual sources. Modified: php/php-src/trunk/README.RELEASE_PROCESS === --- php/php-src/trunk/README.RELEASE_PROCESS2012-02-03 08:13:39 UTC (rev 323039) +++ php/php-src/trunk/README.RELEASE_PROCESS2012-02-03 08:14:39 UTC (rev 323040) @@ -104,7 +104,7 @@ ``sudo -u ezmlm ezmlm-sub ~ezmlm/primary-qa-tester/mod moderator-email-address`` -3. Update ``web/qa/trunk/include/release-qa.php`` with the appropriate information. +3. Update ``qa.git/include/release-qa.php`` with the appropriate information. See the documentation within release-qa.php for more information, but all releases and RCs are configured here. Only $QA_RELEASES needs to be edited. @@ -113,15 +113,15 @@ Note: Remember to update the MD5 checksum information. -4. Update ``web/php/trunk/include/version.inc`` (x=major version number) +4. Update ``php.git/include/version.inc`` (x=major version number) a. ``$PHP_x_RC`` = 5.4.0RC1 b. ``$PHP_x_RC_DATE`` = 06 September 2007 -5. Commit those changes: +5. Commit and push those changes: - a. ``svn commit web/qa/trunk web/php-bugs/trunk web/php/trunk`` + a. ``git commit -a git push origin master`` 6. For the first RC, write the doc team (php...@lists.php.net) about updating the INSTALL and win32/install.txt files which are generated from the PHP manual sources. -- PHP CVS Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
[PHP-CVS] svn: /php/php-src/ branches/PHP_5_3/README.RELEASE_PROCESS branches/PHP_5_4/README.RELEASE_PROCESS trunk/README.RELEASE_PROCESS
pajoye Wed, 14 Dec 2011 16:32:50 + Revision: http://svn.php.net/viewvc?view=revisionrevision=321018 Log: - add announce steps, s,cvs,svn, MFH Changed paths: U php/php-src/branches/PHP_5_3/README.RELEASE_PROCESS U php/php-src/branches/PHP_5_4/README.RELEASE_PROCESS U php/php-src/trunk/README.RELEASE_PROCESS Modified: php/php-src/branches/PHP_5_3/README.RELEASE_PROCESS === --- php/php-src/branches/PHP_5_3/README.RELEASE_PROCESS 2011-12-14 16:28:13 UTC (rev 321017) +++ php/php-src/branches/PHP_5_3/README.RELEASE_PROCESS 2011-12-14 16:32:50 UTC (rev 321018) @@ -20,12 +20,18 @@ 5. Verify the tags to be extra sure everything was tagged properly. -6. Moving extensions from/to PECL requires root level access to the CVS server. -Contact syst...@php.net to get this taken care of. +6. Moving extensions from/to PECL requires write acces to the destination. +Most developers should have this. Moving extensions from php-src to PECL -- Filesystem: cp -r php-src/ext/foo pecl/foo -- cvs rm php-src/ext/foo +- Checkout the pecl directory, most likely you want a sparse-root checkout + svn co --depth=empty https://svn.php.net/repository/pecl +- Create an directory for the extension incl. branch and tag structure, + no trunk at this point and commit this to svn + cd pecl; mkdir foo foo/tags foo/branches; svn add foo; svn commit +- Move the extension from php-src to the new location + svn mv https://svn.php.net/repository/php/php-src/trunk/ext/foo \ + https://svn.php.net/repository/pecl/foo/trunk If the extension is still usable or not dead, in cooperation with the extension maintainers if any: @@ -33,27 +39,25 @@ - create the package.xml, commit - release the package -Moving extensions from PECL to php-src -- Filesystem: cp -r pecl/foo php-src/ext/foo -OR depending on the wishes from the PECL extension maintainer. -- Filesystem: ln -s pecl/foo php-src/ext/foo +For Moving extensions from PECL to php-src the svn mv has to be tone the other +way round. Rolling a non stable release (alpha/beta/RC) -1. Check windows snapshot builder logs (http://snaps.php.net/win32/snapshot-STABLE.log f.e.) +1. Check windows snapshot builder logs (http://windows.php.net/downloads/snaps/ the last revision) -2. Bump the version numbers in ``main/php_version.h``, ``configure.in`` and possibly ``NEWS``. +2. run the scripts/dev/credits script in php-src and commit the changes in the +credits files in ext/standard. + +3. Bump the version numbers in ``main/php_version.h``, ``configure.in`` and possibly ``NEWS``. Do not use abbreviations for alpha and beta. -3. Commit those changes +4. Commit those changes and note the revision id. -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. To do the tag in a fast way do a svn copy on the server using full URLs. You should use the revision id from the above commit to prevent mistakes in case there was a commit in between. f.e. ``svn cp https://svn.php.net/repository/php/php-src/branches/PHP_5_3@308399 https://svn.php.net/repository/php/php-src/tags/php_5_3_6RC1``; +(of course, you need to change that to the version you're rolling an RC for). Mail php-internals to announce the tag so tests/validation/check can be done prior to package it. It is especially important for RCs. -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). - 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 @@ -65,7 +69,7 @@ 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). -9. 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 ``svn up``. 10. run: ``./makedist php 4.4.1RC1``, this will export the tree, create configure and build two tarballs (one gz and one bz2). @@ -109,22 +113,21 @@ Note: Remember to update the MD5 checksum information. -1. Update in ``php-bugs/trunk/include/functions.inc`` the ``show_version_option`` -function to include the new RC and commit. +4. Update ``web/php/trunk/include/version.inc`` (x=major version number) -2. Update ``phpweb/include/version.inc`` (x=major version number) - a. ``$PHP_x_RC`` = 5.3.0RC1 b. ``$PHP_x_RC_DATE`` = 06 September 2007 -3. Commit those changes: +5. Commit those changes: - a. ``cvs commit include/version.inc include/releases.inc`` + a. ``svn commit web/qa/trunk web/php-bugs/trunk web/php/trunk`` -4. For the first RC, write the doc team
[PHP-CVS] svn: /php/php-src/ branches/PHP_5_3/README.RELEASE_PROCESS branches/PHP_5_4/README.RELEASE_PROCESS trunk/README.RELEASE_PROCESS
philip Mon, 30 May 2011 23:26:33 + Revision: http://svn.php.net/viewvc?view=revisionrevision=311614 Log: Updated qa-release.php notes as per the new qa-release.php syntax Changed paths: U php/php-src/branches/PHP_5_3/README.RELEASE_PROCESS U php/php-src/branches/PHP_5_4/README.RELEASE_PROCESS U php/php-src/trunk/README.RELEASE_PROCESS Modified: php/php-src/branches/PHP_5_3/README.RELEASE_PROCESS === --- php/php-src/branches/PHP_5_3/README.RELEASE_PROCESS 2011-05-30 21:58:30 UTC (rev 311613) +++ php/php-src/branches/PHP_5_3/README.RELEASE_PROCESS 2011-05-30 23:26:33 UTC (rev 311614) @@ -100,17 +100,15 @@ ``sudo -u ezmlm ezmlm-sub ~ezmlm/primary-qa-tester/mod moderator-email-address`` -3. Update the MD5 sums in ``web/qa/trunk/include/rc-md5sums.txt`` (no empty lines). +3. Update ``web/qa/trunk/include/release-qa.php`` with the appropriate information. + See the documentation within release-qa.php for more information, but all releases + and RCs are configured here. Only $QA_RELEASES needs to be edited. -4. Update in ``web/qa/trunk/include/release-qa.php`` constants with the new RC and -commit this. + Example: When rolling an RC, set the 'rc' with appropriate information for the + given version. - a. ``$BUILD_TEST_RELEASES`` = array(4.4.7RC1, 5.2.2RC1) + Note: Remember to update the MD5 checksum information. - b. ``$CURRENT_QA_RELEASE_4`` = 4.4.7RC1 (``$CURRENT_QA_RELEASE_5`` for PHP5) - - c. ``$RELEASE_PROCESS`` = array(4 = true, 5 = true) - 1. Update in ``php-bugs/trunk/include/functions.inc`` the ``show_version_option`` function to include the new RC and commit. @@ -244,14 +242,12 @@ 11. Update ``qaweb/include/release-qa.php`` - a. Update the $BUILD_TEST_RELEASES array with the release name + - Update $QA_RELEASES with the appropriate information, which means bumping + the version number to an upcoming version. - b. Update $RELEASE_PROCESS array (set to false) + Example: If PHP 5.3.7 is being released, then PHP 5.3.8 is the next QA version, + so replace 5.3.7 with 5.3.8 within $QA_RELEASES. - I. For PHP4: Set $CURRENT_QA_RELEASE_4 to false - - II. For PHP5: Set $CURRENT_QA_RELEASE_5 to false - Re-releasing the same version (or -pl) -- Modified: php/php-src/branches/PHP_5_4/README.RELEASE_PROCESS === --- php/php-src/branches/PHP_5_4/README.RELEASE_PROCESS 2011-05-30 21:58:30 UTC (rev 311613) +++ php/php-src/branches/PHP_5_4/README.RELEASE_PROCESS 2011-05-30 23:26:33 UTC (rev 311614) @@ -104,17 +104,16 @@ ``sudo -u ezmlm ezmlm-sub ~ezmlm/primary-qa-tester/mod moderator-email-address`` -3. Update the MD5 sums in ``web/qa/trunk/include/rc-md5sums.txt`` (no empty lines, ordered by filename, odler version number first, .bz2 before .gz). +3. Update ``web/qa/trunk/include/release-qa.php`` with the appropriate information. + See the documentation within release-qa.php for more information, but all releases + and RCs are configured here. Only $QA_RELEASES needs to be edited. -4. Update in ``web/qa/trunk/include/release-qa.php`` constants with the new RC and -commit this. + Example: When rolling an RC, set the 'rc' with appropriate information for the + given version. - a. ``$BUILD_TEST_RELEASES`` = array(4.4.7RC1, 5.2.2RC1) + Note: Remember to update the MD5 checksum information. - b. ``$CURRENT_QA_RELEASE_4`` = 4.4.7RC1 (``$CURRENT_QA_RELEASE_5`` for PHP5) - c. ``$RELEASE_PROCESS`` = array(4 = true, 5 = true) - 1. Update in ``web/php-bugs/trunk/include/php_versions.php`` to include the new RC and commit. 2. Update ``web/php/trunk/include/version.inc`` (x=major version number) @@ -247,14 +246,12 @@ 11. Update ``qaweb/include/release-qa.php`` - a. Update the $BUILD_TEST_RELEASES array with the release name + - Update $QA_RELEASES with the appropriate information, which means bumping + the version number to an upcoming version. - b. Update $RELEASE_PROCESS array (set to false) + Example: If PHP 5.3.7 is being released, then PHP 5.3.8 is the next QA version, + so replace 5.3.7 with 5.3.8 within $QA_RELEASES. - I. For PHP4: Set $CURRENT_QA_RELEASE_4 to false - - II. For PHP5: Set $CURRENT_QA_RELEASE_5 to false - Re-releasing the same version (or -pl) -- Modified: php/php-src/trunk/README.RELEASE_PROCESS === --- php/php-src/trunk/README.RELEASE_PROCESS2011-05-30 21:58:30 UTC (rev 311613) +++ php/php-src/trunk/README.RELEASE_PROCESS2011-05-30 23:26:33 UTC (rev 311614) @@ -104,17 +104,15 @@ ``sudo -u ezmlm ezmlm-sub ~ezmlm/primary-qa-tester/mod moderator-email-address`` -3. Update the MD5 sums in ``web/qa/trunk/include/rc-md5sums.txt`` (no empty lines, ordered by filename, odler version number
