Bonjour,
Greg Beaver wrote:
Sebastian Bergmann wrote:
Ilia Alshanetsky wrote:
For every RC we already send an e-mail to about 12 projects asking them
to test their code against the release and let us know of any issues
that come up.
Sadly, this does not seem to work. Maybe because nobody from the
projects feels responsible?
Geez tensions are running high.
I am the tester for PEAR, and I tested the PEAR Installer (I do not test
the gazillion packages that I don't maintain) and it worked great with
PHP 5.1.4. PEAR doesn't use $_POST and I did not detect any errors.
In the past I have found at least 4 PHP bugs when testing PEAR with PHP.
The fact is, most of the bugs I find are found the instant they are
introduced as I use the CVS of PHP_5_X for my testing. In fact the
system is working quite well from my end, but I can't vouch for other
projects.
Greg
I've also been working in the same area.
I would like to add that:
PEAR code is often not php5 E_STRICT compatible for the obvious reason
that we belongs to the real user area , meaning not running only on some
dream installations but real production machines with all the no-choices
that induces and furnishing some layers to practical cases.
But that is not the point here.
Even if we use some kind of fork of run-tests , we have a bunch of tests
(.phpt and others).
So by release process, it could be a good idea to run them as a whole on
different installations.
Yes, we would have to shut off E_STRICT for some of them :)
Outer the fact that some packages need some external means , I believe
it would not be so hard to implement.
History shows we would have trap some bloody stuff if not bugs.
No, no , Greg , it's cool discussion :)
--
toggg
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
