On Sun, Sep 12, 2010 at 1:20 PM, Chip Bennett <span dir="ltr"><<a href="mailto:chip@chipbennett.net">chip@chipbennett.net</a>></span> wrote:<br><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div class="gmail_quote"><div>Do you have *specific* examples of onerous or unnecessary review requirements? Quite honestly, the review queue remains steady at 60+ Themes. We don't have time for navel-gazing. But if there are *specific* requirements that need to be addressed, we're always up for looking at them. (I've actually got a couple to bring up myself, regarding the Theme Unit Tests.)</div>
</div></blockquote><div><br></div><div>Yes. I've said previously on this list (in an email that received no replies) that I do not believe that themes should be rejected for notices and deprecated calls. This is coming from the individual who implemented deprecated argument handling, spent dozens of hours tracking down version numbers for deprecated functions, preaches WP_DEBUG [0, 1, 2], and wrote the logging plugin you use.</div>
<div><br></div><div>[0] <a href="http://www.andrewnacin.com/tag/wp_debug/">http://www.andrewnacin.com/tag/wp_debug/</a></div><div>[1] <a href="http://core.trac.wordpress.org/changeset/13176">http://core.trac.wordpress.org/changeset/13176</a></div>
<div>[2] <a href="http://core.trac.wordpress.org/changeset/13185">http://core.trac.wordpress.org/changeset/13185</a></div><div><br></div><div>That's not to say that theme authors shouldn't be encouraged to rectify notices on future theme submissions, or that the tolerance level shouldn't go down on successive submissions by that author. But it all depends on the notice, and it all depends on the deprecated call. If notices and deprecated calls cannot be properly evaluated for severity, then they should not be evaluated at all.</div>
</div>