2011/9/23 Rasmus Lerdorf <ras...@lerdorf.com>: > On 09/23/2011 12:13 PM, Patrick ALLAERT wrote: >> 2011/9/23 Rasmus Lerdorf <ras...@lerdorf.com> >>> 2. Maybe we should think bigger and put more focus on having large PHP >>> frameworks and apps test every RC. Currently we notify them of RCs >>> and just hope someone will test and report back, but that obviously >>> isn't working. We need a Daniel Brown-like approach to this. Someone >>> who is really annoyingly persistent and will hunt down people to >>> test RCs and keep a sign-off checklist of projects that have given >>> a thumbs-up on an RC. >> >> Solution 2: +1 >> >> Having a Jenkins instance which would run major framework testsuites >> against the different versions of PHP? > > That would be cool, but a lot of work to maintain since every > framework/app has different ways of testing and we'll want to test > different versions. It seems like the best bet is to get the people who > know the code best to maintain the tests. If we could get all of them to > set up *and maintain* their stuff on the Jenkins instance it would be > ideal, but that's probably dreaming in technicolor.
Most serious PHP libraries/frameworks have a CI server. But they are mainly setup to discover when someone breaks something rather than testing various releases of PHP (and certainly not RC ones). Open up an Jenkins instance with some guidelines on how to add a new project which will be automatically launched with different releases of PHP and I am sure project leaders will be glad to setup their project(s) to know if their libraries/framework break with a specific release of PHP. Note that the libraries/frameworks wouldn't be supposed to be updated against their VCS. Ideally key releases of those libs/frameworks would be setup. Davide Mendolia (in CC) has started such a project in the past. Patrick -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
