On 3/1/2012 3:02 PM, Greg Stein wrote: > Modules do not have to be tested *before* they appear in trunk. That's > putting the cart before the horse. Part of the development process > (while in trunk) is doing the testing portion. And hey... if it never > gets tested, then it gets marked as "experimental" and we all move on.
In fact there is an modules/experimental/ tree; mod_noloris is currently one such module. Of course, "if it never gets tested" is a handwave. There's obviously no way for the pmc to assert committers have tested it. The only filter is the acceptance vote. This submitted module was not committed to modules/experimental/, but rather in modules/debugging/ If your desire was to mark this module experimental, you may want to refine your vote to be more explicit. As a diagnostic tool this module is toxic in resource consumption, so in theory, any bugs in this tool are unlikely to cause more pain than using the tool in the first place.
