PHP Wiki

cvs2svnconversion

Anonymous (anonymous@undisclosed.example.com) — 2025-04-03T13:08:43+00:00

2017/09/22 13:28		current
Line 389:		Line 389:
	</code>		</code>

-	Whew. That was going to make for a //very// long options file where it was very easy to make copypasta errors. I needed to add a little Python code. How does one do foreach (array(//blah blah blah//) as $item) { /* etc / } in Python? So I went to my wife Sarah,* who does know Python.	+	Whew. That was going to make for a //very// long options file where it was very easy to make copypasta errors. I needed to add a little Python code. How does one do foreach (array(//blah blah blah//) as $item) { /* etc / } in Python? So I went to a close friend* who does know Python.

	We came up with this rather handy little bit of code:		We came up with this rather handy little bit of code:

firefighting

Anonymous (anonymous@undisclosed.example.com) — 2025-04-03T13:08:43+00:00

2009/07/13 04:08		current
Line 13:		Line 13:
	* The daily "[[http://darkrainfall.org/changelog.tar.gz\|changelog]]" script needs to be updated to use SVN		* The daily "[[http://darkrainfall.org/changelog.tar.gz\|changelog]]" script needs to be updated to use SVN
	* README files still reference CVS: README.CVS-RULES, README.QNX, README.RELEASE_PROCESS, README.SUBMITTING_PATCH (hradtke)		* README files still reference CVS: README.CVS-RULES, README.QNX, README.RELEASE_PROCESS, README.SUBMITTING_PATCH (hradtke)
		+
	===== bugs.php.net =====		===== bugs.php.net =====
	* Uses a local copy of CVSROOT/passwd for authentication. Needs to use the API on master. (Jani)		* Uses a local copy of CVSROOT/passwd for authentication. Needs to use the API on master. (Jani)
Line 32:		Line 33:
	===== oti1.php.net =====		===== oti1.php.net =====
	* This windows box (chm builder) needs to be upgraded to use SVN rather then CVS		* This windows box (chm builder) needs to be upgraded to use SVN rather then CVS
		+
		+
		+	===== osu1.php.net ===== (master)
		+	* systems/ updated to use SVN checkout (bjori)
		+	* mirrors/php-master-web/ updated to use SVN checkout (bjori)
		+	* Can't find other CVS checkouts, should be fine now
		+

bug_triage

Anonymous (anonymous@undisclosed.example.com) — 2025-04-03T13:08:43+00:00

2009/03/11 02:10		current
Line 114:		Line 114:
	* [[pear:qa:bug triage:2009-01-17]]		* [[pear:qa:bug triage:2009-01-17]]
	* [[pear:qa:bug triage:2009-02-07]]		* [[pear:qa:bug triage:2009-02-07]]
		+	* [[pear:qa:bug triage:2009-03-21]]

faq

Anonymous (anonymous@undisclosed.example.com) — 2025-04-03T13:08:43+00:00

