All Known Bugs Fixed [TM]

Hi, Note: cross-posting. Please reply with QA matters to pear-qa, and webmaster matters to pear-webmaster. Thank you. PEAR 1.4.0a1 is ready to go. All unit tests pass on both my windows and my gentoo box, and the things that don't have tests appear to work under normal situations. It is definitely stable enough for a first alpha release. Pierre/Alan: this means get ready to release both the web and gtk frontends after you feel comfortable that they work with PEAR 1.4.0. I need to doubly verify that my changes to peclweb work and then commit them prior to release. I will do all kinds of manual tests to see if I can break it, and tomorrow some time I will post a .tgz that will become the release (assuming no critical bugs are found). In the mean time there are some questions I have about how we should go about things. First of all, in order for releases utilizing the new package.xml format to be uploaded, pearweb must be running PEAR 1.4.0a1. How many of you have a working local copy of pearweb? I've been running pearweb on windows here with PEAR 1.4.0a1 quite successfully, but I have only tested the xmlrpc interface and the package upload/view packages stuff. Is there any PEAR usage outside of the handling of package uploads I should know about? In addition, if I have forgotten about any minor or major issues to be fixed prior to release, please reply to pear-qa so that I can open a bug, or open a bug yourself for the PEAR package. [I fixed the version validation scheme to be much more relaxed] Releasing PEAR is always a huge deal, and so I've been absolutely crazy about getting the code stable. The primary reason for the alpha label is that all of the ideas in the code are so new, I definitely want outside input on whether anything needs to be changed before we freeze the API. To be sure things are working, I am going to wipe my local installs of PEAR on both windows and linux, and then re-install via PEAR upgrade to see if all the problems people have had in the past have been fixed. One thing all of you can do is the following sequence: cvs -d :pserver:****@cvs.php.net:/repository co pear-core cd pear-core pear upgrade package-PEAR.xml cd tests pear run-tests -l If you only wish to see failed tests, run pear run-tests -lq If you wish to log in real time all tests, regardless of success/failure, run pear run-tests -rlq Documentation for all of the new commands that ship with PEAR is available via "pear help" and "pear help <command>" Thanks, Greg