Re: We Want Quality

w>> testing a few of the *major modules* (mysql...) on a few of the *most w>> important OSs* There are many? I know only one and it's... *ducks* *runs* *hides* Well, seriously - if people will use it, we'll know it, if not - this OS is not "most important". You can't just go and tell "go use it on windows" - if nobody uses it, it doesn't get fixed, as soon as people start to use it and problem has enough weight not to be lost in 1001 misconfigurations - it gets fixed pretty quick. w>> we should assign a *simple task* to the *most frequently available users w>> and developers* for several modules or OSs: You probably don't know how *boring* is to re-check all this stuff after each small change (that's usually "small" changes which break the thing). However, automated checklist and automated tools to run it (something like Perl's make test) would be very helpful here. If someone does write them. And then again - it'd never catch bugs like "if I define variable there, and add something to it here, and than run that function - session stops to work with mm handler"... No sane mind can invent such things - they just pop-up from the global code pool. w>> I would take the build *Win32* and do *basic tests part* eg. mysql and odbc w>> - whenever a RC is planned, these people have to stop all work and do w>> these basic tests, if not or they do not cover a basic error - they╢re w>> lynched :) Well, if we had people so available that they can drop everything and go testing PHP in arbirary moment - we'd probably have no bugs left at all and all feature requests satisfied :) -- Stanislav Malyshev stas@zend.com +972-3-6139665