[PHP-CVS] svn: /SVNROOT/ global_avail
lsmith Mon, 27 Dec 2010 12:31:34 + Revision: http://svn.php.net/viewvc?view=revisionrevision=306732 Log: adjusted web PROTOTYPE_2010 karma as per bjori's request Changed paths: U SVNROOT/global_avail Modified: SVNROOT/global_avail === --- SVNROOT/global_avail2010-12-27 09:30:40 UTC (rev 306731) +++ SVNROOT/global_avail2010-12-27 12:31:34 UTC (rev 306732) @@ -58,7 +58,7 @@ avail|danielc|web/php avail|ericstewart|web/php/*/archive -avail|stewartlord,dragoonis,seld|web/php/branches/PROTOTYPE_2010 +avail|stewartlord,dragoonis,seld|web/php/ # The PHP Presentation Group has access to the presentations on the # conf.php.net site. -- PHP CVS Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
[PHP-CVS] cvs: php-src / php.ini-development php.ini-production
lsmith Thu Jul 2 13:34:29 2009 UTC Modified files: /php-srcphp.ini-development php.ini-production Log: removed references to track_vars, since this option doesnt exist since ages http://cvs.php.net/viewvc.cgi/php-src/php.ini-development?r1=1.14r2=1.15diff_format=u Index: php-src/php.ini-development diff -u php-src/php.ini-development:1.14 php-src/php.ini-development:1.15 --- php-src/php.ini-development:1.14Tue Jun 30 08:49:05 2009 +++ php-src/php.ini-development Thu Jul 2 13:34:29 2009 @@ -22,7 +22,7 @@ ; The syntax of the file is extremely simple. Whitespace and Lines ; beginning with a semicolon are silently ignored (as you probably guessed). ; Section headers (e.g. [Foo]) are also silently ignored, even though -; they might mean something in the future. +; they might mean something in the future. ; Directives following the section heading [PATH=/www/mysite] only ; apply to PHP files in the /www/mysite directory. Directives @@ -437,11 +437,11 @@ ; Maximum execution time of each script, in seconds ; http://php.net/max-execution-time ; Note: This directive is hardcoded to 0 for the CLI SAPI -max_execution_time = 30 +max_execution_time = 30 ; Maximum amount of time each script may spend parsing request data. It's a good ; idea to limit this time on productions servers in order to eliminate unexpectedly -; long running scripts. +; long running scripts. ; Note: This directive is hardcoded to -1 for the CLI SAPI ; Default Value: -1 (Unlimited) ; Development Value: 60 (60 seconds) @@ -521,8 +521,8 @@ ; It's recommended that errors be logged on production servers rather than ; having the errors sent to STDOUT. ; Possible Values: -; Off = Do not display any errors -; stderr = Display errors to STDERR (affects only CGI/CLI binaries!) +; Off = Do not display any errors +; stderr = Display errors to STDERR (affects only CGI/CLI binaries!) ; On or stdout = Display errors to STDOUT ; Default Value: On ; Development Value: On @@ -641,8 +641,6 @@ ; Data Handling ; ; -; Note - track_vars is ALWAYS enabled - ; The separator used in PHP generated URLs to separate arguments. ; PHP's default setting is . ; http://php.net/arg-separator.output @@ -674,7 +672,7 @@ ; be registered into the super global array REQUEST. If so, it also determines ; the order in which that data is registered. The values for this directive are ; specified in the same manner as the variables_order directive, EXCEPT one. -; Leaving this value empty will cause PHP to use the value set in the +; Leaving this value empty will cause PHP to use the value set in the ; variables_order directive. It does not mean it will leave the super globals ; array REQUEST empty. ; Default Value: None @@ -685,9 +683,7 @@ ; Whether or not to register the EGPCS variables as global variables. You may ; want to turn this off if you don't want to clutter your scripts' global scope -; with user data. This makes most sense when coupled with track_vars - in which -; case you can access all of the GPC variables through the $HTTP_*_VARS[], -; variables. +; with user data. ; You should do your best to write your scripts so that they do not require ; register_globals to be on; Using form variables as globals can easily lead ; to possible security problems, if the code is not very well thought of. @@ -944,7 +940,7 @@ ; Note that many DLL files are located in the extensions/ (PHP 4) ext/ (PHP 5) ; extension folders as well as the separate PECL DLL download (PHP 5). ; Be sure to appropriately set the extension_dir directive. -; +; ;extension=php_bz2.dll ;extension=php_curl.dll ;extension=php_dba.dll @@ -1021,7 +1017,7 @@ ;iconv.output_encoding = ISO-8859-1 [intl] -;intl.default_locale = +;intl.default_locale = [sqlite] ; http://php.net/sqlite.assoc-case @@ -1035,9 +1031,9 @@ ; http://php.net/pcre.backtrack-limit ;pcre.backtrack_limit=10 -;PCRE library recursion limit. -;Please note that if you set this value to a high number you may consume all -;the available process stack and eventually crash PHP (due to reaching the +;PCRE library recursion limit. +;Please note that if you set this value to a high number you may consume all +;the available process stack and eventually crash PHP (due to reaching the ;stack size limit imposed by the Operating System). ; http://php.net/pcre.recursion-limit ;pcre.recursion_limit=10 @@ -1115,7 +,7 @@ ; http://php.net/odbc.default-pw ;odbc.default_pw= Not yet implemented -; Controls the ODBC cursor model. +; Controls the ODBC cursor model. ; Default: SQL_CURSOR_STATIC (default). ;odbc.default_cursortype @@ -1501,7 +1497,7 @@ ; Whether or not to add the httpOnly flag to the cookie, which makes it inaccessible to browser scripting languages such as JavaScript. ; http://php.net/session.cookie-httponly -session.cookie_httponly = +session.cookie_httponly = ; Handler
[PHP-CVS] cvs: php-src(PHP_5_3) / php.ini-development php.ini-production
lsmith Thu Jul 2 13:34:38 2009 UTC Modified files: (Branch: PHP_5_3) /php-srcphp.ini-production php.ini-development Log: MFH: removed references to track_vars, since this option doesnt exist since ages http://cvs.php.net/viewvc.cgi/php-src/php.ini-production?r1=1.1.2.14r2=1.1.2.15diff_format=u Index: php-src/php.ini-production diff -u php-src/php.ini-production:1.1.2.14 php-src/php.ini-production:1.1.2.15 --- php-src/php.ini-production:1.1.2.14 Sun Jun 28 17:56:18 2009 +++ php-src/php.ini-production Thu Jul 2 13:34:38 2009 @@ -22,7 +22,7 @@ ; The syntax of the file is extremely simple. Whitespace and Lines ; beginning with a semicolon are silently ignored (as you probably guessed). ; Section headers (e.g. [Foo]) are also silently ignored, even though -; they might mean something in the future. +; they might mean something in the future. ; Directives following the section heading [PATH=/www/mysite] only ; apply to PHP files in the /www/mysite directory. Directives @@ -437,11 +437,11 @@ ; Maximum execution time of each script, in seconds ; http://php.net/max-execution-time ; Note: This directive is hardcoded to 0 for the CLI SAPI -max_execution_time = 30 +max_execution_time = 30 ; Maximum amount of time each script may spend parsing request data. It's a good ; idea to limit this time on productions servers in order to eliminate unexpectedly -; long running scripts. +; long running scripts. ; Note: This directive is hardcoded to -1 for the CLI SAPI ; Default Value: -1 (Unlimited) ; Development Value: 60 (60 seconds) @@ -521,8 +521,8 @@ ; It's recommended that errors be logged on production servers rather than ; having the errors sent to STDOUT. ; Possible Values: -; Off = Do not display any errors -; stderr = Display errors to STDERR (affects only CGI/CLI binaries!) +; Off = Do not display any errors +; stderr = Display errors to STDERR (affects only CGI/CLI binaries!) ; On or stdout = Display errors to STDOUT ; Default Value: On ; Development Value: On @@ -641,8 +641,6 @@ ; Data Handling ; ; -; Note - track_vars is ALWAYS enabled - ; The separator used in PHP generated URLs to separate arguments. ; PHP's default setting is . ; http://php.net/arg-separator.output @@ -674,7 +672,7 @@ ; be registered into the super global array REQUEST. If so, it also determines ; the order in which that data is registered. The values for this directive are ; specified in the same manner as the variables_order directive, EXCEPT one. -; Leaving this value empty will cause PHP to use the value set in the +; Leaving this value empty will cause PHP to use the value set in the ; variables_order directive. It does not mean it will leave the super globals ; array REQUEST empty. ; Default Value: None @@ -685,9 +683,7 @@ ; Whether or not to register the EGPCS variables as global variables. You may ; want to turn this off if you don't want to clutter your scripts' global scope -; with user data. This makes most sense when coupled with track_vars - in which -; case you can access all of the GPC variables through the $HTTP_*_VARS[], -; variables. +; with user data. ; You should do your best to write your scripts so that they do not require ; register_globals to be on; Using form variables as globals can easily lead ; to possible security problems, if the code is not very well thought of. @@ -944,7 +940,7 @@ ; Note that many DLL files are located in the extensions/ (PHP 4) ext/ (PHP 5) ; extension folders as well as the separate PECL DLL download (PHP 5). ; Be sure to appropriately set the extension_dir directive. -; +; ;extension=php_bz2.dll ;extension=php_curl.dll ;extension=php_dba.dll @@ -1021,7 +1017,7 @@ ;iconv.output_encoding = ISO-8859-1 [intl] -;intl.default_locale = +;intl.default_locale = [sqlite] ; http://php.net/sqlite.assoc-case @@ -1035,9 +1031,9 @@ ; http://php.net/pcre.backtrack-limit ;pcre.backtrack_limit=10 -;PCRE library recursion limit. -;Please note that if you set this value to a high number you may consume all -;the available process stack and eventually crash PHP (due to reaching the +;PCRE library recursion limit. +;Please note that if you set this value to a high number you may consume all +;the available process stack and eventually crash PHP (due to reaching the ;stack size limit imposed by the Operating System). ; http://php.net/pcre.recursion-limit ;pcre.recursion_limit=10 @@ -1115,7 +,7 @@ ; http://php.net/odbc.default-pw ;odbc.default_pw= Not yet implemented -; Controls the ODBC cursor model. +; Controls the ODBC cursor model. ; Default: SQL_CURSOR_STATIC (default). ;odbc.default_cursortype @@ -1509,7 +1505,7 @@ ; Whether or not to add the httpOnly flag to the cookie, which makes it inaccessible to browser scripting languages such as JavaScript. ; http://php.net/session.cookie-httponly -session.cookie_httponly =
[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(PHP_5_3) / README.RELEASE_PROCESS
lsmith Tue Jun 30 11:37:24 2009 UTC Modified files: (Branch: PHP_5_3) /php-srcREADME.RELEASE_PROCESS Log: MFH: formatting fix for the re-releasing section http://cvs.php.net/viewvc.cgi/php-src/README.RELEASE_PROCESS?r1=1.1.2.19r2=1.1.2.20diff_format=u Index: php-src/README.RELEASE_PROCESS diff -u php-src/README.RELEASE_PROCESS:1.1.2.19 php-src/README.RELEASE_PROCESS:1.1.2.20 --- php-src/README.RELEASE_PROCESS:1.1.2.19 Wed Jun 10 18:15:22 2009 +++ php-src/README.RELEASE_PROCESS Tue Jun 30 11:37:24 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(PHP_5_3) / README.RELEASE_PROCESS
lsmith Tue Jun 30 14:24:25 2009 UTC Modified files: (Branch: PHP_5_3) /php-srcREADME.RELEASE_PROCESS Log: MFH: expanded the section about how to create the changelog http://cvs.php.net/viewvc.cgi/php-src/README.RELEASE_PROCESS?r1=1.1.2.20r2=1.1.2.21diff_format=u Index: php-src/README.RELEASE_PROCESS diff -u php-src/README.RELEASE_PROCESS:1.1.2.20 php-src/README.RELEASE_PROCESS:1.1.2.21 --- php-src/README.RELEASE_PROCESS:1.1.2.20 Tue Jun 30 11:37:24 2009 +++ php-src/README.RELEASE_PROCESS Tue Jun 30 14:24:25 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(PHP_5_3) / README.RELEASE_PROCESS
lsmith Tue Feb 10 20:45:42 2009 UTC Modified files: (Branch: PHP_5_3) /php-srcREADME.RELEASE_PROCESS Log: MFH primary tester ml needs to be in the TO not CC http://cvs.php.net/viewvc.cgi/php-src/README.RELEASE_PROCESS?r1=1.1.2.15r2=1.1.2.16diff_format=u Index: php-src/README.RELEASE_PROCESS diff -u php-src/README.RELEASE_PROCESS:1.1.2.15 php-src/README.RELEASE_PROCESS:1.1.2.16 --- php-src/README.RELEASE_PROCESS:1.1.2.15 Sun Feb 8 20:24:13 2009 +++ php-src/README.RELEASE_PROCESS Tue Feb 10 20:45:42 2009 @@ -89,8 +89,8 @@ 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** -``php...@lists.php.net`` and **CC** ``primary-qa-te...@lists.php.net``. +2. Send an email (see example here http://news.php.net/php.pear.qa/5201) **To** +``php...@lists.php.net`` and ``primary-qa-te...@lists.php.net``. 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, -- PHP CVS Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
[PHP-CVS] cvs: php-src(PHP_5_3) / README.RELEASE_PROCESS
lsmith Sun Feb 8 20:24:13 2009 UTC Modified files: (Branch: PHP_5_3) /php-srcREADME.RELEASE_PROCESS Log: primary testers list is now mailed for every release http://cvs.php.net/viewvc.cgi/php-src/README.RELEASE_PROCESS?r1=1.1.2.14r2=1.1.2.15diff_format=u Index: php-src/README.RELEASE_PROCESS diff -u php-src/README.RELEASE_PROCESS:1.1.2.14 php-src/README.RELEASE_PROCESS:1.1.2.15 --- php-src/README.RELEASE_PROCESS:1.1.2.14 Thu Nov 6 21:35:42 2008 +++ php-src/README.RELEASE_PROCESS Sun Feb 8 20:24:13 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
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: CVSROOT / avail
lsmith Mon Dec 1 22:27:49 2008 UTC Modified files: /CVSROOTavail Log: upgrade christian seiler to ZE karma level http://cvs.php.net/viewvc.cgi/CVSROOT/avail?r1=1.1471r2=1.1472diff_format=u Index: CVSROOT/avail diff -u CVSROOT/avail:1.1471 CVSROOT/avail:1.1472 --- CVSROOT/avail:1.1471Mon Dec 1 21:58:32 2008 +++ CVSROOT/avail Mon Dec 1 22:27:49 2008 @@ -36,7 +36,7 @@ avail|loudi,cweiske|phd,docweb # People who work on the Engine - not people with just tests access -avail|andi,zeev,andrei,stas,sterling,sascha,derick,sebastian,phanto,jani,hirokawa,fujimoto,rvenkat,sesser,kalowsky,iliaa,hyanantha,georg,wez,edink,helly,hholzgra,imajes,gschlossnagle,moriyoshi,dmitry,jon,pollita,tony2001,johannes,bjori,davidw,nicholsr,wharmby,felipe,robinf,scottmac,nlopess,mattwil,colder,lbarnaud,pajoye|Zend,ZendEngine2,TSRM +avail|andi,zeev,andrei,stas,sterling,sascha,derick,sebastian,phanto,jani,hirokawa,fujimoto,rvenkat,sesser,kalowsky,iliaa,hyanantha,georg,wez,edink,helly,hholzgra,imajes,gschlossnagle,moriyoshi,dmitry,jon,pollita,tony2001,johannes,bjori,davidw,nicholsr,wharmby,felipe,robinf,scottmac,nlopess,mattwil,colder,lbarnaud,pajoye,cseiler|Zend,ZendEngine2,TSRM # The PHP Documentation Group maintains the documentation and its # translations. -- PHP CVS Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
[PHP-CVS] cvs: php-src(PHP_5_3) / README.CVS-RULES
lsmith Sun Nov 9 12:13:04 2008 UTC Modified files: (Branch: PHP_5_3) /php-srcREADME.CVS-RULES Log: MFH http://cvs.php.net/viewvc.cgi/php-src/README.CVS-RULES?r1=1.18.2.1.2.2.2.2r2=1.18.2.1.2.2.2.3diff_format=u Index: php-src/README.CVS-RULES diff -u php-src/README.CVS-RULES:1.18.2.1.2.2.2.2 php-src/README.CVS-RULES:1.18.2.1.2.2.2.3 --- php-src/README.CVS-RULES:1.18.2.1.2.2.2.2 Sat Nov 24 13:52:29 2007 +++ php-src/README.CVS-RULESSun Nov 9 12:13:04 2008 @@ -53,36 +53,38 @@ PHP_5_1 This branch is closed. - PHP_4_4 Is used to release the PHP 4.4.x series. Only bugfixes are permitted - on this branch (Consult the releasemaster prior to commit). - - PHP_4_3 This branch is closed. + PHP_4_4 This branch is closed. The next few rules are more of a technical nature:: - 1. DO NOT TOUCH ChangeLog! It is automagically updated from the commit + 1. All changes should first go to HEAD and then get merged from HEAD + (aka MFH'ed) to all other relevant branches. + + 2. DO NOT TOUCH ChangeLog! It is automagically updated from the commit messages every day. Woe be to those who attempt to mess with it. - 2. All news updates intended for public viewing, such as new features, - bug fixes, improvements, etc., should go into the NEWS file. + 3. All news updates intended for public viewing, such as new features, + bug fixes, improvements, etc., should go into the NEWS file of the + *first* to be released version with the given change. In other words + any NEWS file change only needs to done in one branch. NB! Lines, starting with @ will go automagically into NEWS file, but this is NOT recommended, though. Please, add news entries directly to NEWS file and don't forget to keep them adjusted and sorted. - 3. Do not commit multiple file and dump all messages in one commit. If you + 4. Do not commit multiple file and dump all messages in one commit. If you modified several unrelated files, commit each group separately and provide a nice commit message for each one. See example below. - 4. Do write your commit message in such a way that it makes sense even + 5. Do write your commit message in such a way that it makes sense even without the corresponding diff. One should be able to look at it, and immediately know what was modified. Definitely include the function name in the message as shown below. - 5. In your commit messages, keep each line shorter than 80 characters. And + 6. In your commit messages, keep each line shorter than 80 characters. And try to align your lines vertically, if they wrap. It looks bad otherwise. - 6. If you modified a function that is callable from PHP, prepend PHP to + 7. If you modified a function that is callable from PHP, prepend PHP to the function name as shown below. -- PHP CVS Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
[PHP-CVS] cvs: php-src / README.CVS-RULES
lsmith Sun Nov 9 12:12:58 2008 UTC Modified files: /php-srcREADME.CVS-RULES Log: PHP 4.4 is no longer active, clarify that all changes should go to HEAD first and that NEWS entries should only go into one branch http://cvs.php.net/viewvc.cgi/php-src/README.CVS-RULES?r1=1.23r2=1.24diff_format=u Index: php-src/README.CVS-RULES diff -u php-src/README.CVS-RULES:1.23 php-src/README.CVS-RULES:1.24 --- php-src/README.CVS-RULES:1.23 Sat Nov 24 13:52:19 2007 +++ php-src/README.CVS-RULESSun Nov 9 12:12:57 2008 @@ -53,36 +53,38 @@ PHP_5_1 This branch is closed. - PHP_4_4 Is used to release the PHP 4.4.x series. Only bugfixes are permitted - on this branch (Consult the releasemaster prior to commit). - - PHP_4_3 This branch is closed. + PHP_4_4 This branch is closed. The next few rules are more of a technical nature:: - 1. DO NOT TOUCH ChangeLog! It is automagically updated from the commit + 1. All changes should first go to HEAD and then get merged from HEAD + (aka MFH'ed) to all other relevant branches. + + 2. DO NOT TOUCH ChangeLog! It is automagically updated from the commit messages every day. Woe be to those who attempt to mess with it. - 2. All news updates intended for public viewing, such as new features, - bug fixes, improvements, etc., should go into the NEWS file. + 3. All news updates intended for public viewing, such as new features, + bug fixes, improvements, etc., should go into the NEWS file of the + *first* to be released version with the given change. In other words + any NEWS file change only needs to done in one branch. NB! Lines, starting with @ will go automagically into NEWS file, but this is NOT recommended, though. Please, add news entries directly to NEWS file and don't forget to keep them adjusted and sorted. - 3. Do not commit multiple file and dump all messages in one commit. If you + 4. Do not commit multiple file and dump all messages in one commit. If you modified several unrelated files, commit each group separately and provide a nice commit message for each one. See example below. - 4. Do write your commit message in such a way that it makes sense even + 5. Do write your commit message in such a way that it makes sense even without the corresponding diff. One should be able to look at it, and immediately know what was modified. Definitely include the function name in the message as shown below. - 5. In your commit messages, keep each line shorter than 80 characters. And + 6. In your commit messages, keep each line shorter than 80 characters. And try to align your lines vertically, if they wrap. It looks bad otherwise. - 6. If you modified a function that is callable from PHP, prepend PHP to + 7. If you modified a function that is callable from PHP, prepend PHP to the function name as shown below. -- PHP CVS Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
[PHP-CVS] cvs: php-src /ext/msql .cvsignore CREDITS config.m4 config.w32 msql.dsp php_msql.c php_msql.h
lsmith Tue Nov 4 22:22:37 2008 UTC Removed files: /php-src/ext/msql config.w32 php_msql.h msql.dsp .cvsignore CREDITS php_msql.c config.m4 Log: ext/msql has been moved from php-src to PECL adhead of PHP 5.3 -- PHP CVS Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
[PHP-CVS] cvs: php-src(PHP_5_3) /ext/msql .cvsignore CREDITS config.m4 config.w32 msql.dsp php_msql.c php_msql.h
lsmith Tue Nov 4 22:22:44 2008 UTC Removed files: (Branch: PHP_5_3) /php-src/ext/msql .cvsignore php_msql.h config.w32 CREDITS msql.dsp config.m4 php_msql.c Log: MFH -- PHP CVS Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
[PHP-CVS] cvs: php-src(PHP_5_3) / NEWS
lsmith Tue Nov 4 22:31:48 2008 UTC Modified files: (Branch: PHP_5_3) /php-srcNEWS Log: ext/msql is now in PECL starting alpha3 [DOC] http://cvs.php.net/viewvc.cgi/php-src/NEWS?r1=1.2027.2.547.2.965.2.361r2=1.2027.2.547.2.965.2.362diff_format=u Index: php-src/NEWS diff -u php-src/NEWS:1.2027.2.547.2.965.2.361 php-src/NEWS:1.2027.2.547.2.965.2.362 --- php-src/NEWS:1.2027.2.547.2.965.2.361 Tue Nov 4 15:58:49 2008 +++ php-src/NEWSTue Nov 4 22:31:48 2008 @@ -4,7 +4,7 @@ - Upgraded bundled PCRE to version 7.8. (Nuno) - Upgraded bundled sqlite to version 3.6.2. (Scott) -- Changed error level E_ERROR into E_WARNING in Soap extension methods +- Changed error level E_ERROR into E_WARNING in Soap extension methods parameter validation. (Felipe) - Changed openssl info to show the shared library version number. (Scott) @@ -61,6 +61,8 @@ - Fixed bug #44575 (parse_ini_file comment # line problems). (Arnaud) - Fixed bug #44135 (PDO MySQL does not support CLIENT_FOUND_ROWS). (Johannes, chx1975 at gmail dot com) +- Moved ext/msql extension to PECL (Derick/Lukas): + 02 Sep 2008, PHP 5.3.0 Alpha 2 - Removed special treatment of /tmp in sessions for open_basedir. @@ -100,7 +102,7 @@ - Fixed bug #45763 (mysqli::multi_query does not work with mysqlnd). (Johannes) - Fixed bug #45757 (FreeBSD4.11 build failure: failed include; stdint.h). (Hannes) -- Fixed bug #45743 (property_exists fails to find static protected member in +- Fixed bug #45743 (property_exists fails to find static protected member in child class). (Felipe) - Fixed bug #45717 (Fileinfo/libmagic build fails, missing err.h and getopt.h). (Derick) @@ -112,10 +114,10 @@ (Derick) - Fixed bug #45447 (Filesystem time functions on Vista and server 2008). (Pierre) -- Fixed bug #45384 (parse_ini_file will result in parse error with no trailing +- Fixed bug #45384 (parse_ini_file will result in parse error with no trailing newline). (Arnaud) - Fixed bug #45044 (relative paths not resolved correctly). (Dmitry) -- Fixed bug #44842 (parse_ini_file keys that start/end with underscore). +- Fixed bug #44842 (parse_ini_file keys that start/end with underscore). (Arnaud) - Fixed bug #44100 (Inconsistent handling of static array declarations with duplicate keys). (Dmitry) @@ -266,7 +268,7 @@ . Added access to internal values of DSA, RSA and DH keys. (Dmitry) . Fixed a memory leak on openssl_decrypt(). (Henrique) . Fixed segfault caused by openssl_pkey_new(). (Henrique) - . Fixed bug caused by uninitilized variables in openssl_pkcs7_encrypt() and + . Fixed bug caused by uninitilized variables in openssl_pkcs7_encrypt() and openssl_pkcs7_sign(). (Henrique) . Fixed error message in openssl_seal(). (Henrique) @@ -307,8 +309,8 @@ - Improved crypt() function: (Pierre) . Added Blowfish and extended DES support. (Using Blowfish implementation from Solar Designer). - . Made crypt features portable by providing our own implementations -for crypt_r and the algorithms which are used when OS does not provide + . Made crypt features portable by providing our own implementations +for crypt_r and the algorithms which are used when OS does not provide them. PHP implementations are always used for Windows builds. - Added new extensions: @@ -415,7 +417,7 @@ - Fixed bug #45179 (--with-mysql-sock fails to compile work). (Andrey) - Fixed bug #45038 (Crash when using DateTimeZone object returned by Date::getTimezone). (Joe Orton, Derick) -- Fixed bug #45030 (Destination image alpha channel noise when using +- Fixed bug #45030 (Destination image alpha channel noise when using imagecopyresampled). (Pierre) - Fixed bug #44769 (declaring private magic methods should throw error). (Felipe) -- 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(PHP_5_3) / README.RELEASE_PROCESS
lsmith Tue Nov 4 23:00:58 2008 UTC Modified files: (Branch: PHP_5_3) /php-srcREADME.RELEASE_PROCESS Log: MFH http://cvs.php.net/viewvc.cgi/php-src/README.RELEASE_PROCESS?r1=1.1.2.11r2=1.1.2.12diff_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])
[PHP-CVS] cvs: php-src(PHP_5_3) / NEWS
lsmith Tue Nov 4 23:01:13 2008 UTC Modified files: (Branch: PHP_5_3) /php-srcNEWS Log: fixed ext/msql NEWS entry http://cvs.php.net/viewvc.cgi/php-src/NEWS?r1=1.2027.2.547.2.965.2.362r2=1.2027.2.547.2.965.2.363diff_format=u Index: php-src/NEWS diff -u php-src/NEWS:1.2027.2.547.2.965.2.362 php-src/NEWS:1.2027.2.547.2.965.2.363 --- php-src/NEWS:1.2027.2.547.2.965.2.362 Tue Nov 4 22:31:48 2008 +++ php-src/NEWSTue Nov 4 23:01:13 2008 @@ -4,6 +4,8 @@ - Upgraded bundled PCRE to version 7.8. (Nuno) - Upgraded bundled sqlite to version 3.6.2. (Scott) +- Moved ext/msql to PECL. (Derick, Lukas) + - Changed error level E_ERROR into E_WARNING in Soap extension methods parameter validation. (Felipe) - Changed openssl info to show the shared library version number. (Scott) @@ -61,7 +63,6 @@ - Fixed bug #44575 (parse_ini_file comment # line problems). (Arnaud) - Fixed bug #44135 (PDO MySQL does not support CLIENT_FOUND_ROWS). (Johannes, chx1975 at gmail dot com) -- Moved ext/msql extension to PECL (Derick/Lukas): 02 Sep 2008, PHP 5.3.0 Alpha 2 -- 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 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(PHP_5_3) / README.RELEASE_PROCESS
lsmith Wed Nov 5 07:25:18 2008 UTC Modified files: (Branch: PHP_5_3) /php-srcREADME.RELEASE_PROCESS Log: MFH http://cvs.php.net/viewvc.cgi/php-src/README.RELEASE_PROCESS?r1=1.1.2.12r2=1.1.2.13diff_format=u Index: php-src/README.RELEASE_PROCESS diff -u php-src/README.RELEASE_PROCESS:1.1.2.12 php-src/README.RELEASE_PROCESS:1.1.2.13 --- php-src/README.RELEASE_PROCESS:1.1.2.12 Tue Nov 4 23:00:57 2008 +++ php-src/README.RELEASE_PROCESS Wed Nov 5 07:25:18 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(PHP_5_3) / README.RELEASE_PROCESS
lsmith Wed Sep 3 17:08:05 2008 UTC Modified files: (Branch: PHP_5_3) /php-srcREADME.RELEASE_PROCESS Log: MFH http://cvs.php.net/viewvc.cgi/php-src/README.RELEASE_PROCESS?r1=1.1.2.10r2=1.1.2.11diff_format=u Index: php-src/README.RELEASE_PROCESS diff -u php-src/README.RELEASE_PROCESS:1.1.2.10 php-src/README.RELEASE_PROCESS:1.1.2.11 --- php-src/README.RELEASE_PROCESS:1.1.2.10 Sun Aug 31 10:35:06 2008 +++ php-src/README.RELEASE_PROCESS Wed Sep 3 17:08:05 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(PHP_5_3) / README.RELEASE_PROCESS
lsmith Sun Aug 31 08:32:32 2008 UTC Modified files: (Branch: PHP_5_3) /php-srcREADME.RELEASE_PROCESS Log: MFH http://cvs.php.net/viewvc.cgi/php-src/README.RELEASE_PROCESS?r1=1.1.2.8r2=1.1.2.9diff_format=u Index: php-src/README.RELEASE_PROCESS diff -u php-src/README.RELEASE_PROCESS:1.1.2.8 php-src/README.RELEASE_PROCESS:1.1.2.9 --- php-src/README.RELEASE_PROCESS:1.1.2.8 Wed Aug 6 21:49:47 2008 +++ php-src/README.RELEASE_PROCESS Sun Aug 31 08:32:32 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(PHP_5_3) / README.RELEASE_PROCESS
lsmith Sun Aug 31 10:35:06 2008 UTC Modified files: (Branch: PHP_5_3) /php-srcREADME.RELEASE_PROCESS Log: MFH http://cvs.php.net/viewvc.cgi/php-src/README.RELEASE_PROCESS?r1=1.1.2.9r2=1.1.2.10diff_format=u Index: php-src/README.RELEASE_PROCESS diff -u php-src/README.RELEASE_PROCESS:1.1.2.9 php-src/README.RELEASE_PROCESS:1.1.2.10 --- php-src/README.RELEASE_PROCESS:1.1.2.9 Sun Aug 31 08:32:32 2008 +++ php-src/README.RELEASE_PROCESS Sun Aug 31 10:35:06 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``,
[PHP-CVS] cvs: php-src(PHP_5_3) / README.RELEASE_PROCESS
lsmith Wed Aug 6 19:35:20 2008 UTC Modified files: (Branch: PHP_5_3) /php-srcREADME.RELEASE_PROCESS Log: MFH http://cvs.php.net/viewvc.cgi/php-src/README.RELEASE_PROCESS?r1=1.1.2.5r2=1.1.2.6diff_format=u Index: php-src/README.RELEASE_PROCESS diff -u php-src/README.RELEASE_PROCESS:1.1.2.5 php-src/README.RELEASE_PROCESS:1.1.2.6 --- php-src/README.RELEASE_PROCESS:1.1.2.5 Fri Mar 14 21:52:47 2008 +++ php-src/README.RELEASE_PROCESS Wed Aug 6 19:35:20 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) @@ -51,11 +68,11 @@ 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 **CC** [EMAIL PROTECTED] [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 -as a moderator for [EMAIL PROTECTED] by having someone (Wez, -Derick etc.) run the following commands for you: +as a moderator for [EMAIL PROTECTED] by having someone (Wez, +Derick) run the following commands for you: ``ssh lists.php.net`` @@ -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
[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(PHP_5_3) / README.RELEASE_PROCESS
lsmith Wed Aug 6 19:42:01 2008 UTC Modified files: (Branch: PHP_5_3) /php-srcREADME.RELEASE_PROCESS Log: MFH http://cvs.php.net/viewvc.cgi/php-src/README.RELEASE_PROCESS?r1=1.1.2.6r2=1.1.2.7diff_format=u Index: php-src/README.RELEASE_PROCESS diff -u php-src/README.RELEASE_PROCESS:1.1.2.6 php-src/README.RELEASE_PROCESS:1.1.2.7 --- php-src/README.RELEASE_PROCESS:1.1.2.6 Wed Aug 6 19:35:20 2008 +++ php-src/README.RELEASE_PROCESS Wed Aug 6 19:42:01 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(PHP_5_3) / README.RELEASE_PROCESS
lsmith Wed Aug 6 21:49:47 2008 UTC Modified files: (Branch: PHP_5_3) /php-srcREADME.RELEASE_PROCESS Log: MFH http://cvs.php.net/viewvc.cgi/php-src/README.RELEASE_PROCESS?r1=1.1.2.7r2=1.1.2.8diff_format=u Index: php-src/README.RELEASE_PROCESS diff -u php-src/README.RELEASE_PROCESS:1.1.2.7 php-src/README.RELEASE_PROCESS:1.1.2.8 --- php-src/README.RELEASE_PROCESS:1.1.2.7 Wed Aug 6 19:42:01 2008 +++ php-src/README.RELEASE_PROCESS Wed Aug 6 21:49:47 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(PHP_5_3) / README.RELEASE_PROCESS
lsmith Fri Mar 14 21:52:47 2008 UTC Modified files: (Branch: PHP_5_3) /php-srcREADME.RELEASE_PROCESS Log: MFH http://cvs.php.net/viewvc.cgi/php-src/README.RELEASE_PROCESS?r1=1.1.2.4r2=1.1.2.5diff_format=u Index: php-src/README.RELEASE_PROCESS diff -u php-src/README.RELEASE_PROCESS:1.1.2.4 php-src/README.RELEASE_PROCESS:1.1.2.5 --- php-src/README.RELEASE_PROCESS:1.1.2.4 Sat Mar 1 23:25:34 2008 +++ php-src/README.RELEASE_PROCESS Fri Mar 14 21:52:47 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 etc.) 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(PHP_5_3) / README.RELEASE_PROCESS
lsmith Sat Mar 1 22:47:33 2008 UTC Modified files: (Branch: PHP_5_3) /php-srcREADME.RELEASE_PROCESS Log: MFH http://cvs.php.net/viewvc.cgi/php-src/README.RELEASE_PROCESS?r1=1.1.2.2r2=1.1.2.3diff_format=u Index: php-src/README.RELEASE_PROCESS diff -u php-src/README.RELEASE_PROCESS:1.1.2.2 php-src/README.RELEASE_PROCESS:1.1.2.3 --- php-src/README.RELEASE_PROCESS:1.1.2.2 Thu Nov 22 08:59:05 2007 +++ php-src/README.RELEASE_PROCESS Sat Mar 1 22:47:33 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(PHP_5_3) / README.RELEASE_PROCESS
lsmith Sat Mar 1 23:25:34 2008 UTC Modified files: (Branch: PHP_5_3) /php-srcREADME.RELEASE_PROCESS Log: MFH http://cvs.php.net/viewvc.cgi/php-src/README.RELEASE_PROCESS?r1=1.1.2.3r2=1.1.2.4diff_format=u Index: php-src/README.RELEASE_PROCESS diff -u php-src/README.RELEASE_PROCESS:1.1.2.3 php-src/README.RELEASE_PROCESS:1.1.2.4 --- php-src/README.RELEASE_PROCESS:1.1.2.3 Sat Mar 1 22:47:33 2008 +++ php-src/README.RELEASE_PROCESS Sat Mar 1 23:25:34 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.MAILINGLIST_RULES
lsmith Thu Jan 17 14:37:58 2008 UTC Modified files: /php-srcREADME.MAILINGLIST_RULES Log: - mention rfc 1855 http://cvs.php.net/viewvc.cgi/php-src/README.MAILINGLIST_RULES?r1=1.3r2=1.4diff_format=u Index: php-src/README.MAILINGLIST_RULES diff -u php-src/README.MAILINGLIST_RULES:1.3 php-src/README.MAILINGLIST_RULES:1.4 --- php-src/README.MAILINGLIST_RULES:1.3Fri Jan 11 14:01:52 2008 +++ php-src/README.MAILINGLIST_RULESThu Jan 17 14:37:58 2008 @@ -71,6 +71,9 @@ create an entirely new thread copying anything you wish to quote into the new thread. +Finally, additional hints on how to behave inside the virtual community can be +found in RFC 1855 (http://www.faqs.org/rfcs/rfc1855.html). + Happy hacking, PHP Team -- PHP CVS Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
[PHP-CVS] cvs: php-src(PHP_5_3) / README.MAILINGLIST_RULES
lsmith Thu Jan 17 14:38:16 2008 UTC Modified files: (Branch: PHP_5_3) /php-srcREADME.MAILINGLIST_RULES Log: MFH http://cvs.php.net/viewvc.cgi/php-src/README.MAILINGLIST_RULES?r1=1.1.2.4r2=1.1.2.5diff_format=u Index: php-src/README.MAILINGLIST_RULES diff -u php-src/README.MAILINGLIST_RULES:1.1.2.4 php-src/README.MAILINGLIST_RULES:1.1.2.5 --- php-src/README.MAILINGLIST_RULES:1.1.2.4Fri Jan 11 14:02:12 2008 +++ php-src/README.MAILINGLIST_RULESThu Jan 17 14:38:16 2008 @@ -71,6 +71,9 @@ create an entirely new thread copying anything you wish to quote into the new thread. +Finally, additional hints on how to behave inside the virtual community can be +found in RFC 1855 (http://www.faqs.org/rfcs/rfc1855.html). + Happy hacking, PHP Team -- PHP CVS Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
[PHP-CVS] cvs: php-src(PHP_5_3) / README.MAILINGLIST_RULES
lsmith Fri Jan 11 09:40:43 2008 UTC Added files: (Branch: PHP_5_3) /php-srcREADME.MAILINGLIST_RULES Log: MFH http://cvs.php.net/viewvc.cgi/php-src/README.MAILINGLIST_RULES?view=markuprev=1.1 Index: php-src/README.MAILINGLIST_RULES +++ php-src/README.MAILINGLIST_RULES Mailinglist Rules This is the first file you should be reading before doing any posts on PHP mailinglists. Not following these rules is considered imparative to the sucess of the PHP project. Therefore expect your contributions to be of much less positive impact if you do not follow these rules. More importantly you can actually assume that not following these rules will hurt the PHP project. PHP is developed through the efforts of a large number of people. Collaboration is a Good Thing(tm), and mailinglists lets us do this. Thus, following some basic rules with regards to mailinglist usage will: a. Make everybody happier, especially those responsible for developing PHP itself. b. Help in making sure we all use our time more efficiently. c. Prevent you from making a fool of yourself in public. d. Increase the general level of good will on planet Earth. Having said that, here are the organizational rules: 1. Respect other people working on the project. 2. Do not post when you are angry. Any post can wait a few hours. Review your post after a good breather or a good nights sleep. 3. Make sure you pick the right mailinglist for your posting. Please review the descriptions on the mailinglist overview page (http://www.php.net/mailing-lists.php). When in doubt ask a friend or someone you trust on IRC. 4. Make sure you know what you are talking about. PHP is a very large project that strives to be very open. The flip side is that the core developers are faced with a lot of requests. Make sure that you have done your research before posting to the entire developer community. 5. Patches have a much greater chance of acceptance than just asking the PHP developers to implement a feature for you. For one it makes the discussion more concrete and it shows that the poster put thought and time into the request. 6. If you are posting to an existing thread, make sure that you know what previous posters have said. This is even more important the longer the thread is already. The next few rules are more some general hints: 1. If you notice that your posting ratio is much higher than that of other people, double check the above rules. Try to wait a bit longer before sending your replies to give other people more time to digest your answers and more importantly give you the opportunity to make sure that you aggregate your current position into a single mail instead of multiple ones. 2. Consider taking a step back from a very active thread now and then. Maybe talking to some friends and fellow developers will help in understanding the other opinions better. 3. Do not top post. Place your answer underneath anyone you wish to quote and remove any previous comment that is not relevant to your post. 4. Do not high-jack threads, by bringing up entirely new topics. Please create an entirely new thread copying anything you wish to quote into the new thread. Happy hacking, PHP Team -- PHP CVS Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
[PHP-CVS] cvs: php-src / README.MAILINGLIST_RULES
lsmith Fri Jan 11 09:40:20 2008 UTC Added files: /php-srcREADME.MAILINGLIST_RULES Log: - initial commit .. feedback appreciated http://cvs.php.net/viewvc.cgi/php-src/README.MAILINGLIST_RULES?view=markuprev=1.1 Index: php-src/README.MAILINGLIST_RULES +++ php-src/README.MAILINGLIST_RULES Mailinglist Rules This is the first file you should be reading before doing any posts on PHP mailinglists. Not following these rules is considered imparative to the sucess of the PHP project. Therefore expect your contributions to be of much less positive impact if you do not follow these rules. More importantly you can actually assume that not following these rules will hurt the PHP project. PHP is developed through the efforts of a large number of people. Collaboration is a Good Thing(tm), and mailinglists lets us do this. Thus, following some basic rules with regards to mailinglist usage will: a. Make everybody happier, especially those responsible for developing PHP itself. b. Help in making sure we all use our time more efficiently. c. Prevent you from making a fool of yourself in public. d. Increase the general level of good will on planet Earth. Having said that, here are the organizational rules: 1. Respect other people working on the project. 2. Do not post when you are angry. Any post can wait a few hours. Review your post after a good breather or a good nights sleep. 3. Make sure you pick the right mailinglist for your posting. Please review the descriptions on the mailinglist overview page (http://www.php.net/mailing-lists.php). When in doubt ask a friend or someone you trust on IRC. 4. Make sure you know what you are talking about. PHP is a very large project that strives to be very open. The flip side is that the core developers are faced with a lot of requests. Make sure that you have done your research before posting to the entire developer community. 5. Patches have a much greater chance of acceptance than just asking the PHP developers to implement a feature for you. For one it makes the discussion more concrete and it shows that the poster put thought and time into the request. 6. If you are posting to an existing thread, make sure that you know what previous posters have said. This is even more important the longer the thread is already. The next few rules are more some general hints: 1. If you notice that your posting ratio is much higher than that of other people, double check the above rules. Try to wait a bit longer before sending your replies to give other people more time to digest your answers and more importantly give you the opportunity to make sure that you aggregate your current position into a single mail instead of multiple ones. 2. Consider taking a step back from a very active thread now and then. Maybe talking to some friends and fellow developers will help in understanding the other opinions better. 3. Do not top post. Place your answer underneath anyone you wish to quote and remove any previous comment that is not relevant to your post. 4. Do not high-jack threads, by bringing up entirely new topics. Please create an entirely new thread copying anything you wish to quote into the new thread. Happy hacking, PHP Team -- PHP CVS Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
[PHP-CVS] cvs: php-src / README.MAILINGLIST_RULES
lsmith Fri Jan 11 10:49:01 2008 UTC Modified files: /php-srcREADME.MAILINGLIST_RULES Log: - minor typo fixes http://cvs.php.net/viewvc.cgi/php-src/README.MAILINGLIST_RULES?r1=1.1r2=1.2diff_format=u Index: php-src/README.MAILINGLIST_RULES diff -u php-src/README.MAILINGLIST_RULES:1.1 php-src/README.MAILINGLIST_RULES:1.2 --- php-src/README.MAILINGLIST_RULES:1.1Fri Jan 11 09:40:20 2008 +++ php-src/README.MAILINGLIST_RULESFri Jan 11 10:49:01 2008 @@ -3,10 +3,10 @@ This is the first file you should be reading before doing any posts on PHP -mailinglists. Not following these rules is considered imparative to the sucess -of the PHP project. Therefore expect your contributions to be of much less -positive impact if you do not follow these rules. More importantly you can -actually assume that not following these rules will hurt the PHP project. +mailinglists. Following these rules is considered imperative to the success of +the PHP project. Therefore expect your contributions to be of much less positive +impact if you do not follow these rules. More importantly you can actually +assume that not following these rules will hurt the PHP project. PHP is developed through the efforts of a large number of people. Collaboration is a Good Thing(tm), and mailinglists lets us do this. Thus, -- PHP CVS Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
[PHP-CVS] cvs: php-src(PHP_5_3) / README.MAILINGLIST_RULES
lsmith Fri Jan 11 10:49:15 2008 UTC Modified files: (Branch: PHP_5_3) /php-srcREADME.MAILINGLIST_RULES Log: MFH http://cvs.php.net/viewvc.cgi/php-src/README.MAILINGLIST_RULES?r1=1.1.2.2r2=1.1.2.3diff_format=u Index: php-src/README.MAILINGLIST_RULES diff -u php-src/README.MAILINGLIST_RULES:1.1.2.2 php-src/README.MAILINGLIST_RULES:1.1.2.3 --- php-src/README.MAILINGLIST_RULES:1.1.2.2Fri Jan 11 09:40:43 2008 +++ php-src/README.MAILINGLIST_RULESFri Jan 11 10:49:15 2008 @@ -3,10 +3,10 @@ This is the first file you should be reading before doing any posts on PHP -mailinglists. Not following these rules is considered imparative to the sucess -of the PHP project. Therefore expect your contributions to be of much less -positive impact if you do not follow these rules. More importantly you can -actually assume that not following these rules will hurt the PHP project. +mailinglists. Following these rules is considered imperative to the success of +the PHP project. Therefore expect your contributions to be of much less positive +impact if you do not follow these rules. More importantly you can actually +assume that not following these rules will hurt the PHP project. PHP is developed through the efforts of a large number of people. Collaboration is a Good Thing(tm), and mailinglists lets us do this. Thus, -- PHP CVS Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
[PHP-CVS] cvs: php-src(PHP_5_3) / README.MAILINGLIST_RULES
lsmith Fri Jan 11 14:02:12 2008 UTC Modified files: (Branch: PHP_5_3) /php-srcREADME.MAILINGLIST_RULES Log: MFH http://cvs.php.net/viewvc.cgi/php-src/README.MAILINGLIST_RULES?r1=1.1.2.3r2=1.1.2.4diff_format=u Index: php-src/README.MAILINGLIST_RULES diff -u php-src/README.MAILINGLIST_RULES:1.1.2.3 php-src/README.MAILINGLIST_RULES:1.1.2.4 --- php-src/README.MAILINGLIST_RULES:1.1.2.3Fri Jan 11 10:49:15 2008 +++ php-src/README.MAILINGLIST_RULESFri Jan 11 14:02:12 2008 @@ -48,6 +48,8 @@ previous posters have said. This is even more important the longer the thread is already. + 7. Please configure your email client to use a real name and keep message + signatures to a maximum of 2 lines if at all necessary. The next few rules are more some general hints: -- PHP CVS Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
[PHP-CVS] cvs: php-src / README.MAILINGLIST_RULES
lsmith Fri Jan 11 14:01:52 2008 UTC Modified files: /php-srcREADME.MAILINGLIST_RULES Log: - added rules about real names and signatures http://cvs.php.net/viewvc.cgi/php-src/README.MAILINGLIST_RULES?r1=1.2r2=1.3diff_format=u Index: php-src/README.MAILINGLIST_RULES diff -u php-src/README.MAILINGLIST_RULES:1.2 php-src/README.MAILINGLIST_RULES:1.3 --- php-src/README.MAILINGLIST_RULES:1.2Fri Jan 11 10:49:01 2008 +++ php-src/README.MAILINGLIST_RULESFri Jan 11 14:01:52 2008 @@ -48,6 +48,8 @@ previous posters have said. This is even more important the longer the thread is already. + 7. Please configure your email client to use a real name and keep message + signatures to a maximum of 2 lines if at all necessary. The next few rules are more some general hints: -- PHP CVS Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
[PHP-CVS] cvs: php-src / README.CVS-RULES
lsmith Sat Nov 24 13:52:19 2007 UTC Modified files: /php-srcREADME.CVS-RULES Log: - 5.2 is only for bug fixes - emphasis should be made with enclosing with ** and not with _ http://cvs.php.net/viewvc.cgi/php-src/README.CVS-RULES?r1=1.22r2=1.23diff_format=u Index: php-src/README.CVS-RULES diff -u php-src/README.CVS-RULES:1.22 php-src/README.CVS-RULES:1.23 --- php-src/README.CVS-RULES:1.22 Thu Nov 22 18:12:07 2007 +++ php-src/README.CVS-RULESSat Nov 24 13:52:19 2007 @@ -48,9 +48,8 @@ PHP_5_3 Is used to release the PHP 5.3.x series. It still allows for larger enhancements. - PHP_5_2 Is used to release the PHP 5.2.x series. Only minor feature - enhancements may go in here, but please keep that as infrequent as - possible. + PHP_5_2 Is used to release the PHP 5.2.x series. Only bugfixes are permitted + on this branch (Consult the releasemaster prior to commit). PHP_5_1 This branch is closed. @@ -95,7 +94,7 @@ in the ChangeLog. Everything else goes into the ChangeLog. It is important to note that if your comment or news logline spans multiple -lines, you have to put # at the beginning of _every_ such line. +lines, you have to put # at the beginning of **every** such line. Example. Say you modified two files, datetime.c and string.c. In datetime.c you added a new format option for the date() function, and in string.c you fixed a -- PHP CVS Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
[PHP-CVS] cvs: php-src(PHP_5_3) / README.CVS-RULES
lsmith Sat Nov 24 13:52:29 2007 UTC Modified files: (Branch: PHP_5_3) /php-srcREADME.CVS-RULES Log: - MFH http://cvs.php.net/viewvc.cgi/php-src/README.CVS-RULES?r1=1.18.2.1.2.2.2.1r2=1.18.2.1.2.2.2.2diff_format=u Index: php-src/README.CVS-RULES diff -u php-src/README.CVS-RULES:1.18.2.1.2.2.2.1 php-src/README.CVS-RULES:1.18.2.1.2.2.2.2 --- php-src/README.CVS-RULES:1.18.2.1.2.2.2.1 Thu Nov 22 18:13:05 2007 +++ php-src/README.CVS-RULESSat Nov 24 13:52:29 2007 @@ -48,9 +48,8 @@ PHP_5_3 Is used to release the PHP 5.3.x series. It still allows for larger enhancements. - PHP_5_2 Is used to release the PHP 5.2.x series. Only minor feature - enhancements may go in here, but please keep that as infrequent as - possible. + PHP_5_2 Is used to release the PHP 5.2.x series. Only bugfixes are permitted + on this branch (Consult the releasemaster prior to commit). PHP_5_1 This branch is closed. @@ -95,7 +94,7 @@ in the ChangeLog. Everything else goes into the ChangeLog. It is important to note that if your comment or news logline spans multiple -lines, you have to put # at the beginning of _every_ such line. +lines, you have to put # at the beginning of **every** such line. Example. Say you modified two files, datetime.c and string.c. In datetime.c you added a new format option for the date() function, and in string.c you fixed a -- PHP CVS Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
[PHP-CVS] cvs: php-src(PHP_5_3) / CODING_STANDARDS
lsmith Sat Nov 24 13:55:27 2007 UTC Modified files: (Branch: PHP_5_3) /php-srcCODING_STANDARDS Log: - MFH http://cvs.php.net/viewvc.cgi/php-src/CODING_STANDARDS?r1=1.32.4.3.2.1.2.2r2=1.32.4.3.2.1.2.3diff_format=u Index: php-src/CODING_STANDARDS diff -u php-src/CODING_STANDARDS:1.32.4.3.2.1.2.2 php-src/CODING_STANDARDS:1.32.4.3.2.1.2.3 --- php-src/CODING_STANDARDS:1.32.4.3.2.1.2.2 Sun Nov 11 22:12:06 2007 +++ php-src/CODING_STANDARDSSat Nov 24 13:55:27 2007 @@ -16,7 +16,7 @@ 1. Functions that are given pointers to resources should not free them -For instance, function int mail(char *to, char *from) should NOT free +For instance, ``function int mail(char *to, char *from)`` should NOT free to and/or from. Exceptions: -- 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
[PHP-CVS] cvs: php-src(PHP_5_3) / README.RELEASE_PROCESS
lsmith Thu Nov 22 08:59:05 2007 UTC Added files: (Branch: PHP_5_3) /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
[PHP-CVS] cvs: php-src / README.CVS-RULES
lsmith Thu Nov 22 18:12:07 2007 UTC Modified files: /php-srcREADME.CVS-RULES Log: - adapted to reST format - added 5_3 branch - added note about getting confirmation from RM on significant changes http://cvs.php.net/viewvc.cgi/php-src/README.CVS-RULES?r1=1.21r2=1.22diff_format=u Index: php-src/README.CVS-RULES diff -u php-src/README.CVS-RULES:1.21 php-src/README.CVS-RULES:1.22 --- php-src/README.CVS-RULES:1.21 Thu Jul 12 23:44:30 2007 +++ php-src/README.CVS-RULESThu Nov 22 18:12:07 2007 @@ -1,24 +1,31 @@ + + CVS Commit Rules + + This is the first file you should be reading after you get your CVS account. We'll assume you're basically familiar with CVS, but feel free to post -your questions on the mailing list. Please have a look at +your questions on the mailing list. Please have a look at http://cvsbook.red-bean.com/ for more detailed information on CVS. PHP is developed through the efforts of a large number of people. Collaboration is a Good Thing(tm), and CVS lets us do this. Thus, following -some basic rules with regards to CVS usage will: +some basic rules with regards to CVS usage will:: a. Make everybody happier, especially those responsible for maintaining the CVS itself. + b. Keep the changes consistently well documented and easily trackable. + c. Prevent some of those 'Oops' moments. - d. Increase the general level of good will on planet Earth. + d. Increase the general level of good will on planet Earth. -Having said that, here are the organizational rules: +Having said that, here are the organizational rules:: 1. Respect other people working on the project. - 2. Discuss any significant changes on the list before committing. + 2. Discuss any significant changes on the list before committing and get + confirmation from the release manager for the given branch. 3. Look at EXTENSIONS file to see who is the primary maintainer of the code you want to contribute to. @@ -30,30 +37,38 @@ 6. Test your changes before committing them. We mean it. Really. To do so use make test. - + 7. For development use the --enable-maintainer-zts switch to ensure your code handles TSRM correctly and doesn't break for thos who need that. -Currently we have the following branches in use: -HEAD Will become PHP 6.0. This CVS branch is for active development. -PHP_5_2 Is used to release the PHP 5.2.x series. Only minor feature - enhancements may go in here, but please keep that as infrequent as - possible. -PHP_5_1 This branch is closed. -PHP_4_4 Is used to release the PHP 4.4.x series. Only bugfixes are permitted - on this branch (Consult the releasemaster prior to commit). -PHP_4_3 This branch is closed. +Currently we have the following branches in use:: + + HEAD Will become PHP 6.0. This CVS branch is for active development. + + PHP_5_3 Is used to release the PHP 5.3.x series. It still allows for + larger enhancements. -The next few rules are more of a technical nature. + PHP_5_2 Is used to release the PHP 5.2.x series. Only minor feature + enhancements may go in here, but please keep that as infrequent as + possible. + + PHP_5_1 This branch is closed. + + PHP_4_4 Is used to release the PHP 4.4.x series. Only bugfixes are permitted + on this branch (Consult the releasemaster prior to commit). + + PHP_4_3 This branch is closed. + +The next few rules are more of a technical nature:: 1. DO NOT TOUCH ChangeLog! It is automagically updated from the commit messages every day. Woe be to those who attempt to mess with it. 2. All news updates intended for public viewing, such as new features, - bug fixes, improvements, etc., should go into the NEWS file. - + bug fixes, improvements, etc., should go into the NEWS file. + NB! Lines, starting with @ will go automagically into NEWS file, but - this is NOT recommended, though. Please, add news entries directly to + this is NOT recommended, though. Please, add news entries directly to NEWS file and don't forget to keep them adjusted and sorted. 3. Do not commit multiple file and dump all messages in one commit. If you @@ -80,7 +95,7 @@ in the ChangeLog. Everything else goes into the ChangeLog. It is important to note that if your comment or news logline spans multiple -lines, you have to put # at the beginning of _every_ such line. +lines, you have to put # at the beginning of _every_ such line. Example. Say you modified two files, datetime.c and string.c. In datetime.c you added a new format option for the date() function, and in string.c you fixed a @@ -88,13 +103,15 @@ separately and try to make sure your commit messages look something like the following. -For datetime.c: -- Added new 'K' format modifier to date() for
[PHP-CVS] cvs: php-src / CODING_STANDARDS
lsmith Sun Nov 11 16:29:54 2007 UTC Modified files: /php-srcCODING_STANDARDS Log: - migrate syntax to rEST to allow html/docbook rendering http://cvs.php.net/viewvc.cgi/php-src/CODING_STANDARDS?r1=1.36r2=1.37diff_format=u Index: php-src/CODING_STANDARDS diff -u php-src/CODING_STANDARDS:1.36 php-src/CODING_STANDARDS:1.37 --- php-src/CODING_STANDARDS:1.36 Thu Dec 22 20:27:03 2005 +++ php-src/CODING_STANDARDSSun Nov 11 16:29:54 2007 @@ -1,6 +1,6 @@ -PHP Coding Standards - - + + PHP Coding Standards + This file lists several standards that any programmer, adding or changing code in PHP, should follow. Since this file was added at a very late @@ -9,37 +9,38 @@ well into the version 4 releases, many sections have been recoded to use these rules. - Code Implementation --- -[0] Document your code in source files and the manual. [tm] +0. Document your code in source files and the manual. [tm] -[1] Functions that are given pointers to resources should not free them +1. Functions that are given pointers to resources should not free them For instance, function int mail(char *to, char *from) should NOT free to and/or from. Exceptions: - - The function's designated behavior is freeing that resource. E.g. efree() - - The function is given a boolean argument, that controls whether or not -the function may free its arguments (if true - the function must free its -arguments, if false - it must not) - - Low-level parser routines, that are tightly integrated with the token -cache and the bison code for minimum memory copying overhead. - -[2] Functions that are tightly integrated with other functions within the +- The function's designated behavior is freeing that resource. E.g. efree() + +- The function is given a boolean argument, that controls whether or not + the function may free its arguments (if true - the function must free its + arguments, if false - it must not) + +- Low-level parser routines, that are tightly integrated with the token + cache and the bison code for minimum memory copying overhead. + +2. Functions that are tightly integrated with other functions within the same module, and rely on each other non-trivial behavior, should be documented as such and declared 'static'. They should be avoided if possible. -[3] Use definitions and macros whenever possible, so that constants have +3. Use definitions and macros whenever possible, so that constants have meaningful names and can be easily manipulated. The only exceptions to this rule are 0 and 1, when used as false and true (respectively). Any other use of a numeric constant to specify different behavior or actions should be done through a #define. -[4] When writing functions that deal with strings, be sure to remember +4. When writing functions that deal with strings, be sure to remember that PHP holds the length property of each string, and that it shouldn't be calculated with strlen(). Write your functions in a such a way so that they'll take advantage of the length property, both @@ -48,47 +49,47 @@ doing so, should return that new length, so it doesn't have to be recalculated with strlen() (e.g. php_addslashes()) -[5] NEVER USE strncat(). If you're absolutely sure you know what you're doing, +5. NEVER USE strncat(). If you're absolutely sure you know what you're doing, check its man page again, and only then, consider using it, and even then, try avoiding it. -[6] Use PHP_* macros in the PHP source, and ZEND_* macros in the Zend -part of the source. Although the PHP_* macro's are mostly aliased to the -ZEND_* macros it gives a better understanding on what kind of macro you're -calling. +6. Use ``PHP_*`` macros in the PHP source, and ``ZEND_*`` macros in the Zend +part of the source. Although the ``PHP_*`` macro's are mostly aliased to the +``ZEND_*`` macros it gives a better understanding on what kind of macro +you're calling. -[7] When commenting out code using a #if statement, do NOT use 0 only. Instead +7. When commenting out code using a #if statement, do NOT use 0 only. Instead use cvs username here_0. For example, #if FOO_0, where FOO is your -cvs user foo. This allows easier tracking of why code was commented out, -especially in bundled libraries. +cvs user foo. This allows easier tracking of why code was commented out, +especially in bundled libraries. -[8] Do not define functions that are not available. For instance, if a - library is missing a function, do not define the PHP version of the - function, and do not raise a run-time error about the function not - existing. End users should use function_exists() to test for the - existence of a function - -[9] Prefer emalloc(), efree(), estrdup(), etc. to their
[PHP-CVS] cvs: php-src(PHP_5_3) / CODING_STANDARDS
lsmith Sun Nov 11 16:30:35 2007 UTC Modified files: (Branch: PHP_5_3) /php-srcCODING_STANDARDS Log: - MFH http://cvs.php.net/viewvc.cgi/php-src/CODING_STANDARDS?r1=1.32.4.3.2.1r2=1.32.4.3.2.1.2.1diff_format=u Index: php-src/CODING_STANDARDS diff -u php-src/CODING_STANDARDS:1.32.4.3.2.1 php-src/CODING_STANDARDS:1.32.4.3.2.1.2.1 --- php-src/CODING_STANDARDS:1.32.4.3.2.1 Wed Jul 18 23:10:33 2007 +++ php-src/CODING_STANDARDSSun Nov 11 16:30:35 2007 @@ -1,6 +1,6 @@ -PHP Coding Standards - - + + PHP Coding Standards + This file lists several standards that any programmer, adding or changing code in PHP, should follow. Since this file was added at a very late @@ -9,37 +9,38 @@ well into the version 4 releases, many sections have been recoded to use these rules. - Code Implementation --- -[0] Document your code in source files and the manual. [tm] +0. Document your code in source files and the manual. [tm] -[1] Functions that are given pointers to resources should not free them +1. Functions that are given pointers to resources should not free them For instance, function int mail(char *to, char *from) should NOT free to and/or from. Exceptions: - - The function's designated behavior is freeing that resource. E.g. efree() - - The function is given a boolean argument, that controls whether or not -the function may free its arguments (if true - the function must free its -arguments, if false - it must not) - - Low-level parser routines, that are tightly integrated with the token -cache and the bison code for minimum memory copying overhead. - -[2] Functions that are tightly integrated with other functions within the +- The function's designated behavior is freeing that resource. E.g. efree() + +- The function is given a boolean argument, that controls whether or not + the function may free its arguments (if true - the function must free its + arguments, if false - it must not) + +- Low-level parser routines, that are tightly integrated with the token + cache and the bison code for minimum memory copying overhead. + +2. Functions that are tightly integrated with other functions within the same module, and rely on each other non-trivial behavior, should be documented as such and declared 'static'. They should be avoided if possible. -[3] Use definitions and macros whenever possible, so that constants have +3. Use definitions and macros whenever possible, so that constants have meaningful names and can be easily manipulated. The only exceptions to this rule are 0 and 1, when used as false and true (respectively). Any other use of a numeric constant to specify different behavior or actions should be done through a #define. -[4] When writing functions that deal with strings, be sure to remember +4. When writing functions that deal with strings, be sure to remember that PHP holds the length property of each string, and that it shouldn't be calculated with strlen(). Write your functions in a such a way so that they'll take advantage of the length property, both @@ -48,47 +49,47 @@ doing so, should return that new length, so it doesn't have to be recalculated with strlen() (e.g. php_addslashes()) -[5] NEVER USE strncat(). If you're absolutely sure you know what you're doing, +5. NEVER USE strncat(). If you're absolutely sure you know what you're doing, check its man page again, and only then, consider using it, and even then, try avoiding it. -[6] Use PHP_* macros in the PHP source, and ZEND_* macros in the Zend -part of the source. Although the PHP_* macro's are mostly aliased to the -ZEND_* macros it gives a better understanding on what kind of macro you're -calling. +6. Use ``PHP_*`` macros in the PHP source, and ``ZEND_*`` macros in the Zend +part of the source. Although the ``PHP_*`` macro's are mostly aliased to the +``ZEND_*`` macros it gives a better understanding on what kind of macro +you're calling. -[7] When commenting out code using a #if statement, do NOT use 0 only. Instead +7. When commenting out code using a #if statement, do NOT use 0 only. Instead use cvs username here_0. For example, #if FOO_0, where FOO is your -cvs user foo. This allows easier tracking of why code was commented out, -especially in bundled libraries. +cvs user foo. This allows easier tracking of why code was commented out, +especially in bundled libraries. -[8] Do not define functions that are not available. For instance, if a - library is missing a function, do not define the PHP version of the - function, and do not raise a run-time error about the function not - existing. End users should use function_exists() to test for the - existence of a function - -[9] Prefer emalloc(), efree(),
[PHP-CVS] cvs: php-src(PHP_5_3) / CODING_STANDARDS
lsmith Sun Nov 11 22:12:06 2007 UTC Modified files: (Branch: PHP_5_3) /php-srcCODING_STANDARDS Log: - MFH typo fix by Jon http://cvs.php.net/viewvc.cgi/php-src/CODING_STANDARDS?r1=1.32.4.3.2.1.2.1r2=1.32.4.3.2.1.2.2diff_format=u Index: php-src/CODING_STANDARDS diff -u php-src/CODING_STANDARDS:1.32.4.3.2.1.2.1 php-src/CODING_STANDARDS:1.32.4.3.2.1.2.2 --- php-src/CODING_STANDARDS:1.32.4.3.2.1.2.1 Sun Nov 11 16:30:35 2007 +++ php-src/CODING_STANDARDSSun Nov 11 22:12:06 2007 @@ -181,9 +181,9 @@ of PHP or one of its standard modules, please maintain the KR style. This applies to just about everything, starting with indentation and comment styles and up to function declaration -syntax. Also see Identstyle_. +syntax. Also see Indentstyle_. -.. _Identstyle: http://www.catb.org/~esr/jargon/html/I/indent-style.html +.. _Indentstyle: http://www.catb.org/~esr/jargon/html/I/indent-style.html 3. Be generous with whitespace and braces. Keep one empty line between the variable declaration section and the statements in a block, as well as -- PHP CVS Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