2026/04/23 10:37	current
Line 1:	Line 1:
	+	==== So, How exactly do I get the source files for the PHP Manual? ====
	+	Simple. The PHP Project uses CVS to manage its sources, so to retrieve the sources for the PHP Manual you will checkout (download) these sources from CVS. An anonymous CVS user named //cvsread// exists (password: //phpfi//) that anybody in the world may use to make checkouts. For example:
	+
	+	<code>
	+	$ cvs -d :pserver:cvsread@cvs.php.net:/repository login
	+	$ cvs -d :pserver:cvsread@cvs.php.net:/repository checkout phpdoc
	+	</code>
	+
	+	The above assumes you have CVS installed. Odds are if you're using Linux or Mac that this is already installed, but Windows users aren't so lucky (or unlucky, depending on your feelings towards CVS!) The simplest method for Windows users is TortoiseCVS, see the FAQ for that.
	+
	+	There will now exist a directory named //phpdoc// that houses all sources files for the PHP Manual.
	+
	+	==== I use Windows, and heard something about TortoirseCVS... should I use it? ====
	+	Sure, it's simple and offers a friendly GUI so if you're into that then go for it! And besides, it also installs the cvs command so it may be used in your Terminal too. The steps include:
	+
	+	* Install [[http://www.tortoisecvs.org/\|TortoirseCVS]]
	+	* Open a new explorer window and go to the folder you wish to do a checkout in (store CVS files)
	+	* Right click anywhere in the blank area to spawn the context menu, select "CVS Checkout"
	+	* A new window will popup and ask for details about the checkout; these values will be remembered so will be entered just once
	+	* Enter the following:
	+	* CVSROOT: ":pserver:cvsread@cvs.php.net:/repository"
	+	* Module field: "phpdoc"
	+	* Press OK to begin the checkout. If you're prompted to enter a password while checking out, then type in "phpfi" and OK
	+	* When the checkout is complete, then it should have created a directory called "phpdoc" where the english php documentation source tree will be
	+
	+	==== I was told to create a patch, how do I do that? ====
	+	== New Files ==
	+	== Current Files ==
	+
	+	==== How do I know if my changes are good and valid? ====
	+	* Whitespace
	+	* Read diff
	+	* php configure.php
	+	* Describe when editing manual.xml.in is needed
	+	* PhD
	+
	+	==== Is there an online editor? ====
	+	* Yes and No

testfesttalk

Anonymous (anonymous@undisclosed.example.com) — 2025-04-03T13:08:43+00:00

2011/04/06 10:59		current
Line 1:		Line 1:
	====== PHPT roundup talk ======		====== PHPT roundup talk ======
-	This wikipage contains all extra information for the talk prepared for phptestfest 2009. They heavily rely on content written by other people before. Every resource of the talk, even the slides (in different formats) will be in this place. Other testfesters can use and modify this talk to save precious time.	+	This wikipage contains all extra information for the talk prepared for [[qa:testfest-2009\|phptestfest 2009]]. They heavily rely on content written by other people before. Every resource of the talk, even the slides (in different formats) will be in this place. Other testfesters can use and modify this talk to save precious time.

	[[http://tinyurl.com/c9bqf4]]		[[http://tinyurl.com/c9bqf4]]

phpvcs

Anonymous (anonymous@undisclosed.example.com) — 2025-04-03T13:08:43+00:00

2008/11/13 13:27		current
Line 4:		Line 4:
	* Date: 2008-03-29		* Date: 2008-03-29
	* Author: Gwynne Raskind		* Author: Gwynne Raskind
-	* Status: In the works	+	* Status: Accepted
-	* **Votes: (+0/-0)**	+	* **Progress: Roughly 90% implemented, see [[http://svn.php.net/]]**
-	* **Pro:**	+	* **Votes: While most people prefer a move to Git/Github, a more unanimous desire is required before such a large shift. We're sticking with the status quo and moving to SVN. A git bridge will exist.**
-	* Contra:****	+
	==== Purpose ====		==== Purpose ====

Line 92:		Line 92:

	==== Further Discussion And Reading ====		==== Further Discussion And Reading ====
		+	[[http://news.php.net/svn.migration]]
		+
	[[http://doc.php.net/php/rfc/rfc-proposal-show.php?id=8]]		[[http://doc.php.net/php/rfc/rfc-proposal-show.php?id=8]]

2008-10-25

Anonymous (anonymous@undisclosed.example.com) — 2025-04-03T13:08:43+00:00

2026/04/23 10:37	current
Line 1:	Line 1:
	+	====== Bug Triage Day October 25-26th 2008 ======
	+
	+	===== Who's running it? =====
	+	(on auto-pilot)
	+
	+	===== When =====
	+	October 25th, 26th in #pear-bugs on irc.efnet.org
	+
	+	See [[http://www.google.com/calendar/embed?src=rslkppoio4rtq6nm7b6fptclfo%40group.calendar.google.com]]
	+
	+	===== Attendees =====
	+	* cweiske
	+	* doconnor
	+	* kguest
	+	* amir
	+	* justinpatrin
	+	* till
	+	* avb
	+	* Tatsuya Tsuruoka
	+
	+
	+	===== What are we doing =====
	+	* Followup on [[http://pear.php.net/bugs/search.php?cmd=display&search_for=PHPCS&php_os=&boolean=0&bug_type=&bug_age=0&bug_updated=0&order_by=ts1&direction=DESC&packagever=&phpver=&limit=30&handle=&assign=&maintain=&showmenu=1&showmenu=1&status=Open\|PHPCS patches]]
	+	* <del>Validate</del> (amir)
	+	* <del>HTTP_Session2</del> (till)
	+	* <del>Gtk2_PHPConfig</del> (kguest)
	+	* <del>Net_Wifi</del> (cweiske)
	+	* <del>File_XSPF</del> (doconnor)
	+	* <del>Net_Whois</del> (doconnor)
	+
	+	* Followup on [[http://pear.php.net/bugs/search.php?cmd=display&search_for=PHPUnit&php_os=&boolean=0&bug_type=&bug_age=0&bug_updated=0&order_by=ts1&direction=DESC&packagever=&phpver=&limit=30&handle=&assign=&maintain=&showmenu=1&showmenu=1&status=Open\|PHPUnit patches]]
	+	* Make tests pass:
	+	* <del>Text_Wiki</del> (justinpatrin)
	+	* <del>Services_Amazon</del> (Tatsuya Tsuruoka)
	+	* <del>File_Find</del> (doconnor)
	+	* <del>Triage the [[http://pear.php.net/bugs/search.php?search_for=&boolean=0&limit=70&order_by=id&direction=DESC&cmd=display&status=Open&bug_type=All&php_os=&packagever=&phpver=&assign=&maintain=&author_email=&bug_age=0&bug_updated=0\|latest bugs]]</del> (doconnor: done-ish)
	+	* <del>HTTP_Client 1.2.1</del> released (avb)
	+	* <del>File_XSPF missing package.xml</del> (kguest)
	+	* <del>MDB2_Schema test coverage</del> (Igor Feghali)
	+
	+	==== Other items needing volunteers ====
	+	* writing tests for MDB2_Schema bugs (particularly those with patches);
	+	* <del>I18N_UnicodeString needs to be put in CVS (http://news.php.net/php.pear.dev/50419) (in CVS and fixed by kguest)</del>
	+	* <del>PHP_Fork into CVS</del> (cweiske)
	+	* Packages that have the most open bug reports (http://pear.php.net/bugs/stats.php)
	+	* <del>Apply Net_Ping patch for bug #14492</del> (patch by [[shupp]], applied by kguest)
	+	* Docs for Validate packages - ([[amir]] ?)
	+	* Payment_DTA into CVS (doconnor consulting with lead)
	+	* <del>Fix Validate_AU unit tests</del> (doconnor was shirking, but Validate_AU-0.1.2 now exists)
	+
	+	==== Notes: The best way to write unit tests for CVS ====
	+	Say you have a package, Foo_Bar_Item
	+
	+	If you structure you package as:
	+
	+	CVS dir:
	+	<code>/Foo_Bar_Item/</code>
	+
	+	Structure:
	+	<code>/Foo_Bar_Item/Foo/Bar/Item.php
	+	/Foo_Bar_Item/tests/AllTests.php</code>
	+
	+	Then it makes doing
	+	<code>
	+	you@locahost:~/pear$ cvs update
	+	you@locahost:~/pear$ cd Foo_Bar_Item
	+	you@locahost:~/pear/Foo_Bar_Item$ phpunit tests/
	+	</code>
	+	... work just fine with the existing require_once patterns; and when you install the package, the tests should still run.
	+
	+	Otherwise, if you have packages with different structure, you will often have to:
	+
	+	<code>
	+	you@locahost:~/pear$ cvs update
	+	you@locahost:~/pear$ cd Foo_Bar_Item
	+	you@locahost:~/pear/Foo_Bar_Item$ pear package
	+	you@locahost:~/pear/Foo_Bar_Item$ sudo pear install -fa Foo_Bar_Item-0.1.0.tgz
	+	you@locahost:~/pear/Foo_Bar_Item$ phpunit tests/
	+	</code>
	+
	+	==== Unit test results ====
	+	These unit test results are generated overnight / on demand on doconnor's development copy; so may be somewhat overly passing at the moment :)
	+	* [[http://docs.google.com/Doc?id=acm3gmkf7hk_17dfbp7bsw\|Unit test results - Oct 23rd]] 518 / 3195 tests fail or error
	+	* Tests: 3197, Assertions: 20496, Failures: 398, Errors: 48, Incomplete: 86.
	+	* Tests: 3198, Assertions: 20496, Failures: 274, Errors: 48, Incomplete: 86.
	+
	+

better_benchmarks

Anonymous (anonymous@undisclosed.example.com) — 2025-04-03T13:08:43+00:00

2009/07/20 13:09		current
Line 208:		Line 208:
	* crypto-md5 (29.06.2009)		* crypto-md5 (29.06.2009)
	* richards (29.06.2009)		* richards (29.06.2009)
		+	* Crypto-AES

	===== Still unfinished =====		===== Still unfinished =====

updating-markup

Anonymous (anonymous@undisclosed.example.com) — 2025-04-03T13:08:43+00:00

2009/02/16 22:42		current
Line 1:		Line 1:
-	Updating PHP docs to the new markup	+	==== Updating PHP docs to the new markup ====

	Several PHP extensions have documentation for OO-style APIs which is written as if the documentation was a procedural API. A good example of this was ext/soap, but also ext/rar seems to be using the old markup too. So, I'm going to take this as my example. If you go to http://php.net/rar, and look over the methods of the Rar class, you can see they're documented just the same as the functions rar_close(), rar_entry_get(), etc. This isn't handy and makes the search less useful. There is a new variant of the DocBook markup which makes more sense for OO APIs, and it should be converted. This is basically a copy and paste job.		Several PHP extensions have documentation for OO-style APIs which is written as if the documentation was a procedural API. A good example of this was ext/soap, but also ext/rar seems to be using the old markup too. So, I'm going to take this as my example. If you go to http://php.net/rar, and look over the methods of the Rar class, you can see they're documented just the same as the functions rar_close(), rar_entry_get(), etc. This isn't handy and makes the search less useful. There is a new variant of the DocBook markup which makes more sense for OO APIs, and it should be converted. This is basically a copy and paste job.
Line 39:		Line 39:

	TODO: Describe fixing user notes.		TODO: Describe fixing user notes.
		+	TODO: Describe how to deal with old CVS history... links to old files should be in the commit message at least.

karma-ml

Anonymous (anonymous@undisclosed.example.com) — 2025-04-03T13:08:43+00:00

2026/04/23 10:37	current
Line 1:	Line 1:
	+	====== Request for Comments: Karma-based Mailing List ======
	+	* Version: 1.0
	+	* Date: 2008-11-07
	+	* Author: Davey Shafik <davey@php.net>
	+	* Status: Under Discussion
	+	* First Published at: http://wiki.php.net/rfc/karma-ml
	+
	+	===== Introduction =====
	+
	+	This RFC is to start a discussion on technical solutions to the noise:signal ratio on internals and other mailing lists.
	+
	+	==== The Problem ====
	+
	+	The problem with mailing lists is that they are a free for all, it doesn't matter who posts, everybody at every level gets to see the post.
	+
	+	In the real world, communications pass through a hierarchy of people, escalating as necessary, passing from person to person up the chain.
	+
	+	This means that, given enough time, any mailing list starts to have a large noise:signal ratio, at least for any given person's take on the list; they want to read what they want to read, and don't need to be distracted ignoring the stuff they don't want to read.
	+
	+	===== Solving the Problem =====
	+
	+	There is an unspoken — some what hap-hazard — hierarchy among the community, which with some thought, I believe, could be defined, refined and utilized to our advantage. As an example:
	+
	+	<code>
	+	- Active internals contributors with access to internals CVS (contributions of code and useful discussions)
	+	\
	+	- Active internals contributiors without access to internals CVS (patch submitters, useful discussions)
	+	\
	+	- Active non-internals, PHP contributions (docs, phpweb, PEAR)
	+	- Active community leaders
	+	- Active project leaders
	+	- Active linux distro maintainers
	+	\
	+	- General Users with a high understand
	+	\
	+	- Genernal users with little understanding (newbies)
	+	</code>
	+
	+	If we take each of these, and assign them a number:
	+
	+	<code>
	+	L1 - Active internals contributors with access to internals CVS (contributions of code and useful discussions)
	+	\
	+	L2 - Active internals contributiors without access to internals CVS (patch submitters, useful discussions)
	+	\
	+	L3 - Active non-internals, PHP contributions (docs, phpweb, PEAR)
	+	L3 - Active community leaders
	+	L3 - Active project leaders
	+	L3 - Active linux distro maintainers
	+	\
	+	L4 - General Users with a high understand
	+	\
	+	L5 - Genernal users with little understanding (newbies)
	+	</code>
	+
	+	Now, what if, at any level, you could only see (by default) 1 level below you (and all levels above you). For example: L1 can see L2, L2 can see L3 etc.
	+
	+	This immediately means that you only see stuff that might be relevant to you; however, as a community, we then lose the ability for newcomers to contribute good ideas; because they would start out with zero karma. To help solve this issue, we adjust karma based on responses:
	+
	+	==== Scenario ====
	+
	+	* A L3 user posts something of interest
	+	* A L2 user see's the post and replies, the reply is L2
	+	* This bumps the original post up to L2 as well, maintaining context
	+	* All L2 users can see the reply and the original thread
	+	* After a second (or more?) L2 response, an L1 see's the post now, and can then participate in the discussion if they choose
	+
	+	In this case, only the thread in question is bumped up, however given enough L2/L1 (weighted) direct responses over different threads, a L3 user can gain karma and eventually become a L2 user (and obviously this applies to anyone moving up the chain)
	+
	+	In this way, threads (and by this mechanism, users also) can organically make their way up the tree as they gain traction, are discussed at each level and moved up.
	+
	+	Furthermore, by not responding to threads, they will organically die, and never make their way up the tree to bother people.
	+
	+	I believe it would be possible to have a single mailing list that could span everything from internals right down to php-general, but this is probably not desired! It would however allow the users of a single list to, regardless of their experience in the tree, contribute without weighing down the list.
	+
	+	==== Features ====
	+
	+	Karma tree seeded by current "social" climate
	+	based on CVS access level, activity in a sliding timescale, community contributions etc
	+	Some manual work will be needed on this
	+	Weighted responses, a L2 responding to a L3, will move it to L2, but 2 L1's or 1 L2 and 1 L1 responding would move it to L1, for example.
	+	Adjustable threshold. Perhaps some magnanimous internals contributor likes to help out newbies, he can choose to see the whole tree, or perhaps just 3 levels down
	+	Championing — it should be possible for a user to champion someone to quickly move them up the ladder, for example a L2 can bring a L5 up to L3, so their peers can see stuff, this is bringing the user up, not the thread
	+	Continued tweaking of karma based on CVS access and contributions
	+	Personal filters, you can add users (of any level) from whom you would like to see threads, helping the movement of stuff up the tree, skipping levels
	+	In this way, we can, in some ways, automate the karma, and in someways advance it through our own choices; creating a hierarchy based on merit and trust.
	+
	+	==== Final Thoughts ====
	+
	+	* Some smart filtering, so that "You're an idiot" responses don't elevate a thread would be good
	+	* That, or just handle it biologically — Don't respond to people in negative ways
	+	* Implementing this as a ML (in terms of interaction) is likely the only way to get some of the higher internals folks using it, a web interface [for the messages] just won't fly
	+	* Personal filters would be handled at master.php.net or maybe a new web interface for this
	+
	+	==== Comments ====
	+
	+	(paraphrased)
	+
	+	* Greg Beaver: The only way to get the core contributors to use the system, is as a mailing list filter
	+	* Lukas Smith: The automatic management is pretty good, but more transparency is needed for users on how posts/users are being ranked

cvstosvnmigration

Anonymous (anonymous@undisclosed.example.com) — 2025-04-03T13:08:43+00:00

2008/07/26 16:45		current
Line 1:		Line 1:
	====== CVS to SVN Migration ======		====== CVS to SVN Migration ======

-	This page will collect all information about the CVS2SVN migration of PHP's cvs.php.net repositories.	+	This page will collect all information about the CVS2SVN migration of PHP's cvs.php.net repositories. Subversion currently seems like a very likely candidate as the future core VCS for PHP. The history has actually already been imported and now the main task is to port all the existing CVS dependent infrastructure.
		+
		+	Mailinglist:
		+	- http://news.php.net/svn.migration
		+
		+	IRC channel:
		+	- #php.svn (EFNet)

	Further information:		Further information:

per-release-minor

Anonymous (anonymous@undisclosed.example.com) — 2025-04-03T13:08:43+00:00

2026/04/23 10:37	current
Line 1:	Line 1:
	+	==== TODO for every minor (x.Y.0) release ====
	+
	+	== Migration guides ==
	+	Since PHP 5.1.0, every such release has included a migration appendix / upgrade guide. This involves the following:
	+
	+	* php-src/README.UPDATE_X_Y (Examples: [[http://cvs.php.net/viewvc.cgi/phpweb/README_UPGRADE_51.php?hideattic=0\|5.1]], [[http://cvs.php.net/viewvc.cgi/php-src/README.UPDATE_5_2?&pathrev=PHP_5_2\|5.2]])
	+	* phpdoc/appendix/migrationXY.xml (Examples: [[http://cvs.php.net/viewvc.cgi/phpdoc/en/appendices/migration51.xml?view=log\|5.2]], [[http://cvs.php.net/viewvc.cgi/phpdoc/en/appendices/migration52.xml?view=log\|5.2]])
	+
	+	Currently the internals team has created the README files, but this may change.
	+
	+	== Extension categories ==
	+	Some extensions may have been moved to PECL, became bundled, were re-categorized, etc. This information should be updated at this time, or at any time before:
	+	* The XML: [[http://cvs.php.net/viewvc.cgi/phpdoc/en/appendices/extensions.xml?view=log\|phpdoc/en/appendices/extensions.xml]]
	+	* The script that updates it: [[http://cvs.php.net/viewvc.cgi/phpdoc/scripts/extensions.xml.php?view=log\|phpdoc/scripts.extensions.xml.php]]
	+	NOTE: This information comes from the comments found within (on top of) every book.xml. Status, and Membership. The Purpose dictates how the extensions are categorized in the index/table of contents.

phdoe

Anonymous (anonymous@undisclosed.example.com) — 2025-04-03T13:08:43+00:00

2011/04/06 10:59		current
Line 9:		Line 9:
	* Mailing list: phpdoc@lists.php.net		* Mailing list: phpdoc@lists.php.net
	* Blog: [[http://mrkschan.blogspot.com/search/label/gsoc]]		* Blog: [[http://mrkschan.blogspot.com/search/label/gsoc]]
		+	* Live at: [[https://edit.php.net]]
	===== Abstract =====		===== Abstract =====
	Currently, the documentation work is synchronized by cvs. But still, there are potential conflicts due to redundant work. Besides, it's not that easy to share the works or even pipelining the works in a distributed environment. Therefore, a centralized environment is introduced.		Currently, the documentation work is synchronized by cvs. But still, there are potential conflicts due to redundant work. Besides, it's not that easy to share the works or even pipelining the works in a distributed environment. Therefore, a centralized environment is introduced.

translations

Anonymous (anonymous@undisclosed.example.com) — 2025-04-03T13:08:43+00:00

2008/12/23 05:31		current
Line 46:		Line 46:
	=== When we should know ===		=== When we should know ===
	The SVN conversion will be completed sometime in the first quarter of 2009, let's say March 1. We should have our system essentially in place by that time. A sequential move is possible too (Start using SVN numbers, then later gettext) but that wouldn't be ideal. However, given the size of our manual, it may be required.		The SVN conversion will be completed sometime in the first quarter of 2009, let's say March 1. We should have our system essentially in place by that time. A sequential move is possible too (Start using SVN numbers, then later gettext) but that wouldn't be ideal. However, given the size of our manual, it may be required.
		+
		+	=== Status update: May 20, 2009 ===
		+	So far I've (philip) am having success converting translations to po files using po4a. After additional tweaking the plan is to setup pootle and see what happens. We may use transifex instead so we'll see but the key is getting the po files going. The main alternative to po4a is xml2po but so far I like po4a so don't see a need to investigate xml2po much further.
		+
		+	* po4a manual: http://po4a.alioth.debian.org/man/man7/po4a.7.php
		+	* Command: po4a-gettextize -f docbook -m en/reference/strings/functions/strlen.xml -p strlen.po (creates a po file)
		+	* Command: po4a-translate -f docbook -m en/reference/strings/functions/strlen.xml -p foo.po (creates docbook file)
		+	* Command: po4a-gettextize -f docbook -m en/reference/strings/functions/strlen.xml -l ja/reference/strings/functions/strlen.xml -p foo.po (converts translation to po file)
		+
		+	So, the current plan:
		+	* Convert current translations to po files (progressing)
		+	* Setup pootle at translate.php.net
		+	* Profit

2008

Anonymous (anonymous@undisclosed.example.com) — 2025-04-03T13:08:43+00:00

2008/04/01 09:21		current
Line 210:		Line 210:

	You can get start by [[http://xdebug.org\|getting XDebug]] and trying it out. (See the [[http://xdebug.org/docs/profiler\|profiler]] section)		You can get start by [[http://xdebug.org\|getting XDebug]] and trying it out. (See the [[http://xdebug.org/docs/profiler\|profiler]] section)
		+
		+	====== Evalution summary ======
		+
		+	There's a summary of the GSoC mid-term evaluation survey results on http://schlueters.de/~johannes/GSoC-Survey/summary.ods

dvcs

Anonymous (anonymous@undisclosed.example.com) — 2025-04-03T13:08:43+00:00

2011/09/05 09:39		current
Line 3:		Line 3:
	* Date: 2011-07-30		* Date: 2011-07-30
	* Author: David Soria Parra <dsp at php dot net>		* Author: David Soria Parra <dsp at php dot net>
-	* Status: [[rfc:dvcs:vote\|Voting]] (Voting ends Sep 7, 2011 12:00 UTC)	+	* Status: Accepted with Option Git [[rfc:dvcs:vote\|Voting Results]] (Voting ended Sep 7, 2011 12:00 UTC)
	* First Published at: http://wiki.php.net/rfc/dvcs		* First Published at: http://wiki.php.net/rfc/dvcs

svnfaq

Anonymous (anonymous@undisclosed.example.com) — 2025-04-03T13:08:43+00:00

2017/09/22 13:28		current
Line 133:		Line 133:
	* You cannot checkout the entire repository on case-insensitive filesystem		* You cannot checkout the entire repository on case-insensitive filesystem
	===== Validating your account =====		===== Validating your account =====
-	To gain access to svn.php.net you have to "validate your SVN account". This is automatically done by logging into master (https://master.php.net/login.php), the wiki (http://wiki.php.net) or reply to bugs on bugsweb (http://bugs.php.net/) from the developer tab.	+	To gain access to svn.php.net you have to "validate your SVN account". This is automatically done by logging into main (https://main.php.net/login.php), the wiki (http://wiki.php.net) or reply to bugs on bugsweb (http://bugs.php.net/) from the developer tab.
	Your access credentials will be synchronized within 15minutes.		Your access credentials will be synchronized within 15minutes.

ideas

Anonymous (anonymous@undisclosed.example.com) — 2025-04-03T13:08:43+00:00

2011/04/06 10:59		current
Line 155:		Line 155:


-	===== New Mirror Management System =====
-	// Possible Mentor: [[danbrown@php.net\|Daniel P. Brown]] //
-
-	Our existing management system for the network of official mirrors worldwide has a few issues and areas for improvement. The present system is accessible via a browser-based web interface (using a php.net CVS account, and hosted on master.php.net), and provides the following services:
-
-	* Addition, deletion, and modification of DNS for official mirrors of the php.net site as a whole
-	* Automated checking of all mirrors, marking mirrors as "disabled" when issues are detected
-	* Listing of all mirrors presently configured with the system (active and otherwise)
-	* Manual disabling of mirrors
-	* Generic status display of the "health" of the mirror ("OK" or flagged)
-	* Ability to edit the mirror's display information within our list on php.net
-	* Automated mailing to the mirror's maintainer when an issue is detected
-	* Automated mailing of the status of all mirrors on a weekly basis
-
-	Over time, some of the php.net mirror admins have discussed the need and/or desire to add new - or improve existing - functionality in this system. This includes, but is not limited to:
-
-	* Improved mirror status checking
-	* The ability to keep logs of notes regarding the mirror over time, displaying the most recent on the summary page
-	* Simple graphing and statistics for uptime and PING response time
-	* A geo-IP lookup to ensure that the mirror IP address matches the physical region it serves
-	* An online "waiting list" application form (many potential donors currently contact the mailing list or Dan Brown directly)
-	* An online form to collect data from mirror maintainer applicants
-	* A form-to-mail interface to email individual maintainers, the mailing list, or all maintainers directly (for announcements)
-	* Number of interested donors on the "waiting list" under each country's heading
-	* Automated quarterly reminders to folks on the "waiting list" to update their status if they are no longer willing/able (?)
-	* System specifications on each individual mirror (?)
-	* A scoring system based on the system specs of the mirrors (?)
-	* Load-balancing based upon the score of the mirror when redirecting to a local mirror in the region (?)
-	* Automated daily reminder emails to mirror maintainer when mirror is out-of-sync > 24 hours (still auto-disabled) (?)
-	* .... etc.

	===== Close and evaluate PHP Bugs =====		===== Close and evaluate PHP Bugs =====

solution2

Anonymous (anonymous@undisclosed.example.com) — 2025-04-03T13:08:43+00:00

2008/04/02 16:00		current
Line 50:		Line 50:
	* A version string must include a major, a minor and a patch level number (x.y.z) Please note that all are version numbers are mandatory.		* A version string must include a major, a minor and a patch level number (x.y.z) Please note that all are version numbers are mandatory.
	* A package version has a "state" (as indicated in the package.xml file), which describes the maturity. The state may be one of "alpha", "beta", "RC" or "stable" (listed in the order of code maturity). Please note that the state "RC" is achieved by using the state "beta" and appending the version number with "RC" followed by an integer		* A package version has a "state" (as indicated in the package.xml file), which describes the maturity. The state may be one of "alpha", "beta", "RC" or "stable" (listed in the order of code maturity). Please note that the state "RC" is achieved by using the state "beta" and appending the version number with "RC" followed by an integer
-	* The state should always be added as a suffix unless the state is "stable" 'a', 'b' or 'RC' (respectively for alpha, beta and release candidate) followed by a numeric value. E.g. '1.2.1b3', '1.0.0RC2', '1.1.0a1'	+	* The state should always be added as a suffix unless the state is "stable". Valid suffixes are 'a', 'b' or 'RC' (respectively for alpha, beta and release candidate) followed by a numeric value. E.g. '1.2.1b3', '1.0.0RC2', '1.1.0a1'
	* //Note that the PEAR installer cannot recognize hyphens in a package version string//		* //Note that the PEAR installer cannot recognize hyphens in a package version string//
	* In package.xml, the 'status' field for a release may be any of "alpha", "beta" or "stable". These states should be reflected in the version number: a "stable" release should be at least 1.0.0, for example. A Release Candidate is signified by RCx in the version number and a "beta" status in package.xml.		* In package.xml, the 'status' field for a release may be any of "alpha", "beta" or "stable". These states should be reflected in the version number: a "stable" release should be at least 1.0.0, for example. A Release Candidate is signified by RCx in the version number and a "beta" status in package.xml.

calltimebyref

Anonymous (anonymous@undisclosed.example.com) — 2025-04-03T13:08:43+00:00

2011/04/06 10:59		current
Line 3:		Line 3:
	* Date: 2008-05-21		* Date: 2008-05-21
	* Author: Steph Fox <sfox@php.net>		* Author: Steph Fox <sfox@php.net>
-	* Status: Under Discussion	+	* Status: Implemented
	* First Published at: http://wiki.php.net/rfc/calltimebyref		* First Published at: http://wiki.php.net/rfc/calltimebyref

Line 51:		Line 51:
	- [3] [[http://cvs.php.net/viewvc.cgi/php-src/main/main.c?r1=1.676&r2=1.677]]		- [3] [[http://cvs.php.net/viewvc.cgi/php-src/main/main.c?r1=1.676&r2=1.677]]

-		+	==== Comments ====
		+	currently allow_call_time_pass_reference is set to Off in both php.ini-production and php.ini-development for 5.3, and Call-time pass-by-reference was removed from 5.4, so this RFC is implemented/obsolete.

php60

Anonymous (anonymous@undisclosed.example.com) — 2025-04-03T13:08:43+00:00

2009/05/24 20:27		current
Line 22:		Line 22:
	- In run-tests.php output something at the end of c's main() to capture SEGVs during php shutdown in run-tests.php, probably change run-tests.php to catch SEGV (marcus)		- In run-tests.php output something at the end of c's main() to capture SEGVs during php shutdown in run-tests.php, probably change run-tests.php to catch SEGV (marcus)
	- deprecate ext/ctype in 6.0 and move to pecl in 6.1 in preference of unicode replacement functions. Note: the unicode replacements functions need to be merged to 5.x(without actual unicode support) for forward compatibility (andrei)		- deprecate ext/ctype in 6.0 and move to pecl in 6.1 in preference of unicode replacement functions. Note: the unicode replacements functions need to be merged to 5.x(without actual unicode support) for forward compatibility (andrei)
-	- <del>JIT fetch & (de-)encode of auto-globals based on [[http://marc.info/?l=php-internals&m=117145486824260&w=2\|this patch]]. Need to account for extensions wanting to access request data during RINIT. [[http://marc.info/?l=php-internals&m=116613042405124&w=2\|Some]] [[http://marc.info/?l=php-internals&m=116957894007497&w=2\|more]] references.</del> (Andrei) DONE	+	- <del>JIT fetch & (de-)encode of auto-globals based on [[http://marc.info/?l=php-internals&m=117145486824260&w=2\|this patch]]. Need to account for extensions wanting to access request data during RINIT. [[http://marc.info/?l=php-internals&m=116613042405124&w=2\|Some]] [[http://marc.info/?l=php-internals&m=116957894007497&w=2\|more]] references.</del> DONE (Andrei)
	- cleanups		- cleanups
-	- <del>remove UG(unicode) checks/references, Unicode is always "on"</del> (Felipe, Steph) DONE	+	- <del>remove UG(unicode) checks/references, Unicode is always "on"</del> DONE (Felipe, Steph)
	- Get rid of the BC crap in ext/date (derick)		- Get rid of the BC crap in ext/date (derick)
	- Try to find a way to see how case sensitive identifiers could be gradually be implemented, but do not "fix" it for PHP6.		- Try to find a way to see how case sensitive identifiers could be gradually be implemented, but do not "fix" it for PHP6.

introduction

Anonymous (anonymous@undisclosed.example.com) — 2025-04-03T13:08:43+00:00

2009/05/28 16:01		current
Line 12:		Line 12:
	===== Status Updates =====		===== Status Updates =====
	At a minimum status updates should be sent every 2 weeks, these should be sent to the appropriate mailing list and cc'd to [[gsoc@lists.php.net]], your mentor may ask for more regular updates.		At a minimum status updates should be sent every 2 weeks, these should be sent to the appropriate mailing list and cc'd to [[gsoc@lists.php.net]], your mentor may ask for more regular updates.
		+
		+
		+	You can find a template for your report [[gsoc/2009/report_template\|here]]

	===== Exams / Holidays =====		===== Exams / Holidays =====

spreadsheet_excel_writer

Anonymous (anonymous@undisclosed.example.com) — 2025-04-03T13:08:43+00:00

2009/08/03 13:45		current
Line 6:		Line 6:
	===== Alternatives =====		===== Alternatives =====
	* [[pear:packages:opendocument]]		* [[pear:packages:opendocument]]
		+
		+	===== Who uses it? =====
		+	It's pretty darned widely used, because it's unique and mostly works.
		+
		+	We see a fair number of relatively inexperienced developers who make use of it (rather than simple alternatives, like a CSV), and a smattering of more determined developers who contribute back fixes.

	===== The original =====		===== The original =====
Line 39:		Line 44:

	The problem with this is the fragility involved.		The problem with this is the fragility involved.
		+
		+	===== How do we tell if patches are any good? =====
		+	Well, this is a tricky one.
		+
		+	The majority of the users are very enthusiastic, but there's not much in the way of testing you can do on the changes; nor does casual review really help.
		+

solution1

Anonymous (anonymous@undisclosed.example.com) — 2025-04-03T13:08:43+00:00

2008/04/04 09:55		current
Line 3:		Line 3:
	* Status: Work in progress		* Status: Work in progress

-	=== The Problem ===	+	=== History ===
-	Currently, PECL versioning is fairly anarchic. From a user perspective, it's impossible to determine the status of an extension, or whether an update will break binary compatibility with previous versions - or work with a given PHP release - without falling back on trial-and-error. From a developer perspective, it's impossible to know exactly which code base a given bug was reported against. Windows PECL binaries should have reliable version information in the DLL resources (physically visible in the file properties), and PECL packages across all platforms should have this information available at runtime through phpinfo(), phpversion('extname') etc. Some of the processes in php.net that currently use hard-coded extension lists could also benefit from standardized versioning within the source files.	+	PECL versioning has historically been fairly anarchic. From a user perspective, this made it impossible to determine the status of an extension, or whether an update would break binary compatibility with previous versions - or work with a given PHP release - without falling back on trial-and-error. From a developer perspective, it was impossible to know exactly which code base a given bug was reported against. Windows PECL binaries should have reliable version information in the DLL resources (physically visible in the file properties), and PECL packages across all platforms should have this information available at runtime through phpinfo(), phpversion('extname') etc. Some of the processes in php.net that currently use hard-coded extension lists could also benefit from standardized versioning within the source files.
-		+
-	Resolving these issues will help bring PECL to a higher level of quality and reliability.	+
-		+
-	=== Some Facts and Figures ===	+
-	There are currently 214 modules in PECL. Of these:	+
-		+
-	* 1 is written in PHP	+
-	* 3 are SAPIs	+
-	* 2 are no longer hosted in PECL (and should be deleted)	+
-	* 1 doesn't declare a zend_module_entry	+
-	* 1 doesn't have versioning capability (pre-PHP 4.1?)	+
-	* 1 was a CVS error (and should be deleted)	+
-	* 1 is the timezone library for ext/date, and probably has non-standard versioning requirements	+
-		+
-	Of the remaining 204:	+
-		+
-	* 13 already use PHP_EXTNAME_VERSION declared in php_extname.h, but don't use -dev	+
-	* 25 already declare and use a versioning macro in php_extname.h, but the name could be anything	+
-	* 27 already declare and use a versioning macro somewhere in the source	+
-	* 3 do the whole thing in reverse and use the release version from package.xml	+
-	* 136 either hard-code the version, use $Id alone, use $Revision alone or ignore the whole thing	+

	=== Update ===		=== Update ===
-	As of 31st March 2008, the figures given above are incorrect: 145 PECL packages now use the PHP_EXTNAME_VERSION macro appropriately, and a mere handful now declare it in a file other than php_extname.h. The current focus is on PECL packages that are also core extensions in one or more versions of PHP.	+	As of April 2008, all PECL packages should use the PHP_EXTNAME_VERSION macro appropriately and declare the macro in the file //php_extname.h//, and all but a handful have been altered to do so. The one area that is still open for discussion concerns PECL packages that are also core extensions in one or more versions of PHP.

	=== Requirements ===		=== Requirements ===
Line 54:		Line 33:

	* A version string must include a major, a minor and a patch level number (x.x.x)		* A version string must include a major, a minor and a patch level number (x.x.x)
-	* The status of the package may be described using 'a', 'b' or 'RC' followed by a numeric value, e.g. '1.2.1b3', '1.0.0RC2', '1.1.0a1'	+	* The status of the package may be described using 'a', 'b' or 'RC' followed by a numeric value, e.g. '1.2.1b3', '1.0.0rc2', '1.1.0a1'
	* In package.xml, the 'status' field for a release may be any of "dev", "alpha", "beta" or "stable". These states should be reflected in the version number: a "stable" release should be at least 1.0.0, for example. A Release Candidate is signified by RCx in the version number and a "beta" status in package.xml.		* In package.xml, the 'status' field for a release may be any of "dev", "alpha", "beta" or "stable". These states should be reflected in the version number: a "stable" release should be at least 1.0.0, for example. A Release Candidate is signified by RCx in the version number and a "beta" status in package.xml.

Line 60:		Line 39:

	=== Core Modules in PECL ===		=== Core Modules in PECL ===
-	Johannes Schlueter - as Release Master of the PHP 5.3 series - made it known early in the proceedings that he has concerns over -dev, alpha or beta tags appearing in PHP core module versions. There's no process in place to export PECL releases into the PHP core; many of the modules in PECL are symlinked into the PHP core, affecting both snapshots and releases. This has benefits for the PECL modules concerned, in that they get far more testing than they otherwise might during the PHP development cycle, but the point remains that they are linked directly rather than filtered through an independent PECL release process.	+
		+	Johannes Schlueter - currently Release Master of the PHP 5.3 series - made it known early in the proceedings that he had concerns over -dev, alpha or beta tags appearing in PHP core module versions during a PHP release. There's no process in place to export PECL releases into the PHP core; many of the modules in PECL are symlinked into the PHP core, affecting both snapshots and releases. This has benefits for the PECL modules concerned, in that they get far more testing than they otherwise might during the PHP development cycle, but the point remains that they are linked directly rather than filtered through an independent PECL release process.

	The idea of using the tag '-core' rather than '-dev' to reflect the status of those dual-nature extensions came up. The PECL versioning could then remain x.x.x (no tag) during PECL releases, with the version number itself used to reflect alpha/beta development status. Christopher Jones of Oracle voiced his concern regarding core PECL modules in separate development branches, which happens with core symlinking (and can of course occur manually too). "Should the version in CVS HEAD be tagged -core6?" Pierre Joye recommended that module versions with a conflicting API simply reflect this in the version number, e.g. 1.0.3-core for PHP 5.* and 2.0.3-core for PHP 6. The PECL releases would be 1.0.3 and 2.0.3 respectively, and the version bumped to 1.0.4-core/2.0.4-core following release.		The idea of using the tag '-core' rather than '-dev' to reflect the status of those dual-nature extensions came up. The PECL versioning could then remain x.x.x (no tag) during PECL releases, with the version number itself used to reflect alpha/beta development status. Christopher Jones of Oracle voiced his concern regarding core PECL modules in separate development branches, which happens with core symlinking (and can of course occur manually too). "Should the version in CVS HEAD be tagged -core6?" Pierre Joye recommended that module versions with a conflicting API simply reflect this in the version number, e.g. 1.0.3-core for PHP 5.* and 2.0.3-core for PHP 6. The PECL releases would be 1.0.3 and 2.0.3 respectively, and the version bumped to 1.0.4-core/2.0.4-core following release.

2009-02-07

Anonymous (anonymous@undisclosed.example.com) — 2025-04-03T13:08:43+00:00

2009/02/09 23:15		current
Line 11:		Line 11:

	===== What are we doing =====		===== What are we doing =====
-	* Triage the <del>[[http://pear.php.net/bugs/search.php?search_for=&boolean=0&limit=50&order_by=id&direction=DESC&cmd=display&status=Open&bug_type=All&php_os=&packagever=&phpver=&assign=&maintain=&author_email=&bug_age=0&bug_updated=0\|latest 50 bugs]]</del>	+	* Triage the <del>[[http://short.ie/latest50pearbugs\|latest 50 bugs]]</del>
	* Write tests, seek feedback, improve the overall quality of reports.		* Write tests, seek feedback, improve the overall quality of reports.
	* See if we can knock off <del>[[http://pear.php.net/bugs/search.php?search_for=parse&boolean=0&limit=30&order_by=id&direction=DESC&cmd=display&status=Open&bug_type=Bug&php_os=&packagever=&phpver=&assign=&maintain=&author_email=&bug_age=0&bug_updated=0\|parse error related bugs]]</del> :)		* See if we can knock off <del>[[http://pear.php.net/bugs/search.php?search_for=parse&boolean=0&limit=30&order_by=id&direction=DESC&cmd=display&status=Open&bug_type=Bug&php_os=&packagever=&phpver=&assign=&maintain=&author_email=&bug_age=0&bug_updated=0\|parse error related bugs]]</del> :)

git

Anonymous (anonymous@undisclosed.example.com) — 2025-04-03T13:08:43+00:00

2008/07/09 11:51		current
Line 19:		Line 19:
	====== CVS ======		====== CVS ======

-	cvs -d :pserver:bcarlyon@cvs.php.net:/repository co bugtracker	+	cvs -d :pserver:anonymous@cvs.php.net:/repository co bugtracker

specs

Anonymous (anonymous@undisclosed.example.com) — 2025-04-03T13:08:43+00:00

2008/05/28 18:15		current
Line 37:		Line 37:
	* Pluggable user authentication		* Pluggable user authentication
	* REST-interface to extract information from the bugtracker (e.g. to package homepage, IRC)		* REST-interface to extract information from the bugtracker (e.g. to package homepage, IRC)
		+	* Be able to see CVS commits regrading a bug report based on an special ID in the commit log message

backslashnamespaces

Anonymous (anonymous@undisclosed.example.com) — 2025-04-03T13:08:43+00:00

2008/10/25 13:54		current
Line 287:		Line 287:
	* because \ is a single keystroke, it is possible to require \ prefix for all global functions/classes/constants, and conversion is minimally effortful (from personal experience trying to convert files to several namespace separators to see what it was like)		* because \ is a single keystroke, it is possible to require \ prefix for all global functions/classes/constants, and conversion is minimally effortful (from personal experience trying to convert files to several namespace separators to see what it was like)
	* code review ambiguities disappear permanently		* code review ambiguities disappear permanently
-	* name resolution order problems disappear if we decide that "foo/bar" or "foo::bar" is always prefixed with namespace name, and only short names like "bar()" or "new bar" are checked for both "nsname/bar()" and internal function "bar()" or "class nsname/bar" and internal class "bar". "/foo/bar" is used for global scoping.	+	* name resolution order problems disappear if we decide that "foo\bar" or "foo::bar" is always prefixed with namespace name, and only short names like "bar()" or "new bar" are checked for both "nsname\bar()" and internal function "bar()" or "class nsname\bar" and internal class "bar". "\foo\bar" is used for global scoping.
	* code coverage of namespace-related code is so good, it is possible to be very confident of the correctness of the patch.		* code coverage of namespace-related code is so good, it is possible to be very confident of the correctness of the patch.

bugtracker

Anonymous (anonymous@undisclosed.example.com) — 2025-04-03T13:08:43+00:00

2009/06/01 16:02		current
Line 20:		Line 20:
	* May 20 : Decided to use pear/Bugtracker and phpweb/bugs as a base		* May 20 : Decided to use pear/Bugtracker and phpweb/bugs as a base
	* May 28 : Began coding part of GSoC. Starting with removing deprecated libraries from bugtracker, and merging in code from phpweb/bugs		* May 28 : Began coding part of GSoC. Starting with removing deprecated libraries from bugtracker, and merging in code from phpweb/bugs
-	* May 30 : Decided to replace DB, DB_Object and Tree with mysqli	+	* May 30 : Decided to replace DB with MDB2
		+	* Jun 26 : Finished migration from DB to MDB2, remove Savant and Damblan
		+	* Jul 1 : Decided to implement and SVN integration
		+	* Jul 15 : Implemented RSS 2.0
		+	* Jul 20 : Implemented SVN Client and we're discussing how to integrate with bugtracker

	===== Notes =====		===== Notes =====
	* Initial code is [[http://cvs.php.net/viewvc.cgi/pear/Bugtracker/\|pear/Bugtracker]] which is a fork of [[http://cvs.php.net/viewvc.cgi/pearweb/public_html/bugs/\|pearweb/bugs]] from a couple years ago with modifications made by Jani to unify and convert the current bugs database		* Initial code is [[http://cvs.php.net/viewvc.cgi/pear/Bugtracker/\|pear/Bugtracker]] which is a fork of [[http://cvs.php.net/viewvc.cgi/pearweb/public_html/bugs/\|pearweb/bugs]] from a couple years ago with modifications made by Jani to unify and convert the current bugs database

2008-12-28

Anonymous (anonymous@undisclosed.example.com) — 2025-04-03T13:08:43+00:00

2008/12/28 21:48		current
Line 43:		Line 43:
	* http://pear.php.net/bugs/bug.php?id=14772		* http://pear.php.net/bugs/bug.php?id=14772
	* http://pear.php.net/bugs/bug.php?id=12384		* http://pear.php.net/bugs/bug.php?id=12384
-	* Get Services_Akismet2 up and running
	* Services_ExchangeRates [[http://pear.php.net/bugs/search.php?cmd=display&package_name[]=Services_ExchangeRates&status=OpenFeedback&bug_type=Bugs\|needs some love]]!		* Services_ExchangeRates [[http://pear.php.net/bugs/search.php?cmd=display&package_name[]=Services_ExchangeRates&status=OpenFeedback&bug_type=Bugs\|needs some love]]!
	* <del>Parse error</del>, doconnor		* <del>Parse error</del>, doconnor
Line 96:		Line 95:
	* MP3_Playlist - phpcs - doconnor		* MP3_Playlist - phpcs - doconnor
	* Net_IPv6 got into the pear test suite - doconnor		* Net_IPv6 got into the pear test suite - doconnor
		+	* Get Services_Akismet2 up and running - gauthierm and dufuz

2009-01-17

Anonymous (anonymous@undisclosed.example.com) — 2025-04-03T13:08:43+00:00

2009/01/18 21:54		current
Line 86:		Line 86:
	* Test the new version of pearweb - http://euk1.php.net/		* Test the new version of pearweb - http://euk1.php.net/
	* doconnor made a few patches for trivial issues		* doconnor made a few patches for trivial issues
		+	* Releases don't work :( White screen of death

qa

Anonymous (anonymous@undisclosed.example.com) — 2025-04-03T13:08:43+00:00

2017/09/22 13:28		current
Line 13:		Line 13:
	===== Build Overview =====		===== Build Overview =====

-	* [[http://gcov.php.net/viewer.php?version=PHP_5_3\|PHP 5.3 ]]	+	* [[http://gcov.php.net/viewer.php?version=PHP_HEAD\|PHP HEAD ]]
	* [[http://www.php.net/manual/en/faq.build.php#faq.build.configure\|Build Problems FAQ]]		* [[http://www.php.net/manual/en/faq.build.php#faq.build.configure\|Build Problems FAQ]]

	===== Coverage =====		===== Coverage =====
-	* [[http://gcov.php.net/viewer.php?version=PHP_5_3&func=tested_functions\|Tested functions]]	+	* [[http://gcov.php.net/viewer.php?version=PHP_HEAD&func=tested_functions\|Tested functions]]
-	* [[http://gcov.php.net/PHP_5_3/lcov_html/\|Test and Code Coverage Analysis]]	+	* [[http://gcov.php.net/PHP_HEAD/lcov_html\|Test and Code Coverage Analysis]]

	===== Bugtracker =====		===== Bugtracker =====

svnexternals

Anonymous (anonymous@undisclosed.example.com) — 2025-04-03T13:08:43+00:00

2011/04/06 10:59		current
Line 1:		Line 1:
-	====== Request for Comments: How to write RFCs ======	+	====== Request for Comments: SVN externals ======
	* Version: 1.0		* Version: 1.0
	* Date: 2008-07-01		* Date: 2008-07-01

zendsignals

Anonymous (anonymous@undisclosed.example.com) — 2025-04-03T13:08:43+00:00

2011/05/31 22:50		current
Line 3:		Line 3:
	* Date: 2008-07-05		* Date: 2008-07-05
	* Author: Lucas Nealan <lucas@facebook.com>		* Author: Lucas Nealan <lucas@facebook.com>
-	* Status: Under Discussion	+	* Status: Implemented in PHP 5.4
	* First Proposed by: [[http://markmail.org/message/3jg6cwqfghdlydhy\|Rasmus Lerdorf]]		* First Proposed by: [[http://markmail.org/message/3jg6cwqfghdlydhy\|Rasmus Lerdorf]]
	* Source code: [[http://tekrat.com/downloads/bits/php-5.3-signals.20091120.patch\|PHP_5_3 patch]] [[http://tekrat.com/downloads/bits/php-trunk-signals.20091120.patch\|PHP Trunk patch]] (11-20-2009).		* Source code: [[http://tekrat.com/downloads/bits/php-5.3-signals.20091120.patch\|PHP_5_3 patch]] [[http://tekrat.com/downloads/bits/php-trunk-signals.20091120.patch\|PHP Trunk patch]] (11-20-2009).

y1

Anonymous (anonymous@undisclosed.example.com) — 2025-04-03T13:08:43+00:00

2013/11/15 13:19		current
Line 1:		Line 1:
		+	this box was decommisioned, the cvs stuff was killed, and svn was moved to the svn2 box
	====== y1.php.net ======		====== y1.php.net ======

php53

Anonymous (anonymous@undisclosed.example.com) — 2025-04-03T13:08:43+00:00

2011/04/06 10:59		current
Line 151:		Line 151:
	==== After the first stable release ====		==== After the first stable release ====

-	- add firebird/interbase to windows builds	+	- <del>add firebird/interbase to windows builds</del>
	- make all extensions use php implementation of getenv (Pierre)		- make all extensions use php implementation of getenv (Pierre)
	- Improve the build script to ease the parsing of the output and QA		- Improve the build script to ease the parsing of the output and QA

cvs_related_scripts

Anonymous (anonymous@undisclosed.example.com) — 2025-04-03T13:08:43+00:00

2026/04/23 10:37	current
Line 1:	Line 1:
	+	When migrating from CVS to Subversion the following stuff has to be touched (changed/removed/replaced/...)

	+	* scripts in CVSROOT
	+	* cvsclean script in php-src.
	+	* user management (creation/change password)
	+	* snaps building (source and windows)
	+	* release building (similar to snaps...)
	+	* php.net website creation
	+	* doc creation (pear and php)
	+	* *.php.net website publishing
	+	* tiny stuff like "Fixed in CVS" message in the bug tracker
	+	* lxr.php.net
	+	* daily ChangeLog update

runtests

Anonymous (anonymous@undisclosed.example.com) — 2025-04-03T13:08:43+00:00

2009/04/28 17:05		current
Line 7:		Line 7:
	* Timezone: GMT +2 (Georg, Stefan), GMT +1 (Zoe)		* Timezone: GMT +2 (Georg, Stefan), GMT +1 (Zoe)
	* Mailing list: php-qa@lists.php.net – IRC: #php.pecl on EFnet		* Mailing list: php-qa@lists.php.net – IRC: #php.pecl on EFnet
		+	* Repository access : cvs -d :pserver:cvsread@cvs.php.net:/repository checkout phpruntests

policy

Anonymous (anonymous@undisclosed.example.com) — 2025-04-03T13:08:43+00:00

2008/11/24 13:30		current
Line 63:		Line 63:
	Package maintainers can also grant QA the rights to make a releases for their packages.		Package maintainers can also grant QA the rights to make a releases for their packages.

-	==== pearweb QA subsection ====

-	It seems that there is a lack of QA material in the manual that people agree on and there is also need to make it move visible for people so they will actually follow those rules/guidelines. The QA team will therefore get its own QA subsection in the manual and will have control over it just like package maintainer controls package related docs in the manual. The QA team also gets its own subsection on pearweb so people can more easily access QA material which is too dynamic or just related to the QA team own internal documentation purposes. There the QA will, for example, publish their latest decisions. Furthermore here the QA team will be able to provide interfaces to QA team services. For example, here the QA team could offer an interface for maintainers to configure the access rights they want to grant the QA. Finally the core QA team can add QA related notes to each package homepage to communicate QA related information to the user base.

	==== Approving first stable release ====		==== Approving first stable release ====

log

Anonymous (anonymous@undisclosed.example.com) — 2025-04-03T13:08:43+00:00

2009/11/02 18:23		current
Line 267:		Line 267:
	\| [[http://svn.php.net/viewvc?view=revision&revision=290147\|290147]] \| derick \| 2009-11-02T16:12:20.158272Z \| - Updated to version 2009.17 (2009q)\|merged\|		\| [[http://svn.php.net/viewvc?view=revision&revision=290147\|290147]] \| derick \| 2009-11-02T16:12:20.158272Z \| - Updated to version 2009.17 (2009q)\|merged\|
	\| [[http://svn.php.net/viewvc?view=revision&revision=290150\|290150]] \| felipe \| 2009-11-02T17:37:32.398819Z \| - Fixed bug #49244 (Floating point NaN cause garbage characters). (patch by Sjoerd) \|?\|		\| [[http://svn.php.net/viewvc?view=revision&revision=290150\|290150]] \| felipe \| 2009-11-02T17:37:32.398819Z \| - Fixed bug #49244 (Floating point NaN cause garbage characters). (patch by Sjoerd) \|?\|
		+	\| [[http://svn.php.net/viewvc?view=revision&revision=290154\|290154]] \| pajoye \| 2009-11-02T20:46:52.389036Z \| - Fixed #50052, Different Hashes on Windows and Linux on wrong Salt size\|?\|
		+	\| [[http://svn.php.net/viewvc?view=revision&revision=290166\|290166]] \| pajoye \| 2009-11-03T10:48:12.857521Z \| - fix lenght for alloc and cpy (Kanwal)\|?\|
		+	\| [[http://svn.php.net/viewvc?view=revision&revision=290167\|290167]] \| scottmac \| 2009-11-03T12:15:03.991984Z \| Update PCRE to 8.00 \|?\|
		+	\| [[http://svn.php.net/viewvc?view=revision&revision=290168\|290168]] \| scottmac \| 2009-11-03T12:23:54.748600Z \| BFN \|?\|
		+	\| [[http://svn.php.net/viewvc?view=revision&revision=290170\|290170]] \| uw \| 2009-11-03T14:56:04.044360Z \| Fix for bug #49965 . Let mysqli_options() try to cast option values to the appropriate type.\|?\|
		+	\| [[http://svn.php.net/viewvc?view=revision&revision=290190\|290190]] \| guenter \| 2009-11-03T21:21:34.589624Z \| removed now obsolete NetWare hack since I fixed this with Novell some longer time ago in their SDK header. \|?\|
		+	\| [[http://svn.php.net/viewvc?view=revision&revision=290191\|290191]] \| guenter \| 2009-11-03T21:26:39.217225Z \| added timezone define for NetWare. \|?\|
		+	\| [[http://svn.php.net/viewvc?view=revision&revision=290196\|290196]] \| uw \| 2009-11-04T12:33:49.082539Z \| Adding CLEAN sections and making tests portable between PHP 5 and PHP 6 by replacing string(n) with %unicode%% %%string%(n) and similar.\|?\|
		+	\| [[http://svn.php.net/viewvc?view=revision&revision=290199\|290199]] \| iliaa \| 2009-11-04T13:44:10.979986Z \| Fixed bug #50073 (parse_url() incorrect when ? in fragment). \|?\|
		+	\| [[http://svn.php.net/viewvc?view=revision&revision=290206\|290206]] \| uw \| 2009-11-04T16:09:07.758115Z \| Skipping if MySQL old password algorithm is in use as it seems to be the case on gcov.php.net\|?\|
		+	\| [[http://svn.php.net/viewvc?view=revision&revision=290210\|290210]] \| uw \| 2009-11-04T16:56:32.352885Z \| mysqli won't accept empty string for socket, skip test of mysqli.default_socket if test run does not use socket\|?\|
		+	\| [[http://svn.php.net/viewvc?view=revision&revision=290212\|290212]] \| mbeccati \| 2009-11-04T19:16:39.255772Z \| - Reverting previous fix for bug #49985 # Unmerged changes from revision 289924 \|?\|
		+	\| [[http://svn.php.net/viewvc?view=revision&revision=290214\|290214]] \| mbeccati \| 2009-11-04T19:32:27.170798Z \| - Properly fixed bug #49985 (pdo_pgsql prepare() re-use previous aborted transaction). # Removed usage of the memory address when generating prepared statemend names # as uniqueness can't be enforced. Used a statment counter instead. \|?\|
		+	\| [[http://svn.php.net/viewvc?view=revision&revision=290231\|290231]] \| dmitry \| 2009-11-05T09:33:19.672560Z \| Fixed unnecessary invokation of setitimer when timeouts have been disabled (Arvind Srinivasan) \|?\|
		+	\| [[http://svn.php.net/viewvc?view=revision&revision=290236\|290236]] \| dmitry \| 2009-11-05T10:38:56.883775Z \| Avoid invoking setitimer when timeouts have been disabled (Arvind Srinivasan) \|?\|
		+	\| [[http://svn.php.net/viewvc?view=revision&revision=290253\|290253]] \| jani \| 2009-11-05T11:33:32.305688Z \| - Missing entry\|?\|
		+	\| [[http://svn.php.net/viewvc?view=revision&revision=290266\|290266]] \| uw \| 2009-11-05T11:51:21.319010Z \| Fixing test: it didn't do a select_db and gave a false-positive with libmysql\|?\|
		+	\| [[http://svn.php.net/viewvc?view=revision&revision=290288\|290288]] \| uw \| 2009-11-05T12:14:08.310342Z \| Fixing test: of course, libmysql won't care about open_basedir, but mysqlnd should\|?\|
		+	\| [[http://svn.php.net/viewvc?view=revision&revision=290306\|290306]] \| iliaa \| 2009-11-05T13:29:34.995523Z \| Make sure that max_file_uploads is set to 20 by-default in all places \|?\|
		+	\| [[http://svn.php.net/viewvc?view=revision&revision=290362\|290362]] \| wharmby \| 2009-11-05T22:44:02.962662Z \| Fix tests\|?\|
		+	\| [[http://svn.php.net/viewvc?view=revision&revision=290363\|290363]] \| sixd \| 2009-11-05T23:03:28.852685Z \| Update and fix grammar\|?\|
		+	\| [[http://svn.php.net/viewvc?view=revision&revision=290364\|290364]] \| sixd \| 2009-11-06T02:09:47.340472Z \| Add pecl mail list\|?\|
		+	\| [[http://svn.php.net/viewvc?view=revision&revision=290368\|290368]] \| scottmac \| 2009-11-06T09:02:52.634548Z \| Fix a typo \|?\|
		+	\| [[http://svn.php.net/viewvc?view=revision&revision=290392\|290392]] \| felipe \| 2009-11-07T21:27:15.860391Z \| - Fixed bug #50090 (Typo in IteratorIterator constructor) \|?\|
		+	\| [[http://svn.php.net/viewvc?view=revision&revision=290395\|290395]] \| felipe \| 2009-11-08T15:02:54.675081Z \| - Added SKIPIF \|?\|
		+	\| [[http://svn.php.net/viewvc?view=revision&revision=290398\|290398]] \| rasmus \| 2009-11-08T15:18:10.480247Z \| Fix bug #50115 \|?\|
		+	\| [[http://svn.php.net/viewvc?view=revision&revision=290404\|290404]] \| iliaa \| 2009-11-09T01:54:23.517362Z \| Upgraded bundled sqlite to version 3.6.20 \|?\|
		+	\| [[http://svn.php.net/viewvc?view=revision&revision=290419\|290419]] \| rasmus \| 2009-11-09T15:13:07.815872Z \| Fix bug #50124 \|?\|
		+	\| [[http://svn.php.net/viewvc?view=revision&revision=290420\|290420]] \| derick \| 2009-11-09T15:39:15.015555Z \| - Updated to version 2009.18 (2009r)\|?\|
		+	\| [[http://svn.php.net/viewvc?view=revision&revision=290434\|290434]] \| jani \| 2009-11-09T17:08:48.606768Z \| - Fix bad section names (extra - in the end..)\|?\|
		+	\| [[http://svn.php.net/viewvc?view=revision&revision=290435\|290435]] \| rasmus \| 2009-11-09T17:21:15.612206Z \| Fix bug #50129 \|?\|
		+	\| [[http://svn.php.net/viewvc?view=revision&revision=290489\|290489]] \| sixd \| 2009-11-10T22:48:37.738188Z \| Add test for long fixed bug\|?\|
		+	\| [[http://svn.php.net/viewvc?view=revision&revision=290507\|290507]] \| iliaa \| 2009-11-11T13:49:21.273229Z \| typo fix \|?\|
		+	\| [[http://svn.php.net/viewvc?view=revision&revision=290515\|290515]] \| felipe \| 2009-11-11T18:52:12.425227Z \| - Fixed bug #50152 (ReflectionClass::hasProperty hehaves like isset() not property_exists) [5_2 is OK] \|?\|
		+	\| [[http://svn.php.net/viewvc?view=revision&revision=290516\|290516]] \| felipe \| 2009-11-11T18:59:37.518532Z \| - Fixed bug #50146 (property_exists: Closure object cannot have properties) \|?\|
		+	\| [[http://svn.php.net/viewvc?view=revision&revision=290519\|290519]] \| sixd \| 2009-11-11T19:44:53.497711Z \| Sigh. Fix grammar of title\|?\|
		+	\| [[http://svn.php.net/viewvc?view=revision&revision=290527\|290527]] \| cellog \| 2009-11-11T21:02:59.366740Z \| fix PHP Bug #49910: no support for ././@LongLink for long filenames in phar tar support\|?\|
		+	\| [[http://svn.php.net/viewvc?view=revision&revision=290567\|290567]] \| felipe \| 2009-11-12T00:10:00.340842Z \| - Fixed bug #50005 (Throwing through Reflection modified Exception object makes segmentation fault) \|?\|
		+	\| [[http://svn.php.net/viewvc?view=revision&revision=290568\|290568]] \| felipe \| 2009-11-12T00:44:43.769026Z \| - Fix typo\|?\|
		+	\| [[http://svn.php.net/viewvc?view=revision&revision=290570\|290570]] \| rasmus \| 2009-11-12T01:09:16.218434Z \| Fix bug #49098 \|?\|
		+	\| [[http://svn.php.net/viewvc?view=revision&revision=290574\|290574]] \| rasmus \| 2009-11-12T08:26:43.203190Z \| NEWS entries for mysqli crash fix bug \|?\|
		+	\| [[http://svn.php.net/viewvc?view=revision&revision=290575\|290575]] \| jani \| 2009-11-12T09:07:51.095253Z \| bfn\|?\|
		+	\| [[http://svn.php.net/viewvc?view=revision&revision=290578\|290578]] \| johannes \| 2009-11-12T15:05:03.813490Z \| Fix #50063 (safe_mode_include_dir fails)\|?\|
		+	\| [[http://svn.php.net/viewvc?view=revision&revision=290582\|290582]] \| thetaphi \| 2009-11-12T15:19:35.858643Z \| Fix bug #50087: NSAPI performance improvements \|?\|

2008-11-15

Anonymous (anonymous@undisclosed.example.com) — 2025-04-03T13:08:43+00:00

2008/11/17 07:37		current
Line 7:		Line 7:
	===== Overall Goal =====		===== Overall Goal =====
	Increase the unit test coverage for new issues, while decreasing the amount of failures.		Increase the unit test coverage for new issues, while decreasing the amount of failures.
		+
		+	===== Participants =====
		+	cweiske, doconnor, ifeghali, quipo, gauthierm, & kguest (earlier in week)

	===== What are we doing =====		===== What are we doing =====

2008-12-06

Anonymous (anonymous@undisclosed.example.com) — 2025-04-03T13:08:43+00:00

2008/12/06 15:06		current
Line 38:		Line 38:
	* <del>[[http://pear.php.net/bugs/bug.php?id=14868\|Bug #14868 Validate_AT unit test failures]]</del> - doconnor, contacted Nov 5 and 27th		* <del>[[http://pear.php.net/bugs/bug.php?id=14868\|Bug #14868 Validate_AT unit test failures]]</del> - doconnor, contacted Nov 5 and 27th
	* Followup on [[http://pear.php.net/bugs/search.php?cmd=display&search_for=PHPUnit&php_os=&boolean=0&bug_type=&bug_age=0&bug_updated=0&order_by=ts1&direction=DESC&packagever=&phpver=&limit=30&handle=&assign=&maintain=&showmenu=1&showmenu=1&status=Open PHPUnit patches\|Updating unit tests to PHPUnit3]]		* Followup on [[http://pear.php.net/bugs/search.php?cmd=display&search_for=PHPUnit&php_os=&boolean=0&bug_type=&bug_age=0&bug_updated=0&order_by=ts1&direction=DESC&packagever=&phpver=&limit=30&handle=&assign=&maintain=&showmenu=1&showmenu=1&status=Open PHPUnit patches\|Updating unit tests to PHPUnit3]]
-	* Services_Yadis - maintained? Or can we get [[http://pear.php.net/bugs/search.php?cmd=display&package_name[]=Services_Yadis&status=OpenFeedback&bug_type=Bugs\|these bugs resolved]]?	+	* <del>Services_Yadis - maintained? Or can we get [[http://pear.php.net/bugs/search.php?cmd=display&package_name[]=Services_Yadis&status=OpenFeedback&bug_type=Bugs\|these bugs resolved]]</del>? New release (doconnor)

	==== Specific tasks ====		==== Specific tasks ====

doc

Anonymous (anonymous@undisclosed.example.com) — 2025-04-03T13:08:43+00:00

2024/10/04 00:33		current
Line 3:		Line 3:

	===== Guide for Contributors =====		===== Guide for Contributors =====
-	If you are interested in contributing to PHP Manual, check out [[http://doc.php.net/tutorial/\|our guide]].	+	If you are interested in contributing to PHP Manual, check out [[https://doc.php.net/guide/\|our guide]].

	===== Index =====		===== Index =====
Line 18:		Line 18:

	===== External Links =====		===== External Links =====
-	* [[http://doc.php.net/\|Documentation Website]]	+	* [[https://doc.php.net/\|Documentation Website]]
	* [[http://bit.ly/phpdocbugs\|Open Bugs]]		* [[http://bit.ly/phpdocbugs\|Open Bugs]]

phpng-upgrading

Anonymous (anonymous@undisclosed.example.com) — 2025-04-03T13:08:43+00:00

2017/09/22 13:28		current
Line 571:		Line 571:

	- REGISTER_RESOURCE(return_value, result, le_result);		- REGISTER_RESOURCE(return_value, result, le_result);
-	+ RETURN_RES(zend_register_resource(result, le_result);	+	+ RETURN_RES(zend_register_resource(result, le_result));
	</code>		</code>

rfc

Anonymous (anonymous@undisclosed.example.com) — 2026-04-21T19:08:26+00:00

2026/04/21 17:44		current
Line 20:		Line 20:
	This section is for RFCs that have been announced on the PHP "internals" mail list.		This section is for RFCs that have been announced on the PHP "internals" mail list.

-	* [[rfc:partial_function_application_optional_placeholder\|PHP RFC: Partial Function Application: Handling of Optional Parameters]] (created 2026-04-20)	+	* [[rfc:partial_function_application_optional_placeholder\|Partial Function Application: Handling of Optional Parameters]] (created 2026-04-20)
	* [[rfc:remove-link-to-x-from-php-net\|Remove the links to X.com from PHP.net]] (Created 2026-04-12)		* [[rfc:remove-link-to-x-from-php-net\|Remove the links to X.com from PHP.net]] (Created 2026-04-12)
	* [[rfc:mariadb_rfc\|Add MariaDB specific features to mysqlnd and mysqli]] (Created 2026-04-06)		* [[rfc:mariadb_rfc\|Add MariaDB specific features to mysqlnd and mysqli]] (Created 2026-04-06)

svnmigration

Anonymous (anonymous@undisclosed.example.com) — 2025-04-03T13:08:43+00:00

2026/04/23 10:37		current
Line 1:		Line 1:
		+	This is just a note to let people know that the contents of this page have been [[vcs/cvs2svnconversion\|moved]] and there is a [[vcs/cvstosvnmigration\|new landing page]] to collect all documents about the migration from cvs to svn.

feeds

Anonymous (anonymous@undisclosed.example.com) — 2025-04-03T13:08:43+00:00

2026/04/23 10:37	current
Line 1:	Line 1:
	+	==== Discussion List ====
	+	{{rss>http://news.php.net/group.php?group=php.doc&format=rss 10 6h}}
	+
	+	==== Commits ====
	+	{{rss>http://news.php.net/group.php?group=php.doc.cvs&format=rss 10 6h}}
	+
	+	==== Bugs ====
	+	{{rss>http://news.php.net/group.php?group=php.doc.bugs&format=rss 10 6h}}

phpnetauth

Anonymous (anonymous@undisclosed.example.com) — 2025-04-03T13:08:43+00:00

2010/01/08 21:11		current
Line 20:		Line 20:
	* Consider binding VCS access control on a per-user basis (eliminating the avail file)		* Consider binding VCS access control on a per-user basis (eliminating the avail file)
	* RIP Magical Cookie, and thanks for all the memories		* RIP Magical Cookie, and thanks for all the memories
		+	* Consider a fallback system for those who prefer separate logins to each site. This suggests a new auth backend that OpenID can be plugged into.

	==== Status ====		==== Status ====

phpnetmirroring

Anonymous (anonymous@undisclosed.example.com) — 2025-04-03T13:08:43+00:00

2026/04/23 10:37	current
Line 1:	Line 1:
	+	===== New Mirror Management System =====
	+	// Possible Mentor: [[danbrown@php.net\|Daniel P. Brown]] //

	+	==== Description ====
	+	Our existing management system for the network of official mirrors worldwide has a few issues and areas for improvement. The present system is accessible via a browser-based web interface (using a php.net CVS account, and hosted on master.php.net), and provides the following services:
	+
	+	* Addition, deletion, and modification of DNS for official mirrors of the php.net site as a whole
	+	* Automated checking of all mirrors, marking mirrors as "disabled" when issues are detected
	+	* Listing of all mirrors presently configured with the system (active and otherwise)
	+	* Manual disabling of mirrors
	+	* Generic status display of the "health" of the mirror ("OK" or flagged)
	+	* Ability to edit the mirror's display information within our list on php.net
	+	* Automated mailing to the mirror's maintainer when an issue is detected
	+	* Automated mailing of the status of all mirrors on a weekly basis
	+
	+	Over time, some of the php.net mirror admins have discussed the need and/or desire to add new - or improve existing - functionality in this system. This includes, but is not limited to:
	+
	+	* Improved mirror status checking
	+	* The ability to keep logs of notes regarding the mirror over time, displaying the most recent on the summary page
	+	* Simple graphing and statistics for uptime and PING response time
	+	* A geo-IP lookup to ensure that the mirror IP address matches the physical region it serves
	+	* An online "waiting list" application form (many potential donors currently contact the mailing list or Dan Brown directly)
	+	* An online form to collect data from mirror maintainer applicants
	+	* A form-to-mail interface to email individual maintainers, the mailing list, or all maintainers directly (for announcements)
	+	* Number of interested donors on the "waiting list" under each country's heading
	+	* Automated quarterly reminders to folks on the "waiting list" to update their status if they are no longer willing/able (?)
	+	* System specifications on each individual mirror (?)
	+	* A scoring system based on the system specs of the mirrors (?)
	+	* Load-balancing based upon the score of the mirror when redirecting to a local mirror in the region (?)
	+	* Automated daily reminder emails to mirror maintainer when mirror is out-of-sync > 24 hours (still auto-disabled) (?)
	+	* .... etc.
	+
	+	==== Progress ====
	+	A few points integrated.
	+
	+	==== Status ====
	+	Open.
	+
	+	==== TODO ====
	+	* Document currently used process and tools
	+	* Also note that several related bugs exist

testfest-2009

Anonymous (anonymous@undisclosed.example.com) — 2025-04-03T13:08:43+00:00

2026/04/23 10:37	current
Line 1:	Line 1:
	+	====== PHP TestFest 2009 ======

	+	//This page contains out-dated material and is archived here for informational purposes. For recent information, see the [[qa:testfest\| main PHP TestFest page]].//
	+
	+	===== How do I join? How do I get more information? =====
	+
	+	See the [[http://qa.php.net/testfest.php\|TestFest]] homepage on the QA team website for details. Alternatively you can join #php.pecl on Efnet or the #phptestfest channel on Freenode IRC server. There should usually be someone around to help.
	+	Follow twitter [[http://twitter.com/phptestfest\|testfest]]
	+
	+	==== Summary of registered groups ====
	+
	+	^ Group name ^ Date ^ Ext to test ^ mentor ^ Organiser email ^
	+	\| Belgium \| May 9 \| SQlite3, ldap \| Felix de Vleigher \| felixdv@php.net \|
	+	\| Brazil (SP ) \| June 20 \| \| \| rdohms@gmail.com \|
	+	\| Brazil (Rio) \| July 3 \| \| Igor Feghali \| ifeghali@php.net \|
	+	\| Brazil(BR) \| June 23 \| \| Er Galvao Abbott \| galvao@galvao.eti.br \|
	+	\| Brazil(SC) \| \| \| \| silvano@php.net \|
	+	\| Brazil(CEPUG) \| \| \| \| brunoviana@gmail.com \|
	+	\| Catalonia \| June 13 \| \| Hannes Magnusson \| alex@corretge.cat \|
	+	\| Canada (Montreal) \| May 1/2/3 \| Date, time \| Derick Rethans \| afilina@phpquebec.org \|
	+	\| Colombia \| \| \| \| andphe@gmail.com \|
	+	\| France \| May 9 \| CURL \| \| perrick@noparking.net \|
	+	\| Germany (Munich) \| April 16/17 \| \| Pierre Joye \| Pierre Joye \|
	+	\| Germany (Berlin) \| May 9/10 \| gettext, sockets, soap, xsl, posix \| \| till@php.net \|
	+	\| Germany (Wurzburg)\| May 30/31 \| \| \| info@fruityweb.de \|
	+	\| Ireland \| \| \| \| davic@php.ie \|
	+	\| Italy \| June 20/20/21 \| \| \| francesco@cphp.it \|
	+	\| Netherlands \| May 9 \| CURL \| \| stefan@phpgg.nl \|
	+	\| Norway \| June 9 \| \| Hannes Magnusson \| russ@redpill-linpro.com\|
	+	\| Peru \| April 4 \| \| \| info.latino@dokeos.com \|
	+	\| USA (tek) \| May 21 \| \| \| stefan@phpgg.nl \|
	+	\| USA (NYPHP) \| May 23 \| XmlReader/XMLWriter/DOM \| Elizabeth Smith \| Hans Zaunere \|
	+	\| USA (Atlanta) \| \| DOM \| \| Ben Ramsey \|
	+	\| USA (Nashville) \| \| \| \| Will Fitch \|
	+	\| UK (London) \| May 9 \| SPL \| Zoe Slattery \| matt.raines@phplondon.org \|
	+	\| UK (NorthWest) \| May 9 \| SPL \| Scott MacVicar \| lorna@lornajane.net \|
	+	\| NZ (Christchurch) \| June 20 \| \| \| lukemoynihan@gmail.com \|
	+
	+	==== Results ====
	+	See
	+	* http://results.testfest.php.net/displayresults.php (32 bit)
	+	* http://testfest.php.net/displayresults.php (64 bit)
	+
	+
	+	===== Registered UGs =====
	+
	+	==== Belgium ====
	+
	+
	+	* Belgian PHP Usergroup, http://www.phpbelgium.be.
	+	* Contact: Felix De Vliegher, <felixdv@php.net>
	+	* Date: Saturday May 9th 9am-6pm
	+	* Location: Combell offices, Skaldenstraat 121, 9042 Gent, Belgium [[http://maps.google.com/maps?f=q&source=s_q&hl=nl&geocode=&q=Skaldenstraat+121+Gent+9042&sll=37.0625,-95.677068&sspn=34.534108,93.076172&ie=UTF8&ll=51.113707,3.788931&spn=0.006681,0.022724&z=16&iwloc=A \| Google maps]]
	+	* Subscribe/RSVP here: http://tr.im/jpSY
	+	* Extension to test: SQLite3, Ldap
	+
	+	==== Brazil ====
	+
	+	* PHPSP (http://www.phpsp.org.br) Contact Names: Augusto Pascutti & Rafael Dohms <admin@phpsp.org.br> - May
	+	* PHP Rio (http://www.phprio.org) Contact Name: Igor Feghali <ifeghali@php.net>
	+	* PHPBR (http://www.phpbr.com.br) Contact Name: Er Galvão Abbott <galvao@phpbr.com.br>
	+	* PHPSC (http://www.phpsc.com.br) Contact Name: Silvano Girardi Jr. <silvano@php.net>
	+	* CEPUG (http://www.cepug.org) Contact Name: Bruno Viana <brunoviana@gmail.com>
	+
	+	==== Catalonia ====
	+
	+	* CCCPHP, http://cccphp.net. Saturday 13th of june at [[http://ca.wikipedia.org/wiki/Verges\|Verges]] (Baix Empordà). [[http://cccphp.googlecode.com/svn/trunk/org.TestFest2009/cartell%20PHP%20TestFest%202009.pdf\|Agenda]]. [[http://www.facebook.com/home.php#/event.php?eid=75135753753&ref=ts\|Facebook]]. Return of Service to Open Source. Contact name: Àlex Corretgé, <alex@corretge.cat>
	+
	+	==== Canada ====
	+
	+	=== Montreal ===
	+
	+	* Organized by PHP Quebec [[http://phpquebec.org]]
	+	* Contact: Anna Filina <afilina@phpquebec.org>
	+	* Dates
	+	* Friday May 1st 7pm-10pm (social/casual/unofficial warm-up)
	+	* Saturday May 2nd 9am-6pm (TestFest/CodeFest)
	+	* Sunday May 3rd 9am-6pm (TestFest/CodeFest)
	+	* Location: Helm - 273 Bernard W.
	+	* More info about the event: [[http://codefest.ws]]
	+
	+	==== Colombia ====
	+
	+	* Organized by Colombia PHP [[http://groups.google.com/group/php-colombia]] [[http://www.colombiaphp.net]]
	+	* Contact: Andrés Felipe Vargas <andphe@gmail.com>
	+	* Date: to define
	+	* Location: irc #php-co at freenode.net
	+
	+	==== France ====
	+
	+	=== Paris ===
	+
	+	* Organized by AFUP[[http://afup.org]]
	+	* Contact: Perrick Penet <perrick@noparking.net>
	+	* Date: Saturday May 9th 10am-8pm (PhpCamp / TestFest)
	+	* Location: La Cantine - 151 rue Montmartre - Passage des Panoramas - 12 Galerie Montmartre - 75002 Paris
	+	* More info about the event: [[http://afup.org/pages/rendezvous/?id=6]]
	+	* Extension to test: CURL
	+
	+
	+	==== Germany ====
	+
	+	=== Munich ===
	+	* PLEASE RSVP:
	+	* Contact Pierre, email:pierre@php.net
	+	* or come online on Freenode #phptestfest
	+
	+	* Prepare Slides
	+	* How PHP Works
	+	* [[http://wiki.php.net/qa/testfesttalk\|How to write PHPT]]
	+	* 16th Evening Meeting will stand at [[http://www.nockherberg.com/\|Nockhenberg Biergarten]]
	+	* 18.30 Welcome
	+	* 19.00 Talks
	+	* PHP 5.3 - Sebastian Bergmann
	+	* QA and PHP, Sebastian Schürmann
	+	* Food&Drinks
	+	* 17th TestFest Day
	+	* Location: [[http://www.microsoft.com/germany/unternehmen/informationen/gmbh_profil/niederlassungen/muenchen.mspx\|Microsoft EMEA Office in Unterschleißheim]]
	+	* 09:30 welcome, 09:45 presentation (until ~11:30)
	+	* Introductions and presentations of the test infrastructure for PHP
	+	* Write a bunch of tests :)
	+
	+
	+
	+	=== Berlin ===
	+
	+	* Contact Till, email:till@php.net
	+
	+	* Chosen date: May 9th/10th (weekend)
	+
	+	* Location: [[http://maps.google.com/maps?f=q&source=s_q&hl=en&geocode=&q=Boxhagener+Stra%C3%9Fe+119,+10245+Friedrichshain,+Berlin&sll=52.50743,13.467888&sspn=0.010239,0.019312&ie=UTF8&ll=52.512447,13.461277&spn=0.010238,0.019312&t=h&z=16&iwloc=addr\|Boxhagener Str. 119, Berlin]]
	+
	+	* PLEASE RSVP: [[http://wiki.upstream-berlin.com/index.php/PHPTestFest2009]]
	+
	+	* Extensions: gettext, sockets, soap, xsl, posix
	+
	+	* Blog entries about the testfest:
	+	* http://cweiske.de/tagebuch/PHP%20Testfest%20Berlin%202009.htm
	+	* http://till.klampaeckel.de/blog/archives/34-Great-success!.html
	+
	+	=== Würzburg ===
	+	* The PHP user group Wuerzburg decided to start a test fest from 30 May to 31 May.
	+	* Contact - Steffen Hartmann <info@fruityweb.de>
	+
	+	* UG Website: [[http://www.phpug-wuerzburg.de/]]
	+
	+	==== Ireland ====
	+
	+	* Irish PHP User Group (http://php.ie). Contact Jaime Hemmett email: jaime@hemmett.org, David Coallier email: davidc@php.ie
	+
	+	==== Italy ====
	+
	+	=== Cesena ===
	+
	+	* Organized by [[http://www.grusp.it\|GrUSP]] and [[http://www.ideato.it\|ideato srl]]
	+	* Contact: Francesco Trucchia <francesco@cphp.it>
	+	* Dates
	+	* Friday June 19 10-17 (Code dojo TestFest)
	+	* Saturday June 20 10-17 (Pair CodeFest)
	+	* Sunday June 21 10-17 (Deploy TestFest)
	+	* Location: [[http://maps.google.it/maps?f=q&source=s_q&hl=it&geocode=&q=ideato&ie=UTF8&z=8&iwloc=A\|Ideato srl]] - via Quinto Bucci 205, 47023 Cesena (FC).
	+	* More info about the event: [[http://wiki.grusp.it/eventi:phptestfest:riviera2009]]
	+
	+	==== Netherlands ====
	+
	+	* Organized by [[http://phpgg.nl/\|Dutch PHP Usergroup]] with support of [[http://www.microsoft.nl/\|Microsoft]]
	+	* Contact: Stefan Koopmanschap <stefan@phpgg.nl>
	+	* Date and time: Saturday 9 May, 10:30 - 17:00
	+	* Location: Hogeschool Domstad, Utrecht
	+	* More info about the event: [[http://phpgg.nl/testfest2009\|TestFest 2009]]
	+	* Focus on extension: curl
	+
	+	==== Norway ====
	+
	+	===Oslo===
	+
	+	* Organized by [[http://php.no/\|Norway PHP Usergroup]] in association with [[http://redpill-linpro.com/\|Redpill Linpro]]
	+	* Contact: Russell Flynn <russ@redpill-linpro.com>
	+	* Date and time: Tuesday 9th June, 15:30 - 22:00
	+	* Location: Offices of [[http://redpill-linpro.com/\|Redpill Linpro]], Storo, Oslo
	+	* More info about the event: [[http://php.no/wiki/index.php?title=09.06.2009_-_TestFest\|TestFest 2009 Norway]]
	+
	+	==== Peru ====
	+	* Grupo PHP Perú, www.php.org.pe. Contact name: Yannick Warnier, email: info.latino@dokeos.com (Meeting 4/4/9) ([[http://dokeoslead.wordpress.com/2009/04/05/php-testfest-2009-first-try/ \| See report ]])
	+	==== USA ====
	+
	+	* php\|tek (http://tek.mtacon.com/c/s/hackathon) Contact names Stefan Koopmanschap email:stefan@phpgg.nl, Matthew Turland matthew@blueparabola.com
	+	* NYPHP (http://www.nyphp.org) Contact name: Hans Zaunere
	+	* Extensions to test: xmlreader/xmlwriter
	+	* Atlanta PHP (http://atlantaphp.org) Contact name: Ben Ramsey. Subject: DOM
	+	* Nashville PHP (http://www.nashvillephp.org) Contact name: Will Fitch
	+
	+	==== UK ====
	+
	+	* PHP NorthWest. Contact Lorna Jane Mitchell. email: lorna@lornajane.net
	+	* Date and Time: Saturday 9th May, 12 noon until 4pm
	+	* Location: Newton Building, School of Computing, Science and Engineering, Salford University
	+	* Extension to test: SPL
	+	* PHP London. Contact Matt Raines. email: matt.raines@phplondon.org
	+	* Planned date Saturday May 9th - 10:00 to 18:00.
	+	* Location IBM Southbank buildings
	+	* Extension to test: SPL
	+	* Sign up here: http://www.phplondon.org/wiki/May_9th_2009
	+
	+	==== NZ ====
	+
	+	* Web Design Meetup Christchurch. Contact Luke Moynihan. email lukemoynihan@gmail.com
	+	* Date and Time: Saturday 20th June, 10am until 5pm
	+	* Location: Media Suite, Ferrymead, 23 Humphreys Drive, Office 6 (above Kenso)
	+	* Please RSVP
	+
	+
	+	===== Individuals looking for local events =====
	+	This is a log of individual requests to groups participating in TestFest.
	+	* Looking for an event in Bulgaria (Sofia)
	+	===== Available Mentors =====
	+	^ Mentor Name ^ Area of expertise ^ User group to mentor ^ Dates unavailable on-line ^
	+	\| Hannes Magnusson \| Any extension is OK \| Catalonia and Norway \| \|
	+	\| Scott MacVicar \| \| PHPNW \| \|
	+	\| Mikko Koppanen \| \| \| \|
	+	\| Elizabeth Marie Smith \| Anything but XML ext \| In USA - Midwest - NEW YORK \| \|
	+	\| Derick Rethans \| \| \| \|
	+	\| Pierre A. Joye \| \| Munich (with dsop), NL \| \|
	+	\| Felix De Vliegher \| \| Belgium \| \|
	+	\| Igor Feghali \| \| Rio, SP and CEPUG (Brazil) \| \|
	+	\| Ant Phillips \| \| \| \|
	+	\| Zoe Slattery \| Anything core \| London \| 7th - 15th April (likely) \|
	+	\| Raghubansh Kumar \| Anything core, Coding Guidelines \| \| \|
	+	\| Nuno Lopes \| \| Lisbon and Germany \| \|
	+	\| Michael Maclean \| XML exts \| \| 11th to 18th April \|
	+	\| Till Klampaeckel \| \| Berlin, Germany \| \|
	+
	+
	+	===== To do list =====
	+	===== Materials for user groups: =====
	+	* iso images with PHP executable, PHP source, DOCS.
	+	* Linux. Owner:
	+	* Windows. Owner: Pierre
	+	* OSX. Owner:
	+	* A place to put the iso images so that people can download them. Owner:
	+	* VM images with full test environment.
	+	* Windows image. Owner: Pierre
	+	* OSX?
	+	* Linux VirtualBox VM (Ubuntu 32-bit for now): Eric Lee Stewart (http://www.ericstewart.org/tfvm/)
	+	* Unix VirtualBox VM (FreeBSD 32-bit for now): <del>Eric Lee Stewart</del>
	+
	+	===== Locations =====
	+	* Companies prepared to loan their offices on a Saturday?
	+	===== Other Resources =====
	+
	+	==== Internal ====
	+	* [[QA:PHPTLessonsLearned\|Lessons Learned in PHP Testing]]
	+	* [[QA:TestCoverage\|How to get test coverage (Linux)]]
	+	* [[QA:WhatToTest\|More information on what to test]]
	+	* [[QA:Credits\|Crediting test case authors]]
	+	* [[QA:Uploading\|Where to put tests]] (Testfest SVN)
	+	* [[QA:Organisers\|Suggestions & checklist for TestFest organisers]]
	+	* [[qa:testfesttalk\|A reusable talk for the 2009 testfest]]
	+	* [[qa:svnnote\|note for SVN admins]]
	+
	+	==== External ====
	+	* [[http://sebastian-bergmann.de/archives/776-Prepare-for-TestFest.html\|Attendees: how to prepare for TestFest]]
	+	* [[http://sebastian-bergmann.de/archives/777-PHP-Test-Fest-Slides.html\|Basics on phpt slides]]
	+	* [[http://cvs.php.net/viewvc.cgi/php-src/README.TESTING?revision=1.24&view=markup\|Information on run-test.php]]
	+	* [[http://felix.phpbelgium.be/blog/2008/05/22/writing-phpt-tests-on-your-mac/\|Writing phpt tests on Mac OS X]]

abstract_syntax_tree

Anonymous (anonymous@undisclosed.example.com) — 2025-04-03T13:08:43+00:00

2014/08/27 18:08		current
Line 95:		Line 95:

	==== Changes to list() ====		==== Changes to list() ====
		+
		+	> Note: The behavior of ''list($a, $b) = $a'' described below no longer applies. After this RFC was accepted ''list()'' assignments that contain the same variable on the left- and right-hand side have been special cased to ensure the right-hand side always evaluates first. This means that ''list($a, $b) = $a'' continues working as expected.

	''list()'' currently assigns variables right-to-left, the AST implementation will assign them left-to-right instead:		''list()'' currently assigns variables right-to-left, the AST implementation will assign them left-to-right instead:
Line 147:		Line 149:

	==== Auto-vivification order for by-reference assignments ====		==== Auto-vivification order for by-reference assignments ====
		+
		+	> Note: The auto-vivification order for reference assignments has been restored to the old behavior in PHP 7.1. The reason for this is that we found hard to avoid memory safety issues with the new order.

	While by-reference assignments are (CVs notwithstanding) evaluated left-to-right, auto-vivification currently occurs right-to-left. In the AST implementation this will happen left-to-right instead:		While by-reference assignments are (CVs notwithstanding) evaluated left-to-right, auto-vivification currently occurs right-to-left. In the AST implementation this will happen left-to-right instead:

dvcsmigration

Anonymous (anonymous@undisclosed.example.com) — 2025-04-03T13:08:43+00:00

2026/04/23 10:37	current
Line 1:	Line 1:
	+	====== Request for Comments: Migrating to a Distributed Version Control System for PHP ======
	+	* Version: 1.0
	+	* Date: 2010-11-30
	+	* Author: Herman Radtke <hradtke@php.net>
	+	* Status: Under Discussion
	+	* First Published at: http://wiki.php.net/rfc/dvcsmigration
	+
	+	===== Introduction =====
	+	A distributed version control system (DVCS) provides considerable more flexibility than SVN. Key features include a developers ability to interact with the repository without the need for a network connection and the low cost of branching.
	+
	+	The initial discussion for moving to a DVCS began during the SVN conversion process. It was not given much credibility because the SVN conversion was mostly finished. There is also the issue of a learning curve. The workflow for SVN is not that different from CVS. The biggest change in converting to SVN was the syntax change. Converting to a DVCS will introduce both a workflow change and a syntax change. The conversion to a DVCS will have a higher intial cost, but the medium and long term benefits far outweigh this cost.
	+
	+	===== DVCS Options =====
	+
	+	Options are listed in alpha order:
	+	* [[http://bazaar.canonical.com/en/\|Bazaar]]
	+	* [[http://www.git-scm.com/\|git]]
	+	* [[http://mercurial.selenic.com/\|Mercurial]]
	+
	+	===== Migration Path =====
	+	The migration to a DVCS should be a gradual one. Converting a repository of PHP's size is a huge task with lots of moving parts. The SVN conversion was a major disruption to the developer community. The initial steps of migration to a DVCS should focus on the conversion of one section of the existing SVN repository to a DVCS.
	+
	+	This does not mean that the migration plan should be made up as we go along. A solid migration plan for all parts of the existing SVN repository should be in place before the initial migration begins. This includes topics such as karma, authentication and scripts. The community will be encouraged to give feedback as the migration process is underway.
	+
	+	===== Use Cases =====
	+
	+	===== References =====
	+	* http://www.python.org/dev/peps/pep-0374/
	+	* http://book.git-scm.com/index.html
	+
	+

heredoc-with-double-quotes

Anonymous (anonymous@undisclosed.example.com) — 2025-04-03T13:08:43+00:00

2011/04/06 10:59		current
Line 4:		Line 4:
	* Date: 2008-03-22		* Date: 2008-03-22
	* Author: Lars Strojny		* Author: Lars Strojny
-	* Status: [[http://news.php.net/php.zend-engine.cvs/6597\|Accepted]] (Implemented in PHP 5.3)	+	* Status: [[http://news.php.net/php.zend-engine.cvs/6597\|Implemented in PHP 5.3]]
	* Votes: (+6/-4)		* Votes: (+6/-4)
	* Pro: [[http://marc.info/?l=php-internals&m=120679140717702&w=2\|Pierre A. Joye]], [[http://marc.info/?l=php-internals&m=120674698503890&w=2\|Felipe Pena]] , [[http://marc.info/?l=php-internals&m=120636366616273&w=2\|Marcus Boerger]], [[http://marc.info/?l=php-internals&m=120671376003536&w=2\|Gwynne Raskind]], Christopher Jones, Lars Strojny		* Pro: [[http://marc.info/?l=php-internals&m=120679140717702&w=2\|Pierre A. Joye]], [[http://marc.info/?l=php-internals&m=120674698503890&w=2\|Felipe Pena]] , [[http://marc.info/?l=php-internals&m=120636366616273&w=2\|Marcus Boerger]], [[http://marc.info/?l=php-internals&m=120671376003536&w=2\|Gwynne Raskind]], Christopher Jones, Lars Strojny

rounding

Anonymous (anonymous@undisclosed.example.com) — 2025-04-03T13:08:43+00:00

2008/08/24 15:50		current
Line 3:		Line 3:
	* Date: 2008-08-23		* Date: 2008-08-23
	* Author: Christian Seiler <chris_se@gmx.net>		* Author: Christian Seiler <chris_se@gmx.net>
-	* Status: Under Discussion	+	* Status: Implemented
	* First Published at: http://wiki.php.net/rfc/rounding		* First Published at: http://wiki.php.net/rfc/rounding

Line 274:		Line 274:
	in a platform-independent way. The GNU C library offers the _FPU_SETCW and		in a platform-independent way. The GNU C library offers the _FPU_SETCW and
	_FPU_GETCW macros in fpu_control.h while on Windows Systems a function named		_FPU_GETCW macros in fpu_control.h while on Windows Systems a function named
-	_controlfp is available for this job.	+	_controlfp is available for this job. FreeBSD provides fpsetprec() and other
		+	Operating Systems that run on x86 require inline assembly.

	Please note that zend_strtod() is also affected by this problem: On systems		Please note that zend_strtod() is also affected by this problem: On systems
Line 394:		Line 395:
	==== Building an abstraction layer for FP control register manipulation ====		==== Building an abstraction layer for FP control register manipulation ====

-	In a first step, my patch introduces 3 macros:	+	See http://www.christian-seiler.de/projekte/fpmath/ for further information
		+	on how to ensure double precision on different architectures, operating
		+	systems and with different compilers.

-	* _ZEND_FPU_CW_DECLARE	+	This proposal proposes to wrap the above abstraction into the following
-	* _ZEND_FPU_CW_SET	+	macros:
-	* _ZEND_FPU_CW_RESTORE	+

-	The DECLARE macro declares certain necessary variables, the SET macro modifies	+	* ZEND_FLOAT_DECLARE
-	the FPU control word so that double precision is used for calculation and	+	* ZEND_FLOAT_ENSURE()
-	RESTORE restores the previous state of the control word. The following example	+	* ZEND_FLOAT_RESTORE()
-	illustrates how these macros are to be used:	+	* ZEND_FLOAT_RETURN(val)

-	<code c>	+	These will be defined in Zend/zend_float.h.
-	double somefunction (double val)	+
-	{	+
-	_ZEND_FPU_CW_DECLARE;	+
-	double foo;	+
-		+
-	_ZEND_FPU_CW_SET;	+
-		+
-	/* some calculations... */	+
-	foo = val / 100.0;	+
-		+
-	*/ ... /*	+
-		+
-	_ZEND_FPU_CW_RESTORE;	+
-	return foo;	+
-	}	+
-	</code>	+
-		+
-	These macros expand to the correct versions for each platform or to NOPs if	+
-	the method for the corresponding platform could not be determined.	+

	==== Fix of zend_strtod ====		==== Fix of zend_strtod ====
Line 440:		Line 423:
	different results.		different results.

-	For this reason, my patch also fixes zend_strtod() by adding the _ZEND_FPU_CW	+	For this reason, my patch also fixes zend_strtod() by adding the proposed
	macros to the function. Then, C and PHP will yield the same results on all		macros to the function. Then, C and PHP will yield the same results on all
	platforms (that support IEEE 754 arithmetics anyway).		platforms (that support IEEE 754 arithmetics anyway).
Line 451:		Line 434:
	=== Usage of FP control word manipulation ===		=== Usage of FP control word manipulation ===

-	The round function uses the new _ZEND_FPU_CW macros in order to ensure double	+	The round function uses the new ZEND_FLOAT macros in order to ensure double
	precision arithmetics within the function body. This will make sure the final		precision arithmetics within the function body. This will make sure the final
	division works properly.		division works properly.
Line 525:		Line 508:
	==== Patch =====		==== Patch =====

-	The patch is available under	+	The patch was already applied to PHP_5_3 and HEAD.
-	[[http://www.christian-seiler.de/temp/php/2008-08-23-rounding/rounding-5.3-1.patch]].	+
-	It applies against the current CVS branch of 5.3, porting it to HEAD should	+
-	be extremely trivial (since this only affects math-related stuff).	+
-		+
-	I tested the patch under Linux 32 bit x86, Linux 64 bit x86_64 and Windows	+
-	32 bit x86. Please note that MinGW does not define _controlfp_s but does	+
-	define _controlfp. Thus I added a conditional ifdef to use _controlfp instead	+
-	if _controlfp_s is not present. This is not relevant now but may be relevant	+
-	when CMake is used as build system for PHP and thus PHP starts to support	+
-	MinGW.	+

-	The _ZEND_FPU_CW macros are currently defined in zend_strtod.h, but there may	+	I tested the patch under Linux 32 bit x86, Linux 64 bit x86_64, Windows
-	be a better place for that. Also, the configure checks for those makros are	+	32 bit x86 and FreeBSD 32 bit x86. Additionally, the macros themselves were
-	currently in ext/standard/config.{m4,w32} while they are probably better	+	tested on various platforms (see the above link for details).
-	located somewhere else.	+

	===== Comparison with the 2004 proposal =====		===== Comparison with the 2004 proposal =====
Line 599:		Line 571:
	===== Changelog =====		===== Changelog =====

		+	* 2008-12-02 Christian Seiler: Updated to current situation
	* 2008-08-23 Christian Seiler: Created RFC		* 2008-08-23 Christian Seiler: Created RFC

shortsyntaxforarrays

Anonymous (anonymous@undisclosed.example.com) — 2025-04-03T13:08:43+00:00

2011/08/06 19:28		current
Line 75:		Line 75:
	===== Conclusion =====		===== Conclusion =====

-	This patch will not be accepted because slight majority of the core developers voted against. Though if you take a accumulated mean between core developers and userland votes seems to show the opposite it would be irresponsible to submit a patch witch is not supported or maintained in the long run.	+	This patch has been merged in PHP 5.4.0 and trunk.
	===== Discussion on the List =====		===== Discussion on the List =====

trailing-comma-function-args

Anonymous (anonymous@undisclosed.example.com) — 2025-04-03T13:08:43+00:00

2013/03/25 18:28		current
Line 3:		Line 3:
	* Date: 2013-02-19		* Date: 2013-02-19
	* Author: Sara Golemon <pollita@php.net>		* Author: Sara Golemon <pollita@php.net>
-	* Status: Voting Open	+	* Status: Rejected
	* First Published at: http://wiki.php.net/rfc/trailing-comma-function-args		* First Published at: http://wiki.php.net/rfc/trailing-comma-function-args

uniform_variable_syntax

Anonymous (anonymous@undisclosed.example.com) — 2025-04-03T13:08:43+00:00

2014/07/30 00:03		current
Line 2:		Line 2:
	* Date: 2014-05-31		* Date: 2014-05-31
	* Author: Nikita Popov <nikic@php.net>		* Author: Nikita Popov <nikic@php.net>
-	* Status: Accepted (for PHP 7)	+	* Status: Implemented (in PHP 7)
	* Discussion: http://markmail.org/message/mr4ihbubfbdxygci		* Discussion: http://markmail.org/message/mr4ihbubfbdxygci

Line 276:		Line 276:
	</code>		</code>

-	This change is backwards incompatible (with low practical impact), which is the reason why this RFC targets PHP 6.	+	This change is backwards incompatible (with low practical impact), which is the reason why this RFC targets PHP 7.
	However it is always possible to recreate the old behavior by explicitly using braces:		However it is always possible to recreate the old behavior by explicitly using braces:

Line 285:		Line 285:
	</code>		</code>

-	This syntax will have guaranteed same behavior in both PHP 5 and PHP 6.	+	This syntax will have guaranteed same behavior in both PHP 5 and PHP 7.

	==== Newly added and generalized syntax ====		==== Newly added and generalized syntax ====
Line 357:		Line 357:
	occurrence of ''%%$loader[0]::$loader[1]($className)%%'' in the Doctrine class loader will be affected by this change.		occurrence of ''%%$loader[0]::$loader[1]($className)%%'' in the Doctrine class loader will be affected by this change.
	This occurrence must be replaced with ''%%$loader[0]::{$loader[1]}($className)%%'' to achieve compatibility with both		This occurrence must be replaced with ''%%$loader[0]::{$loader[1]}($className)%%'' to achieve compatibility with both
-	PHP 5 and PHP 6.	+	PHP 5 and PHP 7.

	The latter change turns currently valid syntax into a parse error. Expressions like ''%%global $$foo->bar%%'' are no		The latter change turns currently valid syntax into a parse error. Expressions like ''%%global $$foo->bar%%'' are no
	longer valid and ''%%global ${$foo->bar}%%'' must be used instead.		longer valid and ''%%global ${$foo->bar}%%'' must be used instead.

-	As these changes only apply to some very rarely used syntax, the breakage seems acceptable for PHP 6.	+	As these changes only apply to some very rarely used syntax, the breakage seems acceptable for PHP 7.

	===== Open issues =====		===== Open issues =====

euk1

Anonymous (anonymous@undisclosed.example.com) — 2025-04-03T13:08:43+00:00

2011/11/16 01:42		current
Line 71:		Line 71:

	==== Upgrading ====		==== Upgrading ====
-	First, make your changes to the [[http://github.com/pear/pearweb\|pearweb]] source.	+	Make your changes to the [[http://github.com/pear/pearweb\|pearweb]] source, then follow [[https://github.com/pear/pearweb/blob/master/README\|the README]] steps.
-		+
-	Second, ensure that you have deployed and tested the changes on [[sgrv1]]	+
-	pear upgrade -f package.xml	+
-	or a specific area:	+
-	pear upgrade -f package-pepr.xml	+
-		+
-	Once you have tested your changes, you can proceed.	+
-		+
-	Third, make the appropriate pearweb release and push it to pear.php.net. Be sure to update the relevant package_*.php file and generate the new package.xml	+
-		+
-	$ vim package_pepr.php	+
-	$ php package_pepr.php make	+
-	$ git commit -m "Release preparation" package-pepr.xml package_pepr.php	+
-		+
-	Join the #pear IRC channel on efnet, and discuss the changes you are about to make.	+
-		+
-	Next:	+
-	$ ssh pear.php.net	+
-	$ sudo pear upgrade pearweb	+
-		+
-	or	+
-	$ sudo pear upgrade pearweb_pepr	+
-		+
-	Apply any mysql, crontab changes manually.	+
-		+
-	Verify that http://pear.php.net/ is still functioning and update this changelog.	+

	===== PHAR =====		===== PHAR =====

munin

Anonymous (anonymous@undisclosed.example.com) — 2025-04-03T13:08:43+00:00

2011/04/06 10:59		current
Line 17:		Line 17:
	- Install the ''munin-node'' application. Most modern UNIX-like operating systems ship with it. For boxes with CentOS, make sure that [[http://wiki.centos.org/AdditionalResources/Repositories/RPMForge\|rpmforge]] is being used.		- Install the ''munin-node'' application. Most modern UNIX-like operating systems ship with it. For boxes with CentOS, make sure that [[http://wiki.centos.org/AdditionalResources/Repositories/RPMForge\|rpmforge]] is being used.
	- Allow ''sp1'' to connect to the node by adding an ''allow 66\.249\.27\.150'' line to the configuration file for ''munin-node''.		- Allow ''sp1'' to connect to the node by adding an ''allow 66\.249\.27\.150'' line to the configuration file for ''munin-node''.
-	- Depending on the machine it may be necessary to all access to port 4949 from the outside. Use ''iptables -I INPUT -p tcp --dport 4949 --src 66.249.27.150 -j ACCEPT'' for this.	+	- Depending on the machine it may be necessary to allow access to port 4949 from the outside. Use ''iptables -I INPUT -p tcp --dport 4949 --src 66.249.27.150 -j ACCEPT'' for this.
	- Let Martin (mj) know once the node is set up so that it can be added to the server's list of clients.		- Let Martin (mj) know once the node is set up so that it can be added to the server's list of clients.

php52

Anonymous (anonymous@undisclosed.example.com) — 2025-04-03T13:08:43+00:00

2008/07/01 20:27		current
Line 3:		Line 3:
	===== Timetable =====		===== Timetable =====

-	no timetable for a 5.2.7 release has been defined	+	- PHP 5.2.7 RC3 - October 30th

	===== Todo Items =====		===== Todo Items =====
Line 11:		Line 11:

	==== Open for Discussion ====		==== Open for Discussion ====
-

php54

Anonymous (anonymous@undisclosed.example.com) — 2025-04-03T13:08:43+00:00

2012/03/23 05:37		current
Line 13:		Line 13:
	- beta2 - October 20 2011 DONE		- beta2 - October 20 2011 DONE
	- 5.4.0 - Released on March 1, 2012		- 5.4.0 - Released on March 1, 2012
-	- 5.4.1 RC1 - March 29, 2012 (pushed back one week)	+	- 5.4.1 - Released on April 26, 2012
		+	- 5.4.2 RC1 - Planned on May 10, 2012
	Original proposal: [[http://markmail.org/message/3ddcqbu4mpan5ypk\|here]]		Original proposal: [[http://markmail.org/message/3ddcqbu4mpan5ypk\|here]]
-
	===== TODO Items =====		===== TODO Items =====

gitfaq

Anonymous (anonymous@undisclosed.example.com) — 2025-04-03T13:08:43+00:00

2021/04/06 08:00		current
Line 282:		Line 282:
	===== Github Pull Requests =====		===== Github Pull Requests =====

-	There is a mailing list called <git-pulls@lists.php.net>. All pull requests created for the [[http://github.com/php\|github.com/php]] user will go to this mailing list.	+	As php-src is now hosted on GitHub, you can either use GitHub's UI to merge pull requests, or merge it locally and push it upstream. If you rebase or squash the commits, you can add "Closes GH-1234" to the description of the commit to auto-close the PR.

-	If you have commit rights to a mirrored PHP repository you can pull the requests and push it to the official repositories.	+	See the pull request related sections of the [[gitworkflow#reviewing_and_closing_pull_requests\|Git Workflow]] document for more information.

-	You cannot use the Merge button on GitHub for that. The PHP Organization on GitHub will not accept contributors. It's only for mirroring!	+	There is also a mailing list called <git-pulls@lists.php.net>. All pull requests created for the [[http://github.com/php\|github.com/php]] user will go to this mailing list. The mailing list is less noisy than watching all pull request activity.
-		+
-	See the pull request related sections of the [[gitworkflow#reviewing_and_closing_pull_requests\|Git Workflow]] document for more information.	+

	===== Commit Mails =====		===== Commit Mails =====

newtranslation

Anonymous (anonymous@undisclosed.example.com) — 2025-04-03T13:08:43+00:00

2008/05/11 00:50		current
Line 8:		Line 8:
	* Update CVSROOT/modules		* Update CVSROOT/modules
	* Update CVSROOT/loginfo		* Update CVSROOT/loginfo
		+	* Update CVSROOT/avail (in a couple places)
	* Add {lang} to docweb for revcheck		* Add {lang} to docweb for revcheck
	* Add {lang} to phpweb/includes/languages.inc as INACTIVE		* Add {lang} to phpweb/includes/languages.inc as INACTIVE
	* Add the new {lang} mailing list to our super secret gmail doc account (user php.doc.lists)		* Add the new {lang} mailing list to our super secret gmail doc account (user php.doc.lists)

pecldocs

Anonymous (anonymous@undisclosed.example.com) — 2025-04-03T13:08:43+00:00

2009/03/24 17:14		current
Line 17:		Line 17:
	</code>		</code>

-	This will create a directory named 'tmp' for the extension named 'extname' which will be full of documentation skeletons. Reflection is used to make guesses about the extension, like for classes, methods, functions, constants, parameters, version information, etc. but this information will not be fully correct. Please go through and edit each XML file by updating this information and adding documentation.	+	This will create a directory named 'tmp' that will contain documentation skeletons for the 'pecl' extension named 'extname'. Reflection is used to make guesses about the extension, like for classes, methods, functions, constants, parameters, version information, etc. but this information will not be fully correct. Please go through and edit each XML file by updating this information and adding documentation.

	* Read the Validating Changes section of the [[doc:scratchpad:howto\|PHP Documentation HOWTO]].		* Read the Validating Changes section of the [[doc:scratchpad:howto\|PHP Documentation HOWTO]].

install

Anonymous (anonymous@undisclosed.example.com) — 2025-04-03T13:08:43+00:00

2026/04/23 10:37	current
Line 1:	Line 1:
	+	=== Installation section rewrite ===
	+	This task involves rewriting and restructuring the installation section of the PHP Manual. This is a large task so may be broken up into smaller parts.

	+	The section in question:
	+	* URL: http://php.net/install
	+	* Source: http://cvs.php.net/viewvc.cgi/phpdoc/en/install/
	+
	+	=== Problems ===
	+	This section has become outdated. For example, we highlight Apache 2.0.x and only include a few notes about Apache 2.2.x. There are a ton of user notes from confused users that should be addressed. The IIS/PWS section is outdated. The Mac section is outdated. Other parts, outdated.
	+
	+	=== TODO ===
	+	Start work on this one section at a time.

per-release-all

Anonymous (anonymous@undisclosed.example.com) — 2025-04-03T13:08:43+00:00

2011/06/20 03:41		current
Line 9:		Line 9:
	$ cd svn/phpdoc/trunk		$ cd svn/phpdoc/trunk
	$ xmllint --output tmp.xml --noent doc-base/install-unix.xml && phd -d ./tmp.xml -P PHP -f bigxhtml -o ./ && lynx -dump -nolist -justify -display_charset UTF-8 ./php-bigxhtml.html > INSTALL		$ xmllint --output tmp.xml --noent doc-base/install-unix.xml && phd -d ./tmp.xml -P PHP -f bigxhtml -o ./ && lynx -dump -nolist -justify -display_charset UTF-8 ./php-bigxhtml.html > INSTALL
-	$ xmllint --output tmp.xml --noent doc-base/install-windows.xml && phd -d ./tmp.xml -P PHP -f bigxhtml -o ./ && lynx -dump -nolist -justify -display_charset UTF-8 ./php-bigxhtml.html > install.txt	+	$ xmllint --output tmp.xml --noent doc-base/install-win.xml && phd -d ./tmp.xml -P PHP -f bigxhtml -o ./ && lynx -dump -nolist -justify -display_charset UTF-8 ./php-bigxhtml.html > install.txt
	</code>		</code>

per-release-major

Anonymous (anonymous@undisclosed.example.com) — 2025-04-03T13:08:43+00:00

2026/04/23 10:37	current
Line 1:	Line 1:
	+	==== TODO for every major (X.0.0) PHP Release ====
	+
	+	== Check version information ==
	+	Since each major PHP version is stored in the version files, this is taken into account at this time.
	+
	+	== Consider removing old information ==
	+	For example, is PHP 3 still relevant? How about PHP 4? If using version specific tagging, does the build system need adjusting?
	+
	+	== Update PHP version specific info ==
	+	The following manual pages contain version specific information that needs updating:
	+	* [[http://cvs.php.net/viewvc.cgi/phpdoc/en/appendices/about.xml?view=log\|appendices/about.xml]]

release

Anonymous (anonymous@undisclosed.example.com) — 2025-04-03T13:08:43+00:00

2008/12/08 21:59		current
Line 25:		Line 25:


-	===== PHP 6 =====	+	===== PHP 5.3.x =====
	==== Thread Safe ====		==== Thread Safe ====
	<code bash>		<code bash>
-	--enable-snapshot-build --enable-debug-pack --without-static-icu --with-pdo-oci=C:\php-sdk\oracle\instantclient10\sdk,shared --with-oci8=C:\php-sdk\oracle\instantclient10\sdk,shared --with-oci8-11g=C:\php-sdk\oracle\instantclient11\sdk,shared	+	configure.bat --enable-snapshot-build --enable-debug-pack --with-pdo-oci=C:\php-sdk\oracle\instantclient10\sdk,shared --with-oci8=C:\php-sdk\oracle\instantclient10\sdk,shared --with-oci8-11g=C:\php-sdk\oracle\instantclient11\sdk,shared
	</code>		</code>

	==== Non Thread Safe ====		==== Non Thread Safe ====
	<code bash>		<code bash>
-	--enable-snapshot-build --enable-debug-pack --without-static-icu --disable-zts --disable-isapi --disable-nsapi --with-pdo-oci=C:\php-sdk\oracle\instantclient10\sdk,shared --with-oci8=C:\php-sdk\oracle\instantclient10\sdk,shared --with-oci8-11g=C:\php-sdk\oracle\instantclient11\sdk,shared	+	configure.bat --enable-snapshot-build --enable-debug-pack --disable-zts --disable-isapi --disable-nsapi --with-pdo-oci=C:\php-sdk\oracle\instantclient10\sdk,shared --with-oci8=C:\php-sdk\oracle\instantclient10\sdk,shared --with-oci8-11g=C:\php-sdk\oracle\instantclient11\sdk,shared
	</code>		</code>

-	===== PHP 5.3.x =====	+	===== PHP 6 =====
	==== Thread Safe ====		==== Thread Safe ====
	<code bash>		<code bash>
-	--enable-snapshot-build --enable-debug-pack --with-pdo-oci=C:\php-sdk\oracle\instantclient10\sdk,shared --with-oci8=C:\php-sdk\oracle\instantclient10\sdk,shared --with-oci8-11g=C:\php-sdk\oracle\instantclient11\sdk,shared	+	configure.bat --enable-snapshot-build --enable-debug-pack --without-static-icu --with-pdo-oci=C:\php-sdk\oracle\instantclient10\sdk,shared --with-oci8=C:\php-sdk\oracle\instantclient10\sdk,shared --with-oci8-11g=C:\php-sdk\oracle\instantclient11\sdk,shared
	</code>		</code>

	==== Non Thread Safe ====		==== Non Thread Safe ====
	<code bash>		<code bash>
-	--enable-snapshot-build --enable-debug-pack --disable-zts --disable-isapi --disable-nsapi --with-pdo-oci=C:\php-sdk\oracle\instantclient10\sdk,shared --with-oci8=C:\php-sdk\oracle\instantclient10\sdk,shared --with-oci8-11g=C:\php-sdk\oracle\instantclient11\sdk,shared	+	configure.bat --enable-snapshot-build --enable-debug-pack --without-static-icu --disable-zts --disable-isapi --disable-nsapi --with-pdo-oci=C:\php-sdk\oracle\instantclient10\sdk,shared --with-oci8=C:\php-sdk\oracle\instantclient10\sdk,shared --with-oci8-11g=C:\php-sdk\oracle\instantclient11\sdk,shared
	</code>		</code>
-	The box is 64 bit - so 64 bit builds are possible in the future.	+

migration

Anonymous (anonymous@undisclosed.example.com) — 2025-04-03T13:08:43+00:00

2010/10/05 10:24		current
Line 31:		Line 31:
	* <del>[[pear:packages:Event_Dispatcher]]</del> (unmaintained, new release, doconnor)		* <del>[[pear:packages:Event_Dispatcher]]</del> (unmaintained, new release, doconnor)
	* [[pear:packages:File_DICOM]]		* [[pear:packages:File_DICOM]]
-	* [[pear:packages:File_DNS]]	+	* <del>[[pear:packages:File_DNS]]</del>
	* [[pear:packages:File_Find]]		* [[pear:packages:File_Find]]
	* [[pear:packages:File_Fstab]]		* [[pear:packages:File_Fstab]]
Line 46:		Line 46:
	* [[pear:packages:HTML_Safe]]		* [[pear:packages:HTML_Safe]]
	* [[pear:packages:HTML_Select]]		* [[pear:packages:HTML_Select]]
-	* [[pear:packages:HTML_Select_Common]]	+	* <del>[[pear:packages:HTML_Select_Common]]</del>
	* <del>[[pear:packages:HTML_Table_Matrix]]</del> (new release)		* <del>[[pear:packages:HTML_Table_Matrix]]</del> (new release)
	* [[pear:packages:HTML_Template_Xipe]]		* [[pear:packages:HTML_Template_Xipe]]
	* [[pear:packages:HTTP_Header]]		* [[pear:packages:HTTP_Header]]
-	* [[pear:packages:HTTP_Server]]	+	* <del>[[pear:packages:HTTP_Server]]</del>
	* [[pear:packages:HTTP_SessionServer]]		* [[pear:packages:HTTP_SessionServer]]
	* <del>[[pear:packages:HTTP_Upload]]</del> (new release)		* <del>[[pear:packages:HTTP_Upload]]</del> (new release)
Line 75:		Line 75:
	* [[pear:packages:Math_Finance]]		* [[pear:packages:Math_Finance]]
	* [[pear:packages:Math_Histogram]]		* [[pear:packages:Math_Histogram]]
-	* [[pear:packages:Math_Integer]]	+	* <del>[[pear:packages:Math_Integer]]</del>
	* <del>[[pear:packages:Math_Matrix]]</del>		* <del>[[pear:packages:Math_Matrix]]</del>
	* [[pear:packages:Math_Polynomial]]		* [[pear:packages:Math_Polynomial]]

numbers_words

Anonymous (anonymous@undisclosed.example.com) — 2025-04-03T13:08:43+00:00

2008/11/26 13:34		current
Line 22:		Line 22:
	Do you speak any of:		Do you speak any of:

-	* Bulgarian	+	* <del>Bulgarian</del>
	* Czech		* Czech
	* Danish		* Danish

opendocument

Anonymous (anonymous@undisclosed.example.com) — 2025-04-03T13:08:43+00:00

2011/08/24 06:29		current
Line 3:		Line 3:
	^ Current version: \| 0.2.0 (alpha) was released on 2009-07-28 \|		^ Current version: \| 0.2.0 (alpha) was released on 2009-07-28 \|
	^ Source repository: \| https://github.com/pear/OpenDocument \|		^ Source repository: \| https://github.com/pear/OpenDocument \|
-	^ Bug tracker: \| http://pear.php.net/bugs/search.php?cmd=display&package_name[]=OpenDocument \|	+	^ Bug tracker: \| [[http://pear.php.net/bugs/search.php?cmd=display&package_name[]=OpenDocument]] \|

	OpenDocument is a package to create, read and update [[http://en.wikipedia.org/wiki/OpenDocument\|Open Document Format]] files. ODF is an XML-based file format for office documents such as spreadsheets, charts, presentations and word processing documents, with a standardised specification as an //OASIS Committee Specification// ([[http://docs.oasis-open.org/office/v1.2/OpenDocument-v1.2.html\|v.1.2]]) and //ISO/IEC 26300:2006// (v.1.0 with v.1.1 currently a Draft Amendment). The former specification is the most recently updated, is publicly available, and is the one we're working from for this PEAR package.		OpenDocument is a package to create, read and update [[http://en.wikipedia.org/wiki/OpenDocument\|Open Document Format]] files. ODF is an XML-based file format for office documents such as spreadsheets, charts, presentations and word processing documents, with a standardised specification as an //OASIS Committee Specification// ([[http://docs.oasis-open.org/office/v1.2/OpenDocument-v1.2.html\|v.1.2]]) and //ISO/IEC 26300:2006// (v.1.0 with v.1.1 currently a Draft Amendment). The former specification is the most recently updated, is publicly available, and is the one we're working from for this PEAR package.

documentation

Anonymous (anonymous@undisclosed.example.com) — 2025-04-03T13:08:43+00:00

2008/11/17 05:30		current
Line 23:		Line 23:


-	'''Items which I don't know where to place:'''	+	==== Items which I don't know where to place: ====
	- <del>Decide on a move to a set/book structure, and where the sets/books are separated at (categories/collectives, or individual packages)</del> - done, cweiske		- <del>Decide on a move to a set/book structure, and where the sets/books are separated at (categories/collectives, or individual packages)</del> - done, cweiske
	- <del>what, semantically is involved in this - docbook reference</del> - done, cweiske		- <del>what, semantically is involved in this - docbook reference</del> - done, cweiske
Line 38:		Line 37:
	This is a start at a conversion script, which will handle almost all of step 4 above.		This is a start at a conversion script, which will handle almost all of step 4 above.

-	'''Execution examples:'''	+	==== Execution examples ====

-	Convert all files $	+	Convert all files
	<code>./peardoc_conversion.sh</code>		<code>./peardoc_conversion.sh</code>

-	Convert one file $	+	Convert one file
	<code>./peardoc_conversion.sh peardoc/en/chapters/installation/shared.xml</code>		<code>./peardoc_conversion.sh peardoc/en/chapters/installation/shared.xml</code>

todos

Anonymous (anonymous@undisclosed.example.com) — 2025-04-03T13:08:43+00:00

2012/05/21 21:08		current
Line 15:		Line 15:
	* Package as a single file (like run-tests.php)		* Package as a single file (like run-tests.php)
	* Add a test using --disable-all and check that it runs (not parallel, which will always need pcntl()...DONE		* Add a test using --disable-all and check that it runs (not parallel, which will always need pcntl()...DONE
		+	* Code review
		+	* Should rtTestTaskGroup and rtPhpTestGroup be merged?
		+	* Check memory usage

progress

Anonymous (anonymous@undisclosed.example.com) — 2025-04-03T13:08:43+00:00

2014/01/20 16:47		current
Line 128:		Line 128:
	\| Implement mechanism to ensure PECL extensions fail to compile if not updated for new API \| not started \|		\| Implement mechanism to ensure PECL extensions fail to compile if not updated for new API \| not started \|
	\| Do smart platform recognition and ermove the size_t/int64 configure options \| done \|		\| Do smart platform recognition and ermove the size_t/int64 configure options \| done \|
-	\| Develop a tutorial (and possibly tools) for PECL extensions \| not started \|	+	\| Develop a tutorial (and possibly tools) for PECL extensions \| in progress \|

53

Anonymous (anonymous@undisclosed.example.com) — 2025-04-03T13:08:43+00:00

2009/06/26 02:29		current
Line 1:		Line 1:
	====== PHP 5.3 upgrading notes ======		====== PHP 5.3 upgrading notes ======
	* This document has been removed in favor of [[http://cvs.php.net/viewvc.cgi/php-src/UPGRADING?view=markup&pathrev=PHP_5_3\|UPGRADING]] and will eventually live in the PHP Manual (see below)		* This document has been removed in favor of [[http://cvs.php.net/viewvc.cgi/php-src/UPGRADING?view=markup&pathrev=PHP_5_3\|UPGRADING]] and will eventually live in the PHP Manual (see below)
-	* The 5.3.0 upgrade guide can be seen here: [[http://php.net/migration53]]	+	* The 5.3.0 upgrade guide can be seen here: [[http://docs.php.net/migration53]]
-	* The 5.2.0 upgrade guide can be seen here: [[http://php.net/migration52]]	+	* The 5.2.0 upgrade guide can be seen here: [[http://docs.php.net/migration52]]
-	* The 5.1.0 upgrade guide can be seen here: [[http://php.net/migration51]]	+	* The 5.1.0 upgrade guide can be seen here: [[http://docs.php.net/migration51]]

refstruct-progress

Anonymous (anonymous@undisclosed.example.com) — 2025-04-03T13:08:43+00:00

2008/03/21 20:36		current
Line 6:		Line 6:

	===== Progress =====		===== Progress =====
-	* ar (?)	+	* <del>ar</del>
	* <del>bg</del>		* <del>bg</del>
	* ca (?)		* ca (?)
Line 13:		Line 13:
	* <del>de</del>		* <del>de</del>
	* el		* el
-	* es	+	* <del>es</del>
	* fi		* fi
-	* fr	+	* <del>fr</del>
	* he		* he
	* hk		* hk
	* hu		* hu
	* <del>id</del>		* <del>id</del>
-	* it	+	* <del>it</del>
	* <del>ja</del>		* <del>ja</del>
	* kr		* kr
Line 26:		Line 26:
	* nl		* nl
	* no		* no
-	* pl	+	* <del>pl</del>
	* pt		* pt
	* <del>pt-br</del>		* <del>pt-br</del>
-	* ro	+	* <del>ro</del>
	* <del>ru</del>		* <del>ru</del>
	* sk		* sk

bindlib

Anonymous (anonymous@undisclosed.example.com) — 2025-04-03T13:08:43+00:00

2008/04/30 13:27		current
Line 1:		Line 1:
	====== Bindlib ======		====== Bindlib ======

-	This is a fork of [[http://www.isc.org/index.pl?/sw/bind/index.php\|bind]] uses exclusively for domain resolving for PHP on Windows. The source for this is located in PHP CVS and has no versioning. Changes are made to patch known security issues or to fix windows compiler problems only.	+	This is a fork of [[http://www.isc.org/index.pl?/sw/bind/index.php\|bind]] used exclusively for domain resolving for PHP on Windows. The source for this is located in PHP CVS and has no versioning. Changes are made to patch known security issues or to fix windows compiler problems only.

tidy

Anonymous (anonymous@undisclosed.example.com) — 2025-04-03T13:08:43+00:00

2013/01/29 11:32		current
Line 14:		Line 14:

	where x.y.z defines the version, vcversion which Visual C++ has been used and architecture defines whether the build is for win32 or win64.		where x.y.z defines the version, vcversion which Visual C++ has been used and architecture defines whether the build is for win32 or win64.
		+
		+	For PHP suitable sources and up-to-date information see [[https://github.com/winlibs/libtidy]].

	===== Building LibTidy =====		===== Building LibTidy =====

20070513

Anonymous (anonymous@undisclosed.example.com) — 2025-04-03T13:08:43+00:00

2008/11/09 03:03		current
Line 63:		Line 63:
	* Why so many dead proposals?		* Why so many dead proposals?
	* Some sort of Design Guide to go along with coding standards		* Some sort of Design Guide to go along with coding standards
		+
		+	===== Minutes =====
		+	These are the minutes from the May 13th PEAR Group meeting, if you have any questions feel free to send us an email (pear-group at php.net).
		+
		+	These minutes will be posted on the pear website at a latter date.
		+	-josh
		+	--------
		+
		+	===Attending===
		+
		+	* Arnaud Limbourg (arnaud)
		+	* Christian Weiske (cweiske)
		+	* Helgi Pormar (helgi)
		+	* Joshua Eichorn (jeichorn)
		+	* Lukas Smith (lsmith)
		+
		+	* Pear President Greg Beaver (cellog)
		+
		+	===Not Attending===
		+	* David Coallier (davidc)
		+	* Martin Jansen (mj)
		+
		+
		+	arnaud and lsmith left the meeting after the first hour
		+	cellog arrived 2 hours into the meeting
		+
		+	==Discussion==
		+
		+	Agenda for meeting is at: [[MeetingAgenda20070513]]
		+
		+	===Making decisions (non-policy)===
		+	Decisions are made by consensus (http://en.wikipedia.org/wiki/Consensus), any member can call for a vote if they disagree, voting has to be seconded
		+	If the entire pear group is available in a meeting voting can be done during the meeting otherwise an email vote is done
		+	Email votes should be a minmum of 7 days (or until all votes are cast) with sponsor of vote having the ability to set a longer time
		+	Email votes should be managed by any PEAR Group momber other then the membe rhwo called for the vote
		+	All Votes are final
		+
		+	Community notification will be on a case by case basis depending on the importance of the decision, with a minimum of an email to pear-dev
		+	A pear group member can call for a pear group vote to decide an issue by full pear election
		+
		+	====action items====
		+	* jeichorn - post this wording to the group for review
		+	* helgi - find a place on the website for items like this
		+
		+	===Community Notification, increasing transparency===
		+	Minutes will be posted from each meeting to a new section of the website with notifications to pear-dev and website front page
		+
		+	====action items====
		+	* arnaud - sending current thoughts to the rest of the pear group and making sure everyone else is fine with our solution
		+	* helgi - creating a new section on the website to post minutes too
		+	* jeichorn - post minutes from this meeting
		+
		+	===Vice President===
		+	candidates:
		+	* jeichorn
		+
		+	====action items====
		+	* postponing until after the runoff election to give winner a chance to be a candidate if they want
		+
		+	===Meeting Schedule===
		+	Meet every 2 weeks, need at least 3 members present to have a meeting
		+
		+	====action items====
		+	* helgi - schedule another meeting next week
		+
		+	===Constitution updates===
		+	Cover pear group tie for last position runoff
		+	Cover winning president less then 50% of votes
		+	Schedule election on new wording within a month
		+
		+	====action items====
		+	* cweiske will work on the language of the amendment
		+
		+	===Defining Collectives===
		+	Goal is for each collective to have at least 5 packages
		+	Review with pear group, and then entire community
		+	http://wiki.bluga.net/pear/collectives
		+	We will need to create a guide to help collectives get started
		+
		+	====action items====
		+	* jeichorn- send out url and ask for feedback
		+	* jeichorn- put back on agenda for next meeting
		+
		+	===Managing ongoing tasks===
		+	Were just going to leave this to whoever has time, we seem to be covering things well right now
		+
		+	====action items====
		+	* helgi - add a feature request for a cron check on limbo account approvals http://pear.php.net/bugs/bug.php?id=11026
		+
		+	===RFC Process===
		+	http://wiki.bluga.net/pear/rfc
		+	Working off current proposal
		+	Need to look at when to do a full pear vote
		+
		+	====action items====
		+	* jeichorn - get review from rest of the pear group
		+	* cweiske - create RFC section of the manual
		+
		+	Skip Items #9 to #11 on agenda
		+
		+	===Licensing in general===
		+	were not going to push any license on the approved list, but we will discourage the php license on none extension code
		+	recommendations about handling multiple copyright owners on code, and license compatibility would be good
		+	recommend GFDL for the manual
		+
		+	====action items====
		+	* cellog - search for legal advice to help review current licenses
		+
		+	===Mozilla Code and the MPL===
		+	We don't want another license in PEAR it's hard enough as it stands
		+
		+	====action items====
		+	* cellog - contact and mozilla and work out their concerns
		+	* jeichorn - find original pear-dev email
		+
		+	===Review Suggestions===
		+	Need to cover more, with the rest of the group
		+	spent some time covering a new include proposal from cellog for pear2 that would solve include_path concerns
		+
		+	Prop Summary:
		+	1 file per package that includes all its code
		+	Support autoload for people who want that
		+	PEAR2 provides an autoload class
		+
		+	====action items====
		+	* jeichorn - make sure all of pear group has read the comments
		+
		+	All other items on the Agenda were moved to the next meeting
		+
		+	===General Action Items===
		+	* jeichorn - start agenda for the next meeting
		+	* jeichorn - get minutes approved and published on pear-dev
		+

20070520

Anonymous (anonymous@undisclosed.example.com) — 2025-04-03T13:08:43+00:00

2026/04/23 10:37	current
Line 1:	Line 1:
	+	====== PEAR Group Meeting Sunday 20th May 2007 ======
	+
	+	Looks like the meeting will be on Sunday the 20th 7pm UTC, check the pear clock for your timezone
	+
	+	http://clock.bluga.net/pear.php
	+
	+	You should all watch this before the meeting: http://video.google.com/videoplay?docid=-4216011961522818645
	+
	+	* Review last weeks action items
	+	* Review decision making process http://wiki.bluga.net/pear/decision_making?
	+	* Vote on vice president
	+	* Schedule some future meetings
	+	* Defining Collectives
	+	* Review RFC Proposal ((rfc))
	+	* Getting more people involved
	+	* Mentor Program
	+	* Reduction of adversarial attitude to new proposals
	+	* Community Outreach program (phpwomen, phpgtk, users groups)
	+	* PEAR Evangelist(s) who reach out to other libraries/frameworks/communities to try and foster PEAR use within their projects
	+	* Overall attitude and behaviors of current developers
	+	* Figuring out what people think of PEAR (and how we can make that positive)
	+	* I don't think its all great thoughts
	+	* Lots of people are turned off by the installer21
	+	* We have lots of positive aspects too, how do we focus on them
	+	* Website organization/updates
	+	* get users' feedback. A lot of people use pear or even write articles yet very little exists to show this material on the site
	+	* Review Suggestions from:
	+	* http://blog.joshuaeichorn.com/archives/2007/05/03/how-would-you-improve-pear/
	+	* http://www.sitepoint.com/blogs/2004/04/12/more-debate-on-pear/
	+	* Dealing with unmaintained/deprecated/dead packages
	+	* Also dead pepr proposals
	+	* Thoughts on PEAR2
	+	* Creating some sort of roadmap to move us forward
	+	* Creation of working groups to move projects forward
	+	* Reviewing RFCs
	+	* Creating a mentoring program
	+	* Community outreach
	+	* Evangelists (Driven by Greg?)
	+	* Success Stories
	+	* porting peardoc to livedoc (mainly helping the php effort, has to be this summer, phillip has more details)
	+	* Website Look/Feel Redesign/Update
	+	* Some kind of news effort, weekly/bi-weekly/monthly, perhaps working with Steph, this would only be couple of people that would over see the project and other people should be able to contribute easily
	+	* Good way to get outside people more in sync what's happening in the community
	+	* PEAR's week of code (David)
	+	* Idea
	+	* Sponsorship
	+	* Priorities
	+	* Tools
	+	* how to keep track of all that (wiki, trac, other: basecamp, etc) ?
	+	* have a serendipity install or other to manage publishing news on the site (committing to cvs and updating the site is not the greatest thing). We can also have a PEAR official blog.
	+	* Some sort of Design Guide to go along with coding standards, this would be a more in depth guide covering some common patterns guidelines for class/method sizes etc, would also be non binding just a guide, would need lots of community help

20070603

Anonymous (anonymous@undisclosed.example.com) — 2025-04-03T13:08:43+00:00

2026/04/23 10:37	current
Line 1:	Line 1:
	+	====== PEAR Group Meeting Sunday 3rd June 20077 ======
	+	Looks like the meeting will be on Sunday June 3rd 7pm UTC, check the pear clock for your timezone
	+
	+	http://clock.bluga.net/pear.php
	+
	+	You should all watch this before the meeting: http://video.google.com/videoplay?docid=-4216011961522818645
	+
	+	* Review last weeks action items
	+	* Schedule Next meeting
	+	* Vote on Vice President
	+	* Accept constitution extension. This should be added to the constitution on II Checks and balances:
	+	''PEAR Group and president elections take one month.
	+	In case of a tie, a runoff election between
	+	the tied competitors will be held. The runoff election will commence 10
	+	days after the previous election concludes, and will last 10 days.''
	+	* Review Collective List
	+	* Vote on RFC
	+	* Review Suggestions from:
	+	* http://blog.joshuaeichorn.com/archives/2007/05/03/how-would-you-improve-pear/
	+	* http://www.sitepoint.com/blogs/2004/04/12/more-debate-on-pear/
	+	* Dealing with unmaintained/deprecated/dead packages
	+	* Also dead pepr proposals
	+	* Coding standards: How to deal with "{" after "class Foo" -> Current consensus is a newline, then {, but that's not written down
	+	* Thoughts on PEAR2
	+	* Creating some sort of roadmap to move us forward
	+	* Naming (branding) of new installer/repository (Pyrus/Peach? Pyrus/PEAR2? etc.)
	+	* Creation of working groups to move projects forward
	+	* Reviewing RFCs
	+	* Creating a mentoring program
	+	* Community outreach
	+	* Evangelists (Driven by Greg?)
	+	* Success Stories
	+	* porting peardoc to livedoc (mainly helping the php effort, has to be this summer, phillip has more details)
	+	* Website Look/Feel Redesign/Update
	+	* Some kind of news effort, weekly/bi-weekly/monthly, perhaps working with Steph, this would only be couple of people that would over see the project and other people should be able to contribute easily
	+	* Good way to get outside people more in sync what's happening in the community
	+	* PEAR's week of code (David)
	+	* Idea
	+	* Sponsorship
	+	* Priorities
	+	* Tools
	+	* how to keep track of all that (wiki, trac, other: basecamp, etc) ?
	+	* Wiki needs to accept pear logins, not require pear devs to register.
	+	* have a serendipity install or other to manage publishing news on the site (committing to cvs and updating the site is not the greatest thing). We can also have a PEAR official blog.
	+	* Some sort of Design Guide to go along with coding standards, this would be a more in depth guide covering some common patterns guidelines for class/method sizes etc, would also be non binding just a guide, would need lots of community help
	+	* Mission statement
	+	* have a wiki page with the mission statement (thread from october 2006 on pear-dev)

20080622

Anonymous (anonymous@undisclosed.example.com) — 2025-04-03T13:08:43+00:00

2008/11/09 03:07		current
Line 14:		Line 14:
	* Plan for removing package v1		* Plan for removing package v1
	* Bug Triage Updates/Plan		* Bug Triage Updates/Plan
		+
		+	===== Minutes =====
		+
		+	==== Attendees ====
		+	* Greg Beaver [Past President] ([[cellog]])
		+	* Christian Weiske ([[cweiske]])
		+	* Chuck Burgess ([[ashnazg]])
		+	* Travis Swicegood ([[tswicegood]])
		+	* Brett Bieber ([[saltybeagle]])
		+	* Josh Eichorn ([[jeichorn]])
		+	* Joe Stump ([[jstump]])
		+	* David Coallier ([[davidc]])
		+
		+	==== Topics ====
		+
		+	Greg requested a past-president summary.
		+
		+	===Past President Summary===
		+
		+	* Congrats to new people
		+	* Limited Nominations/Voting as a sign that current PEAR devs are content
		+	* Volume of proposals has risen = thanks to the old people
		+	* Number of bugs is rising, despite declining new bug reports
		+	* Talk of PEAR2 is encouraging new devs and could be holding off development of old packages
		+	* Yet unresolved - how collectives will work/look.
		+	* A few constitutional amendments that were informally proposed by the old group - need to be approved by referendum.
		+	* Important for president to maintain relations with PHP internals
		+	* Important for the president to identify the individuals who have the most influence over PHP internals issues that affect PEAR
		+
		+	Greg recommended:
		+
		+	* Keep tabs on the stats
		+	* Brainstorm ways of improving retention if we are losing people
		+	* Keep attendance up at conferences for face-to-face
		+
		+
		+	=== Administrative ===
		+	* [[saltybeagele\|Brett]] will take meeting minutes
		+	* [[helgi\|Helgi]] will update pearweb index
		+	* [[jeichorn\|Josh]] granted access to group members to the PEAR blog
		+	* [[cweiske\|Christian]] granted pear.group karma
		+
		+	=== Conference Meetup ===
		+
		+	* Group will try and have a face to face meeting, PHP Appalachia in the USA, another in Europe if possible.
		+	* Christian will try and suggest a meeting in Canada or Europe, FOWA was suggested, which is in London this year early Oct.
		+
		+	=== Vice President was voted on ===
		+	* 6 votes for [[cweiske\|Christian]]
		+
		+	=== PEARDOC DB4=>DB5 conversion ===
		+	peardoc upgrade is planned for Next Week, June 30th - July 4th, Christian and Brett will take the lead on this and get Rudy from GSoC's code running and upgrade peardoc - solicit help from pear-dev - We WILL NOT Branch! A freeze will be announced on the pear-doc list
		+
		+	===Bug Triage Updates/Plan===
		+	Once every two months?
		+	Chuck will assist in bug triage updates on the wiki, highlight agenda to be sent to the list, josh suggests a post on the blog and pear-dev announcements for each event.
		+
		+	===Plan for removing package v1===
		+	Version bump?
		+	* Chuck +1
		+	* Christian +1
		+	* Travis +1
		+	* Josh +1
		+	* Brett +1
		+	* Joe +1
		+
		+	Try and contact developers first to upgrade their package.xml to version 2. Brett will draft an email to be sent to developers of package v1 packages.
		+
		+	====Next meeting time/date====
		+	Christian suggested meetings should not be held by a hard date, adjust meetings by amount of work to be done.
		+
		+	[[twsicegood\|Travis]] suggested a maximum/limit of time to ensure meetings happen on some schedule
		+
		+	The next meeting will be July 13th, same time 5pm GMT.
		+
		+	==== Action Items ====
		+
		+	* [[davidc\|David]] will email systems and get pear-group@ alias updated. - Done
		+	* [[davidc\|David]] plans to post a introductory post on the president's blog - Done
		+	* [[ashnazg\|Chuck]] will email Helgi about updates to the Calendar of events
		+	* [[ashnazg\|Chuck]] will send notices regarding upcoming bug triage events
		+	* [[saltybeagle\|Brett]] will draft an email to developers of package v1 packages, announcing the update.

2008-05-03

Anonymous (anonymous@undisclosed.example.com) — 2025-04-03T13:08:43+00:00

2026/04/23 10:37	current
Line 1:	Line 1:
	+	=== Who's running it? ===
	+
	+	=== What are we doing ===
	+	Working from [[http://pear.php.net/bugs/search.php?search_for=&boolean=0&limit=All&order_by=&direction=ASC&cmd=display&status=Open&bug_type=Bug&php_os=&packagever=&phpver=&assign=&maintain=&author_email=&bug_age=0&bug_updated=0\|lowest to highest]]
	+
	+
	+	=== Help needed / Low hanging fruit ===
	+	* [http://pear.php.net/bugs/bug.php?id=11815 Bug 11815] - decide which version is the one true version
	+	* [http://pear.php.net/bugs/bug.php?id=6356 Bug 6356] - Fatal error with PHP 5 / Determine future of Image_Remote package
	+	* [http://pear.php.net/bugs/bug.php?id=2067 Doc Req 2067] - Package documentation for [http://pear.php.net/package/Auth_PrefManager2 Auth_PrefManager2]
	+	* [http://pear.php.net/bugs/2885 Bug 2885] - Wrong class name in Auth_PrefManager2
	+
	+	* [http://pear.php.net/bugs/bug.php?id=7252 Bug 7252] - Undefined variable (tests needed)
	+	* [http://pear.php.net/bugs/bug.php?id=7897 Bug 7897] - XML_FastCreate makes the wrong sort of CDATA
	+	* [http://pear.php.net/bugs/bug.php?id=11511 Bug 11511] - BC break (use of self vs PHP 4)
	+	* [http://pear.php.net/bugs/bug.php?id=12575 Bug 12575] - Resolve licencing confusion
	+	* [http://pear.php.net/bugs/bug.php?id=13482 Bug 13482] - Bad md5sum for Validate_HU tar
	+	* [http://pear.php.net/bugs/bug.php?id=12086 Bug 12086] - CaseSensitivity patch for Net_UserAgent_Detect
	+	* [http://pear.php.net/bugs/bug.php?id=13605 Bug 13605] - Patch: Make Console_GetArgs work with phpunit3
	+
	+	=== In Progress ===
	+	* doconnor: There's a few packages with source missing from CVS, with no links to a repo. I've been mailing the maintainers to politely hassle.
	+	* http://pear.php.net/package/I18N_UnicodeString
	+	* http://pear.php.net/package/Validate_HU
	+
	+	=== Accomplishments ===
	+	* ashnazg: I've created a test suite for all API methods in XML_Util.
	+	* ashnzag: [http://pear.php.net/bugs/bug.php?id=4950 Bug 4950] - is closed
	+	* firman: [http://pear.php.net/bugs/bug.php?id=13615 Bug 13615] - Patch: Fix timezone data
	+	* doconnor: [http://pear.php.net/bugs/bug.php?id=7924 Bug 7924] - Net_Geo has a dependency on an unstable package
	+

2009-03-21

Anonymous (anonymous@undisclosed.example.com) — 2025-04-03T13:08:43+00:00

2009/03/22 01:24		current
Line 51:		Line 51:
	* Contact_Vcard_Parse		* Contact_Vcard_Parse
	* Validate_DE - Stefan is busy but aware, emailed March 2nd		* Validate_DE - Stefan is busy but aware, emailed March 2nd
		+	* Net_DNS - emailed 22nd March, doconnor
	==== Targets to update to package 2.0 xml ====		==== Targets to update to package 2.0 xml ====

2009/11/02 18:23		current
Line 267:		Line 267:
	\| [[http://svn.php.net/viewvc?view=revision&revision=290147\|290147]] \| derick \| 2009-11-02T16:12:20.158272Z \| - Updated to version 2009.17 (2009q)\|merged\|		\| [[http://svn.php.net/viewvc?view=revision&revision=290147\|290147]] \| derick \| 2009-11-02T16:12:20.158272Z \| - Updated to version 2009.17 (2009q)\|merged\|
	\| [[http://svn.php.net/viewvc?view=revision&revision=290150\|290150]] \| felipe \| 2009-11-02T17:37:32.398819Z \| - Fixed bug #49244 (Floating point NaN cause garbage characters). (patch by Sjoerd) \|?\|		\| [[http://svn.php.net/viewvc?view=revision&revision=290150\|290150]] \| felipe \| 2009-11-02T17:37:32.398819Z \| - Fixed bug #49244 (Floating point NaN cause garbage characters). (patch by Sjoerd) \|?\|
		+	\| [[http://svn.php.net/viewvc?view=revision&revision=290154\|290154]] \| pajoye \| 2009-11-02T20:46:52.389036Z \| - Fixed #50052, Different Hashes on Windows and Linux on wrong Salt size\|?\|
		+	\| [[http://svn.php.net/viewvc?view=revision&revision=290166\|290166]] \| pajoye \| 2009-11-03T10:48:12.857521Z \| - fix lenght for alloc and cpy (Kanwal)\|?\|
		+	\| [[http://svn.php.net/viewvc?view=revision&revision=290167\|290167]] \| scottmac \| 2009-11-03T12:15:03.991984Z \| Update PCRE to 8.00 \|?\|
		+	\| [[http://svn.php.net/viewvc?view=revision&revision=290168\|290168]] \| scottmac \| 2009-11-03T12:23:54.748600Z \| BFN \|?\|
		+	\| [[http://svn.php.net/viewvc?view=revision&revision=290170\|290170]] \| uw \| 2009-11-03T14:56:04.044360Z \| Fix for bug #49965 . Let mysqli_options() try to cast option values to the appropriate type.\|?\|
		+	\| [[http://svn.php.net/viewvc?view=revision&revision=290190\|290190]] \| guenter \| 2009-11-03T21:21:34.589624Z \| removed now obsolete NetWare hack since I fixed this with Novell some longer time ago in their SDK header. \|?\|
		+	\| [[http://svn.php.net/viewvc?view=revision&revision=290191\|290191]] \| guenter \| 2009-11-03T21:26:39.217225Z \| added timezone define for NetWare. \|?\|
		+	\| [[http://svn.php.net/viewvc?view=revision&revision=290196\|290196]] \| uw \| 2009-11-04T12:33:49.082539Z \| Adding CLEAN sections and making tests portable between PHP 5 and PHP 6 by replacing string(n) with %unicode%% %%string%(n) and similar.\|?\|
		+	\| [[http://svn.php.net/viewvc?view=revision&revision=290199\|290199]] \| iliaa \| 2009-11-04T13:44:10.979986Z \| Fixed bug #50073 (parse_url() incorrect when ? in fragment). \|?\|
		+	\| [[http://svn.php.net/viewvc?view=revision&revision=290206\|290206]] \| uw \| 2009-11-04T16:09:07.758115Z \| Skipping if MySQL old password algorithm is in use as it seems to be the case on gcov.php.net\|?\|
		+	\| [[http://svn.php.net/viewvc?view=revision&revision=290210\|290210]] \| uw \| 2009-11-04T16:56:32.352885Z \| mysqli won't accept empty string for socket, skip test of mysqli.default_socket if test run does not use socket\|?\|
		+	\| [[http://svn.php.net/viewvc?view=revision&revision=290212\|290212]] \| mbeccati \| 2009-11-04T19:16:39.255772Z \| - Reverting previous fix for bug #49985 # Unmerged changes from revision 289924 \|?\|
		+	\| [[http://svn.php.net/viewvc?view=revision&revision=290214\|290214]] \| mbeccati \| 2009-11-04T19:32:27.170798Z \| - Properly fixed bug #49985 (pdo_pgsql prepare() re-use previous aborted transaction). # Removed usage of the memory address when generating prepared statemend names # as uniqueness can't be enforced. Used a statment counter instead. \|?\|
		+	\| [[http://svn.php.net/viewvc?view=revision&revision=290231\|290231]] \| dmitry \| 2009-11-05T09:33:19.672560Z \| Fixed unnecessary invokation of setitimer when timeouts have been disabled (Arvind Srinivasan) \|?\|
		+	\| [[http://svn.php.net/viewvc?view=revision&revision=290236\|290236]] \| dmitry \| 2009-11-05T10:38:56.883775Z \| Avoid invoking setitimer when timeouts have been disabled (Arvind Srinivasan) \|?\|
		+	\| [[http://svn.php.net/viewvc?view=revision&revision=290253\|290253]] \| jani \| 2009-11-05T11:33:32.305688Z \| - Missing entry\|?\|
		+	\| [[http://svn.php.net/viewvc?view=revision&revision=290266\|290266]] \| uw \| 2009-11-05T11:51:21.319010Z \| Fixing test: it didn't do a select_db and gave a false-positive with libmysql\|?\|
		+	\| [[http://svn.php.net/viewvc?view=revision&revision=290288\|290288]] \| uw \| 2009-11-05T12:14:08.310342Z \| Fixing test: of course, libmysql won't care about open_basedir, but mysqlnd should\|?\|
		+	\| [[http://svn.php.net/viewvc?view=revision&revision=290306\|290306]] \| iliaa \| 2009-11-05T13:29:34.995523Z \| Make sure that max_file_uploads is set to 20 by-default in all places \|?\|
		+	\| [[http://svn.php.net/viewvc?view=revision&revision=290362\|290362]] \| wharmby \| 2009-11-05T22:44:02.962662Z \| Fix tests\|?\|
		+	\| [[http://svn.php.net/viewvc?view=revision&revision=290363\|290363]] \| sixd \| 2009-11-05T23:03:28.852685Z \| Update and fix grammar\|?\|
		+	\| [[http://svn.php.net/viewvc?view=revision&revision=290364\|290364]] \| sixd \| 2009-11-06T02:09:47.340472Z \| Add pecl mail list\|?\|
		+	\| [[http://svn.php.net/viewvc?view=revision&revision=290368\|290368]] \| scottmac \| 2009-11-06T09:02:52.634548Z \| Fix a typo \|?\|
		+	\| [[http://svn.php.net/viewvc?view=revision&revision=290392\|290392]] \| felipe \| 2009-11-07T21:27:15.860391Z \| - Fixed bug #50090 (Typo in IteratorIterator constructor) \|?\|
		+	\| [[http://svn.php.net/viewvc?view=revision&revision=290395\|290395]] \| felipe \| 2009-11-08T15:02:54.675081Z \| - Added SKIPIF \|?\|
		+	\| [[http://svn.php.net/viewvc?view=revision&revision=290398\|290398]] \| rasmus \| 2009-11-08T15:18:10.480247Z \| Fix bug #50115 \|?\|
		+	\| [[http://svn.php.net/viewvc?view=revision&revision=290404\|290404]] \| iliaa \| 2009-11-09T01:54:23.517362Z \| Upgraded bundled sqlite to version 3.6.20 \|?\|
		+	\| [[http://svn.php.net/viewvc?view=revision&revision=290419\|290419]] \| rasmus \| 2009-11-09T15:13:07.815872Z \| Fix bug #50124 \|?\|
		+	\| [[http://svn.php.net/viewvc?view=revision&revision=290420\|290420]] \| derick \| 2009-11-09T15:39:15.015555Z \| - Updated to version 2009.18 (2009r)\|?\|
		+	\| [[http://svn.php.net/viewvc?view=revision&revision=290434\|290434]] \| jani \| 2009-11-09T17:08:48.606768Z \| - Fix bad section names (extra - in the end..)\|?\|
		+	\| [[http://svn.php.net/viewvc?view=revision&revision=290435\|290435]] \| rasmus \| 2009-11-09T17:21:15.612206Z \| Fix bug #50129 \|?\|
		+	\| [[http://svn.php.net/viewvc?view=revision&revision=290489\|290489]] \| sixd \| 2009-11-10T22:48:37.738188Z \| Add test for long fixed bug\|?\|
		+	\| [[http://svn.php.net/viewvc?view=revision&revision=290507\|290507]] \| iliaa \| 2009-11-11T13:49:21.273229Z \| typo fix \|?\|
		+	\| [[http://svn.php.net/viewvc?view=revision&revision=290515\|290515]] \| felipe \| 2009-11-11T18:52:12.425227Z \| - Fixed bug #50152 (ReflectionClass::hasProperty hehaves like isset() not property_exists) [5_2 is OK] \|?\|
		+	\| [[http://svn.php.net/viewvc?view=revision&revision=290516\|290516]] \| felipe \| 2009-11-11T18:59:37.518532Z \| - Fixed bug #50146 (property_exists: Closure object cannot have properties) \|?\|
		+	\| [[http://svn.php.net/viewvc?view=revision&revision=290519\|290519]] \| sixd \| 2009-11-11T19:44:53.497711Z \| Sigh. Fix grammar of title\|?\|
		+	\| [[http://svn.php.net/viewvc?view=revision&revision=290527\|290527]] \| cellog \| 2009-11-11T21:02:59.366740Z \| fix PHP Bug #49910: no support for ././@LongLink for long filenames in phar tar support\|?\|
		+	\| [[http://svn.php.net/viewvc?view=revision&revision=290567\|290567]] \| felipe \| 2009-11-12T00:10:00.340842Z \| - Fixed bug #50005 (Throwing through Reflection modified Exception object makes segmentation fault) \|?\|
		+	\| [[http://svn.php.net/viewvc?view=revision&revision=290568\|290568]] \| felipe \| 2009-11-12T00:44:43.769026Z \| - Fix typo\|?\|
		+	\| [[http://svn.php.net/viewvc?view=revision&revision=290570\|290570]] \| rasmus \| 2009-11-12T01:09:16.218434Z \| Fix bug #49098 \|?\|
		+	\| [[http://svn.php.net/viewvc?view=revision&revision=290574\|290574]] \| rasmus \| 2009-11-12T08:26:43.203190Z \| NEWS entries for mysqli crash fix bug \|?\|
		+	\| [[http://svn.php.net/viewvc?view=revision&revision=290575\|290575]] \| jani \| 2009-11-12T09:07:51.095253Z \| bfn\|?\|
		+	\| [[http://svn.php.net/viewvc?view=revision&revision=290578\|290578]] \| johannes \| 2009-11-12T15:05:03.813490Z \| Fix #50063 (safe_mode_include_dir fails)\|?\|
		+	\| [[http://svn.php.net/viewvc?view=revision&revision=290582\|290582]] \| thetaphi \| 2009-11-12T15:19:35.858643Z \| Fix bug #50087: NSAPI performance improvements \|?\|