On Fri, 2011-09-23 at 12:15 -0400, Matthew Weier O'Phinney wrote: > On 2011-09-23, Rasmus Lerdorf <ras...@lerdorf.com> wrote: > > 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. > > I've made the decision that my team will test against RCs as soon as > they are out (and we're going to be trying to do each beta as well). If > we run into issues, we'll of course report back here.
Good are also "success" reports so we know tests were run and succeeded. > That said, I think it would be good to have a notification system > whereby framework leads are all pinged on new betas and RCs, and a wiki > page where they can indicate that they've run tests (and whether or not > they had issues). That way, you could have a targetted nag list -- "Hey, > I don't see an update from you -- RUN THE TESTS!", and a deadline > whereby if they haven't run them, they accept the consequences. :) We send out mails like this: http://news.php.net/php.qa/65903 to maintainers of different PHP projects who have opted in for every RC. I usually get one response and lots of black-hole void reactions. For 5.3.9 I'll make more responses a release requirement. (have to check the current recipient list and probably update that to define that closer, will also work w/ Stas/dsp on that to have it identical for 5.4) > I could also see this being an interesting peer-pressure move -- "First > to test!", "We tested last week; how come _you_ haven't?", etc. This also means that this list has more traffic. Which makes it more likely to be ignored ... johannes -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
