On Tue, May 16, 2006 8:04 am, Sebastian Bergmann wrote: > Ilia Alshanetsky wrote: >> For every RC we already send an e-mail to about 12 projects asking >> them >> to test their code against the release and let us know of any issues >> that come up. > > Sadly, this does not seem to work. Maybe because nobody from the > projects feels responsible?
I would submit that: They assume they only need to tell you if something is WRONG because that is what they are told to do. (See first sentence above) That's quite different from: We're waiting for a "green light" from your project so we know it's a good solid release. If you only ask to hear about problems, you don't hear a "200 OK" when you need it. :-) It's also possible that the PHP RC release cycle is too quick for them to test, depending on their current availability, so it never gets done on time... Though obviously it's gotta be pretty high priority for them to be sure it's all good. Development of automated testing for these projects (by the projects themselves, not PHP Devs) would go a long way towards the ideal of catching bugs before release... But it seems like PHP itself could use some work in this area to lead by example. :-) Just some random thoughts when I should be working... -- Like Music? http://l-i-e.com/artists.htm -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
