[PHP-CVS] cvs: php-src / README.RELEASE_PROCESS
lsmith Tue Jun 30 11:37:16 2009 UTC Modified files: /php-srcREADME.RELEASE_PROCESS Log: formatting fix for the re-releasing section http://cvs.php.net/viewvc.cgi/php-src/README.RELEASE_PROCESS?r1=1.19r2=1.20diff_format=u Index: php-src/README.RELEASE_PROCESS diff -u php-src/README.RELEASE_PROCESS:1.19 php-src/README.RELEASE_PROCESS:1.20 --- php-src/README.RELEASE_PROCESS:1.19 Wed Jun 10 18:15:12 2009 +++ php-src/README.RELEASE_PROCESS Tue Jun 30 11:37:16 2009 @@ -248,9 +248,8 @@ II. For PHP5: Set $CURRENT_QA_RELEASE_5 to false - Re-releasing the same version (or -pl) - +-- 1. Commit the new binaries to ``phpweb/distributions/`` @@ -281,4 +280,3 @@ 5. Wait an hour or two, then send a mail to php-annou...@lists.php.net, php-gene...@lists.php.net and intern...@lists.php.net with a text similar to the news entry. - -- PHP CVS Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
[PHP-CVS] cvs: php-src / README.RELEASE_PROCESS
lsmith Tue Jun 30 14:24:15 2009 UTC Modified files: /php-srcREADME.RELEASE_PROCESS Log: expanded the section about how to create the changelog http://cvs.php.net/viewvc.cgi/php-src/README.RELEASE_PROCESS?r1=1.20r2=1.21diff_format=u Index: php-src/README.RELEASE_PROCESS diff -u php-src/README.RELEASE_PROCESS:1.20 php-src/README.RELEASE_PROCESS:1.21 --- php-src/README.RELEASE_PROCESS:1.20 Tue Jun 30 11:37:16 2009 +++ php-src/README.RELEASE_PROCESS Tue Jun 30 14:24:15 2009 @@ -210,6 +210,10 @@ III. ``s/Fixed bug #\([0-9]\+\)/?php bugfix(\1); ?/`` + IV. ``s/Fixed PECL bug #\([0-9]\+\)/?php peclbugfix(\1); ?/`` + + V. ``s/FR #\([0-9]\+\)/FR ?php bugl(\1); ?/`` + 4. ``cp releases/4_4_0.php releases/4_4_1.php`` 5. ``cvs add releases/4_4_1.php`` -- PHP CVS Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
[PHP-CVS] cvs: php-src / README.RELEASE_PROCESS
johannesWed Jun 10 18:15:12 2009 UTC Modified files: /php-srcREADME.RELEASE_PROCESS Log: Hannes said this shall not be run for RCs http://cvs.php.net/viewvc.cgi/php-src/README.RELEASE_PROCESS?r1=1.18r2=1.19diff_format=u Index: php-src/README.RELEASE_PROCESS diff -u php-src/README.RELEASE_PROCESS:1.18 php-src/README.RELEASE_PROCESS:1.19 --- php-src/README.RELEASE_PROCESS:1.18 Sat Apr 11 03:40:34 2009 +++ php-src/README.RELEASE_PROCESS Wed Jun 10 18:15:12 2009 @@ -114,21 +114,17 @@ 1. Update in ``php-bugs-web/include/functions.inc`` the ``show_version_option`` function to include the new RC and commit. -2. Run the bumpRelease script for phpweb in your local checkout - - a. ``php bin/bumpRelease 5`` (or ``php bin/bumpRelease 4`` for PHP4) - -3. Update ``phpweb/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 -4. Commit those changes: +3. Commit those changes: a. ``cvs commit include/version.inc include/releases.inc`` -5. For the first RC, write the doc team (php...@lists.php.net) about updating the +4. 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. Rolling a stable release -- PHP CVS Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
[PHP-CVS] cvs: php-src / README.RELEASE_PROCESS
philip Sat Apr 11 03:40:34 2009 UTC Modified files: /php-srcREADME.RELEASE_PROCESS Log: Removed an unnecessary item, that calls for doc builds http://cvs.php.net/viewvc.cgi/php-src/README.RELEASE_PROCESS?r1=1.17r2=1.18diff_format=u Index: php-src/README.RELEASE_PROCESS diff -u php-src/README.RELEASE_PROCESS:1.17 php-src/README.RELEASE_PROCESS:1.18 --- php-src/README.RELEASE_PROCESS:1.17 Wed Apr 8 08:38:57 2009 +++ php-src/README.RELEASE_PROCESS Sat Apr 11 03:40:34 2009 @@ -252,8 +252,6 @@ II. For PHP5: Set $CURRENT_QA_RELEASE_5 to false -12. Rebuild the English and Japanese docs (ask Derick) - Re-releasing the same version (or -pl) -- PHP CVS Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
[PHP-CVS] cvs: php-src / README.RELEASE_PROCESS
bjori Wed Apr 8 08:38:57 2009 UTC Modified files: /php-srcREADME.RELEASE_PROCESS Log: Add guidelines for re-releasing http://cvs.php.net/viewvc.cgi/php-src/README.RELEASE_PROCESS?r1=1.16r2=1.17diff_format=u Index: php-src/README.RELEASE_PROCESS diff -u php-src/README.RELEASE_PROCESS:1.16 php-src/README.RELEASE_PROCESS:1.17 --- php-src/README.RELEASE_PROCESS:1.16 Tue Feb 10 20:45:27 2009 +++ php-src/README.RELEASE_PROCESS Wed Apr 8 08:38:57 2009 @@ -253,3 +253,38 @@ II. For PHP5: Set $CURRENT_QA_RELEASE_5 to false 12. Rebuild the English and Japanese docs (ask Derick) + + +Re-releasing the same version (or -pl) + + +1. Commit the new binaries to ``phpweb/distributions/`` + +2. Edit ``phpweb/include/version.inc`` and change (X=major release number): + + a. If only releasing for one OS, make sure you edit only those variables + + b. ``$PHP_X_VERSION`` to the correct version + + c. ``$PHP_X_DATE`` to the release date + + d. ``$PHP_X_MD5`` array and update all the md5 sums + + e. Make sure there are no outdated notes or edited date keys in the + ``$RELEASES[X][$PHP_X_VERSION][source]`` array + +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. + + a. Call php bin/createNewsEntry in your local phpweb checkout + + b. Add the content for the news entry + +4. Commit all the changes (``include/version.inc``, ``archive/archive.xml``, +``archive/entries/-MM-DD-N.xml``) + +5. Wait an hour or two, then send a mail to php-annou...@lists.php.net, +php-gene...@lists.php.net and intern...@lists.php.net with a text similar to +the news entry. + -- PHP CVS Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
[PHP-CVS] cvs: php-src / README.RELEASE_PROCESS
lsmith Sun Feb 8 20:24:44 2009 UTC Modified files: /php-srcREADME.RELEASE_PROCESS Log: MFB primary testers list is now mailed for every release http://cvs.php.net/viewvc.cgi/php-src/README.RELEASE_PROCESS?r1=1.14r2=1.15diff_format=u Index: php-src/README.RELEASE_PROCESS diff -u php-src/README.RELEASE_PROCESS:1.14 php-src/README.RELEASE_PROCESS:1.15 --- php-src/README.RELEASE_PROCESS:1.14 Thu Nov 6 21:38:12 2008 +++ php-src/README.RELEASE_PROCESS Sun Feb 8 20:24:44 2009 @@ -89,11 +89,10 @@ pointing out the location of the release and the possible release date of either the next RC, or the final release. -2. Only for an RC release also send an email -(see example here http://news.php.net/php.qa/26069) **To** +2. Send an email (see example here http://news.php.net/php.qa/26069) **To** ``php...@lists.php.net`` and **CC** ``primary-qa-te...@lists.php.net``. -This email is to notify the selected projects about a new RC so that they can -make sure their projects keep working. Make sure that you have been setup +This email is to notify the selected projects about a new release so that they +can make sure their projects keep working. Make sure that you have been setup as a moderator for ``primary-qa-te...@lists.php.net`` by having someone (Wez, Derick) run the following commands for you: @@ -129,7 +128,7 @@ a. ``cvs commit include/version.inc include/releases.inc`` -5. For the first RC, write the doc team (php...@lists.php.net) about updating the +5. 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. Rolling a stable release -- PHP CVS Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
[PHP-CVS] cvs: php-src / README.RELEASE_PROCESS
philip Thu Nov 6 21:38:12 2008 UTC Modified files: /php-srcREADME.RELEASE_PROCESS Log: MFB: Added the update INSTALL and win32/install.txt tasks http://cvs.php.net/viewvc.cgi/php-src/README.RELEASE_PROCESS?r1=1.13r2=1.14diff_format=u Index: php-src/README.RELEASE_PROCESS diff -u php-src/README.RELEASE_PROCESS:1.13 php-src/README.RELEASE_PROCESS:1.14 --- php-src/README.RELEASE_PROCESS:1.13 Wed Nov 5 07:25:12 2008 +++ php-src/README.RELEASE_PROCESS Thu Nov 6 21:38:12 2008 @@ -129,6 +129,9 @@ a. ``cvs commit include/version.inc include/releases.inc`` +5. For the first RC, write the doc team ([EMAIL PROTECTED]) about updating the +INSTALL and win32/install.txt files which are generated from the PHP manual sources. + Rolling a stable release -- PHP CVS Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
[PHP-CVS] cvs: php-src / README.RELEASE_PROCESS
lsmith Tue Nov 4 23:00:18 2008 UTC Modified files: /php-srcREADME.RELEASE_PROCESS Log: added note about running scripts/dev/credits http://cvs.php.net/viewvc.cgi/php-src/README.RELEASE_PROCESS?r1=1.11r2=1.12diff_format=u Index: php-src/README.RELEASE_PROCESS diff -u php-src/README.RELEASE_PROCESS:1.11 php-src/README.RELEASE_PROCESS:1.12 --- php-src/README.RELEASE_PROCESS:1.11 Wed Sep 3 17:08:00 2008 +++ php-src/README.RELEASE_PROCESS Tue Nov 4 23:00:18 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])
[PHP-CVS] cvs: php-src / README.RELEASE_PROCESS
lsmith Wed Nov 5 07:25:12 2008 UTC Modified files: /php-srcREADME.RELEASE_PROCESS Log: typo fix (thx chris jones for spotting) http://cvs.php.net/viewvc.cgi/php-src/README.RELEASE_PROCESS?r1=1.12r2=1.13diff_format=u Index: php-src/README.RELEASE_PROCESS diff -u php-src/README.RELEASE_PROCESS:1.12 php-src/README.RELEASE_PROCESS:1.13 --- php-src/README.RELEASE_PROCESS:1.12 Tue Nov 4 23:00:18 2008 +++ php-src/README.RELEASE_PROCESS Wed Nov 5 07:25:12 2008 @@ -70,7 +70,7 @@ 10. run: ``./makedist php 4.4.1RC1``, this will export the tree, create configure and build two tarballs (one gz and one bz2). -11. 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 there 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. -- PHP CVS Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
[PHP-CVS] cvs: php-src / README.RELEASE_PROCESS
lsmith Wed Sep 3 17:08:00 2008 UTC Modified files: /php-srcREADME.RELEASE_PROCESS Log: - made it clear which steps are relevant for RCs only http://cvs.php.net/viewvc.cgi/php-src/README.RELEASE_PROCESS?r1=1.10r2=1.11diff_format=u Index: php-src/README.RELEASE_PROCESS diff -u php-src/README.RELEASE_PROCESS:1.10 php-src/README.RELEASE_PROCESS:1.11 --- php-src/README.RELEASE_PROCESS:1.10 Sun Aug 31 10:34:56 2008 +++ php-src/README.RELEASE_PROCESS Wed Sep 3 17:08:00 2008 @@ -78,15 +78,16 @@ ([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. -Getting the non stable release announced - +Getting the non stable release (alpha/beta/RC) announced + 1. Send an email (see example here: http://news.php.net/php.internals/19486) **To** [EMAIL PROTECTED] and [EMAIL PROTECTED] lists pointing out the location of the release and the possible release date of either the next RC, or the final release. -2. Send an email (see example here http://news.php.net/php.qa/26069) **To** +2. Only for an RC release also send an email +(see example here http://news.php.net/php.qa/26069) **To** [EMAIL PROTECTED] and **CC** [EMAIL PROTECTED] This email is to notify the selected projects about a new RC so that they can make sure their projects keep working. Make sure that you have been setup @@ -97,7 +98,7 @@ ``sudo -u ezmlm ezmlm-sub ~ezmlm/primary-qa-tester/mod moderator-email-address`` -3. Update the MD5 sums in ``qaweb/include/rc-md5sums.txt``. +3. Update the MD5 sums in ``qaweb/include/rc-md5sums.txt`` (no empty lines). 4. Update in ``qaweb/include/release-qa.php`` constants with the new RC and commit this. -- PHP CVS Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
[PHP-CVS] cvs: php-src / README.RELEASE_PROCESS
lsmith Sun Aug 31 08:32:21 2008 UTC Modified files: /php-srcREADME.RELEASE_PROCESS Log: added note about how to move extensions from/to pecl http://cvs.php.net/viewvc.cgi/php-src/README.RELEASE_PROCESS?r1=1.8r2=1.9diff_format=u Index: php-src/README.RELEASE_PROCESS diff -u php-src/README.RELEASE_PROCESS:1.8 php-src/README.RELEASE_PROCESS:1.9 --- php-src/README.RELEASE_PROCESS:1.8 Wed Aug 6 21:49:37 2008 +++ php-src/README.RELEASE_PROCESS Sun Aug 31 08:32:21 2008 @@ -20,6 +20,9 @@ 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. +Do not use cvs rm, because this will prevent moving the CVS history. + Rolling a non stable release (alpha/beta/RC) -- PHP CVS Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
[PHP-CVS] cvs: php-src / README.RELEASE_PROCESS
lsmith Sun Aug 31 10:34:57 2008 UTC Modified files: /php-srcREADME.RELEASE_PROCESS Log: - added further details on the steps necessary to move ext from/to pecl http://cvs.php.net/viewvc.cgi/php-src/README.RELEASE_PROCESS?r1=1.9r2=1.10diff_format=u Index: php-src/README.RELEASE_PROCESS diff -u php-src/README.RELEASE_PROCESS:1.9 php-src/README.RELEASE_PROCESS:1.10 --- php-src/README.RELEASE_PROCESS:1.9 Sun Aug 31 08:32:21 2008 +++ php-src/README.RELEASE_PROCESS Sun Aug 31 10:34:56 2008 @@ -21,7 +21,22 @@ 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. -Do not use cvs rm, because this will prevent moving the CVS history. +Contact [EMAIL PROTECTED] to get this taken care of. + +Moving extensions from php-src to PECL +- Filesystem: cp -r php-src/ext/foo pecl/foo +- cvs rm php-src/ext/foo + +If the extension is still usable or not dead, in cooperation with the extension +maintainers if any: +- create the pecl.php.net/foo package and its content, license, maintainer +- 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 Rolling a non stable release (alpha/beta/RC) -- PHP CVS Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
[PHP-CVS] cvs: php-src / README.RELEASE_PROCESS
lsmith Wed Aug 6 19:34:35 2008 UTC Modified files: /php-srcREADME.RELEASE_PROCESS Log: updated in regards to windows, added some clarifications and addition tipps http://cvs.php.net/viewvc.cgi/php-src/README.RELEASE_PROCESS?r1=1.5r2=1.6diff_format=u Index: php-src/README.RELEASE_PROCESS diff -u php-src/README.RELEASE_PROCESS:1.5 php-src/README.RELEASE_PROCESS:1.6 --- php-src/README.RELEASE_PROCESS:1.5 Fri Mar 14 21:52:09 2008 +++ php-src/README.RELEASE_PROCESS Wed Aug 6 19:34:35 2008 @@ -2,18 +2,35 @@ PHP Release Process === -Rolling a release candidate +General notes and tipps +--- + +1. Do not release on Fridays, Saturdays or Sundays +because the sysadmins can not upgrade stuff then. + +2. Package the day before a release. So if the release is to be on Thursday, +package on Wednesday. + +3. Ensure that Windows builds will work before packaging + +4. Follow all steps to the letter. When unclear ask previous RM's (Derick/Ilia) +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. + +Rolling a non stable release (alpha/beta/RC) --- 1. Check windows snapshot builder logs (http://snaps.php.net/win32/snapshot-STABLE.log f.e.) 2. 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. tag the repository with ``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!! +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 @@ -26,7 +43,7 @@ 7. 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 ofcourse you can with ``cvs up -dP``. +8. 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 and build two tarballs (one gz and one bz2). @@ -38,11 +55,11 @@ 11. 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 Edin Kadribasic (edink @ usual -php e-mail) so that Windows binaries can be created. Once those are made, they -should be placed into the same directory as the source snapshots. +12. 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. -Getting the Release Candidate out there +Getting the non stable release announced --- 1. Send an email (see example here: http://news.php.net/php.internals/19486) @@ -75,7 +92,7 @@ 1. Update in ``php-bugs-web/include/functions.inc`` the ``show_version_option`` function to include the new RC and commit. -2. Run the bumpRelease script for phpweb +2. Run the bumpRelease script for phpweb in your local checkout a. ``php bin/bumpRelease 5`` (or ``php bin/bumpRelease 4`` for PHP4) @@ -89,7 +106,7 @@ a. ``cvs commit include/version.inc include/releases.inc`` -Rolling a release +Rolling a stable release - 1. Check windows snapshot builder logs (http://snaps.php.net/win32/snapshot-STABLE.log f.e.) @@ -100,9 +117,9 @@ 4. Commit those changes -5. tag the repository with ``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!! +5. 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 possibly ``NEWS`` again, to the **next** version. F.e. if the release candidate @@ -114,26 +131,26 @@ 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 ofcourse you can with ``cvs up -dP``. +9. You do not have to update the tree, but of course you can with ``cvs up -dP``. 10. run: ``./makedist php 4.4.1``,
Re: [PHP-CVS] cvs: php-src / README.RELEASE_PROCESS
Hi! +General notes and tipps I think you have a typpo here ;) -- Stanislav Malyshev, Zend Software Architect [EMAIL PROTECTED] http://www.zend.com/ (408)253-8829 MSN: [EMAIL PROTECTED] -- PHP CVS Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP-CVS] cvs: php-src / README.RELEASE_PROCESS
On 06.08.2008, at 21:37, Stanislav Malyshev wrote: Hi! +General notes and tipps I think you have a typpo here ;) Bah, why does english have to be different than german? :) regards, Lukas Kahwe Smith [EMAIL PROTECTED] -- PHP CVS Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
[PHP-CVS] cvs: php-src / README.RELEASE_PROCESS
lsmith Wed Aug 6 19:41:54 2008 UTC Modified files: /php-srcREADME.RELEASE_PROCESS Log: lets me all american :) http://cvs.php.net/viewvc.cgi/php-src/README.RELEASE_PROCESS?r1=1.6r2=1.7diff_format=u Index: php-src/README.RELEASE_PROCESS diff -u php-src/README.RELEASE_PROCESS:1.6 php-src/README.RELEASE_PROCESS:1.7 --- php-src/README.RELEASE_PROCESS:1.6 Wed Aug 6 19:34:35 2008 +++ php-src/README.RELEASE_PROCESS Wed Aug 6 19:41:54 2008 @@ -2,7 +2,7 @@ PHP Release Process === -General notes and tipps +General notes and tips --- 1. Do not release on Fridays, Saturdays or Sundays @@ -195,7 +195,7 @@ a. security fixes, - b. changes in behaviour (whether due to a bug fix or not) + b. changes in behavior (whether due to a bug fix or not) 7. 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 -- PHP CVS Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
[PHP-CVS] cvs: php-src / README.RELEASE_PROCESS
lsmith Wed Aug 6 21:49:37 2008 UTC Modified files: /php-srcREADME.RELEASE_PROCESS Log: separate tagging of the zend dir should not be necessary, fix reST formatting of titles http://cvs.php.net/viewvc.cgi/php-src/README.RELEASE_PROCESS?r1=1.7r2=1.8diff_format=u Index: php-src/README.RELEASE_PROCESS diff -u php-src/README.RELEASE_PROCESS:1.7 php-src/README.RELEASE_PROCESS:1.8 --- php-src/README.RELEASE_PROCESS:1.7 Wed Aug 6 19:41:54 2008 +++ php-src/README.RELEASE_PROCESS Wed Aug 6 21:49:37 2008 @@ -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 @@ 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 @@ 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 @@ 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** [EMAIL PROTECTED] and [EMAIL PROTECTED] lists @@ -107,7 +108,7 @@ 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 @@ ([EMAIL PROTECTED]) to prepare the installer packages for Win32. Getting the stable release announced -- + 1. Run the bumpRelease script for phpweb on your local checkout -- PHP CVS Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
[PHP-CVS] cvs: php-src / README.RELEASE_PROCESS
lsmith Fri Mar 14 21:52:09 2008 UTC Modified files: /php-srcREADME.RELEASE_PROCESS Log: updated due to the creation of the primary testers mailinglist http://cvs.php.net/viewvc.cgi/php-src/README.RELEASE_PROCESS?r1=1.4r2=1.5diff_format=u Index: php-src/README.RELEASE_PROCESS diff -u php-src/README.RELEASE_PROCESS:1.4 php-src/README.RELEASE_PROCESS:1.5 --- php-src/README.RELEASE_PROCESS:1.4 Sat Mar 1 23:25:28 2008 +++ php-src/README.RELEASE_PROCESS Fri Mar 14 21:52:09 2008 @@ -51,12 +51,15 @@ either the next RC, or the final release. 2. Send an email (see example here http://news.php.net/php.qa/26069) **To** [EMAIL PROTECTED] and **Bcc** everybody on the -`PhP4yzhttp://wiki.pooteeweet.org/PhP4yz`_, -`PhP5yzhttp://wiki.pooteeweet.org/PhP5yz`_ or -`PhP6yzhttp://wiki.pooteeweet.org/PhP6yz`_ list (depending on the PHP version). [EMAIL PROTECTED] and **CC** [EMAIL PROTECTED] This email is to notify the selected projects about a new RC so that they can -make sure their projects keep working. +make sure their projects keep working. Make sure that you have been setup +as a moderator for [EMAIL PROTECTED] by having someone (Wez, +Derick) run the following commands for you: + +``ssh lists.php.net`` + +``sudo -u ezmlm ezmlm-sub ~ezmlm/primary-qa-tester/mod moderator-email-address`` 3. Update the MD5 sums in ``qaweb/include/rc-md5sums.txt``. -- PHP CVS Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
[PHP-CVS] cvs: php-src / README.RELEASE_PROCESS
lsmith Sat Mar 1 22:47:27 2008 UTC Modified files: /php-srcREADME.RELEASE_PROCESS Log: link primary tester URLs and tried to limit lines to 80 chars http://cvs.php.net/viewvc.cgi/php-src/README.RELEASE_PROCESS?r1=1.2r2=1.3diff_format=u Index: php-src/README.RELEASE_PROCESS diff -u php-src/README.RELEASE_PROCESS:1.2 php-src/README.RELEASE_PROCESS:1.3 --- php-src/README.RELEASE_PROCESS:1.2 Wed Dec 19 13:13:27 2007 +++ php-src/README.RELEASE_PROCESS Sat Mar 1 22:47:27 2008 @@ -11,34 +11,57 @@ 3. Commit those changes -4. tag the repository with ``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. Bumb 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. +4. tag the repository with ``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. Bumb 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. 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). +7. 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 ofcourse you can with ``cvs up -dP``. -9. 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 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, f.e. http://downloads.php.net/derick/ +9. run: ``./makedist php 4.4.1RC1``, this will export the tree, create configure +and build two tarballs (one gz and one bz2). -12. Once the release has been tagged, contact Edin Kadribasic (edink @ usual php e-mail) so that Windows binaries can be created. Once those are made, they should be placed into the same directory as the source snapshots. +10. 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, +f.e. http://downloads.php.net/derick/ + +12. Once the release has been tagged, contact Edin Kadribasic (edink @ usual +php e-mail) so that Windows binaries can be created. Once those are made, they +should be placed into the same directory as the source snapshots. Getting the Release Candidate out there --- -1. Send an email (see example here: http://news.php.net/php.internals/19486) **To** [EMAIL PROTECTED] and [EMAIL PROTECTED] lists pointing out the location of the release and the possible release date of either the next RC, or the final release. - -2. Send an email (see example here http://news.php.net/php.qa/26069) **To** [EMAIL PROTECTED] and **Bcc** everybody on the PhP4yz, PhP5yz or PhP6yz list (depending on the PHP version). This email is to notify the selected projects about a new RC so that they can make sure their projects keep working. +1. Send an email (see example here: http://news.php.net/php.internals/19486) +**To** [EMAIL PROTECTED] and [EMAIL PROTECTED] lists +pointing out the location of the release and the possible release date of +either the next RC, or the final release. + +2. Send an email (see example here http://news.php.net/php.qa/26069) **To** [EMAIL PROTECTED] and **Bcc** everybody on the +`PhP4yzhttp://wiki.pooteeweet.org/PhP4yz`_, +`PhP5yzhttp://wiki.pooteeweet.org/PhP5yz`_ or +`PhP6yzhttp://wiki.pooteeweet.org/PhP6yz`_ list (depending on the PHP version). +This email is to notify the selected projects about a new RC so that they can +make sure their projects keep working. 3. Update the MD5 sums in ``qaweb/include/rc-md5sums.txt``. -4. Update in ``qaweb/include/release-qa.php`` constants with the new RC and commit this. +4. Update in ``qaweb/include/release-qa.php`` constants with the new RC and +commit this. a. ``$BUILD_TEST_RELEASES`` = array(4.4.7RC1, 5.2.2RC1) @@ -46,7 +69,8 @@ c.
[PHP-CVS] cvs: php-src / README.RELEASE_PROCESS
lsmith Sat Mar 1 23:25:29 2008 UTC Modified files: /php-srcREADME.RELEASE_PROCESS Log: typo fix (thx chris) http://cvs.php.net/viewvc.cgi/php-src/README.RELEASE_PROCESS?r1=1.3r2=1.4diff_format=u Index: php-src/README.RELEASE_PROCESS diff -u php-src/README.RELEASE_PROCESS:1.3 php-src/README.RELEASE_PROCESS:1.4 --- php-src/README.RELEASE_PROCESS:1.3 Sat Mar 1 22:47:27 2008 +++ php-src/README.RELEASE_PROCESS Sat Mar 1 23:25:28 2008 @@ -7,7 +7,7 @@ 1. Check windows snapshot builder logs (http://snaps.php.net/win32/snapshot-STABLE.log f.e.) -2. Bumb the version numbers in ``main/php_version.h``, ``configure.in`` and possibly ``NEWS``. +2. Bump the version numbers in ``main/php_version.h``, ``configure.in`` and possibly ``NEWS``. 3. Commit those changes @@ -15,7 +15,7 @@ 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. Bumb up the version numbers in ``main/php_version.h``, ``configure.in`` +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 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 @@ -91,7 +91,7 @@ 1. Check windows snapshot builder logs (http://snaps.php.net/win32/snapshot-STABLE.log f.e.) -2. Bumb the version numbers in ``main/php_version.h``, ``configure.in`` and possibly ``NEWS``. +2. Bump the version numbers in ``main/php_version.h``, ``configure.in`` and possibly ``NEWS``. 3. **Merge** all related sections in NEWS (f.e. merge the 4.4.1RC1 and 4.4.0 sections) @@ -101,7 +101,7 @@ 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. Bumb up the version numbers in ``main/php_version.h``, ``configure.in`` and +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. -- PHP CVS Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
[PHP-CVS] cvs: php-src / README.RELEASE_PROCESS
derick Wed Dec 19 13:13:27 2007 UTC Modified files: /php-srcREADME.RELEASE_PROCESS Log: - Fixed rest warnings http://cvs.php.net/viewvc.cgi/php-src/README.RELEASE_PROCESS?r1=1.1r2=1.2diff_format=u Index: php-src/README.RELEASE_PROCESS diff -u php-src/README.RELEASE_PROCESS:1.1 php-src/README.RELEASE_PROCESS:1.2 --- php-src/README.RELEASE_PROCESS:1.1 Thu Nov 22 08:58:32 2007 +++ php-src/README.RELEASE_PROCESS Wed Dec 19 13:13:27 2007 @@ -134,7 +134,7 @@ 5. ``cvs add releases/4_4_1.php`` -6. Update the releases/*.php file with relevant data. The release announcement file should list in detail: +6. Update the ``releases/*.php`` file with relevant data. The release announcement file should list in detail: a. security fixes, -- PHP CVS Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
[PHP-CVS] cvs: php-src / README.RELEASE_PROCESS
lsmith Thu Nov 22 08:58:32 2007 UTC Added files: /php-srcREADME.RELEASE_PROCESS Log: - port from todo wiki to reST (http://wiki.pooteeweet.org/ReleaseChecklist) http://cvs.php.net/viewvc.cgi/php-src/README.RELEASE_PROCESS?view=markuprev=1.1 Index: php-src/README.RELEASE_PROCESS +++ php-src/README.RELEASE_PROCESS === PHP Release Process === Rolling a release candidate --- 1. Check windows snapshot builder logs (http://snaps.php.net/win32/snapshot-STABLE.log f.e.) 2. Bumb the version numbers in ``main/php_version.h``, ``configure.in`` and possibly ``NEWS``. 3. Commit those changes 4. tag the repository with ``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. Bumb 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. 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 ofcourse you can with ``cvs up -dP``. 9. 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 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, f.e. http://downloads.php.net/derick/ 12. Once the release has been tagged, contact Edin Kadribasic (edink @ usual php e-mail) so that Windows binaries can be created. Once those are made, they should be placed into the same directory as the source snapshots. Getting the Release Candidate out there --- 1. Send an email (see example here: http://news.php.net/php.internals/19486) **To** [EMAIL PROTECTED] and [EMAIL PROTECTED] lists pointing out the location of the release and the possible release date of either the next RC, or the final release. 2. Send an email (see example here http://news.php.net/php.qa/26069) **To** [EMAIL PROTECTED] and **Bcc** everybody on the PhP4yz, PhP5yz or PhP6yz list (depending on the PHP version). This email is to notify the selected projects about a new RC so that they can make sure their projects keep working. 3. Update the MD5 sums in ``qaweb/include/rc-md5sums.txt``. 4. Update in ``qaweb/include/release-qa.php`` constants with the new RC and commit this. a. ``$BUILD_TEST_RELEASES`` = array(4.4.7RC1, 5.2.2RC1) 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-web/include/functions.inc`` the ``show_version_option`` function to include the new RC and commit. 2. Run the bumpRelease script for phpweb a. ``php bin/bumpRelease 5`` (or ``php bin/bumpRelease 4`` for PHP4) 3. Update ``phpweb/include/version.inc`` (x=major version number) a. ``$PHP_x_RC`` = 5.3.0RC1 b. ``$PHP_x_RC_DATE`` = 06 September 2007 4. Commit those changes: a. ``cvs commit include/version.inc include/releases.inc`` Rolling a release - 1. Check windows snapshot builder logs (http://snaps.php.net/win32/snapshot-STABLE.log f.e.) 2. Bumb the version numbers in ``main/php_version.h``, ``configure.in`` and possibly ``NEWS``. 3. **Merge** all related sections in NEWS (f.e. merge the 4.4.1RC1 and 4.4.0 sections) 4. Commit those changes 5. tag the repository with ``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. Bumb 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. 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 ofcourse you can with ``cvs up -dP``. 10. 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. Once the release has been tagged, contact Edin Kadribasic (edink @ usual php e-mail) so that Windows binaries can be created. Once
