PHP-QAT
|
The PHP/QA Team is a small group of developers
whose primary goal is to support the PHP core developers by providing
them with timely quality assurance.
|
Projects & Goals
|
Find more information about PHP/QA Team's current
projects and future goals.
|
Release Candidates
|
What are release candidates and how you can help us testing them.
|
Contact Information
|
Questions about the PHP-QAT should be sent to the
PHP/QAT Mailing List
Bug Reports should be submitted to the official PHP bug list
(http://bugs.php.net)
All other questions should be directed to the appropriate
PHP mailing list.
|
|
|
|
Release Candidates
|
|
|
Basics
Release candidates are development packages released to check if any critical
problems have slipped into the code during the previous development period.
Release candidates are NOT for production use, they are for testing purposes only
even though in most cases there are almost no differences between the general
availability (GA) release and the last RC.
You can help the PHP Team and yourself detect problems by installing and testing
release candidates on your own (non-production!) server.
|
|
|
Installation problems
First of all, make sure the build process (on *nix only) and installation went fine for you.
PHP supports quite a number of operating systems on different platforms and we continue
to work on increasing this number.
If you encounter any problems during the installation, we would like to know about them.
|
|
|
Testing the installation
When done with the build, please run the test engine by using the 'make test ' command
and send us the results (hit 'Y ' when it asks you whether to send the report).
This way we'll receive the required information about your system to fix the problems
detected by the test suite (if any). Each and every report goes towards helping us
provide the best software we can, your feedback is a valuable resource and the
PHP group would hereby like to extend their gratitude for your effort.
|
|
|
Real-life tests
We would also appreciate if you install the RC on your development server and run
your software. This would help us to detect any unintentional changes between
the release candidates and general releases.
Such real-life tests are the most valuable because our test suite does not yet
cover every possible use case (but we're working on that).
|
|
|
Getting the Release Candidates
The release candidates are available for download from the QA frontpage.
|
|
|