Minor enhancement: CI server now builds trunk packages

I just tinkered around with the CI server, and now it'll build (via pyrus) a package off of trunk; and publish it. For instance: http://test.pear.php.net:8080/cruisecontrol/artifacts/Auth/20100822212117/package/ I plan to add links from http://pear.php.net/qa/packages_closed_reports_no_release.php to the relevant build artifacts; or... perhaps even on the package homepages for successful builds. As a side note, I don't suppose that anyone with a bit of time would like to look at a qa-package-script? IE: 1. Grab list of bugs closed since last release / svn changelog since last release (message + author) 2. Open up the package.xml and create a new release, adding the changelog info. 3. Build with pyrus / pear 4. Optionally svn commit && svntag as appropriate There's only so many hours in a day; and if a lot of the QA tasks we do within PEAR can be fully or semi automated; I think we could actually make a dent in the growing lists of tasks without burning out our volunteers.