On Wed, 2011-08-24 at 12:24 +0200, Ferenc Kovacs wrote: > we could have spotted this via two ways: > - those who participated in fixing > https://bugs.php.net/bug.php?id=53727 could have spotted this > - our tests should have start failing after the change
Third option: - RC testers might have spotted and reported it. I have the impression that very few people actually test these. When creating an RC we inform the "primary testers" as well as qa and internals list members. From there I get one or two responses in general. When I approach PHP users I often get answers like installing PHP without breaking their setup would be complicated (which is not the case but maybe needs education?) and they won't have time. I try to use a hypothetical case, like we have here in reality, to explain them why it is beneficial for their business if it is detected early as then we can fix it, fixing something after a release is hard. We also can try to improve our tests but we will never be able to test each and every way PHP is being used out there in the wild. So how can we motivate people to test new versions during RC not the day after it is being released? We don't push them out as news on the php.net frontpage and we don't send it out to the announce list for reasons like not confusing users. Should we change that? Other ideas? johannes -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
