<div class="gmail_quote">On Thu, Aug 26, 2010 at 6:20 AM, Andrew Nacin <span dir="ltr"><<a href="mailto:wp@andrewnacin.com">wp@andrewnacin.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div class="gmail_quote"><div class="im">On Thu, Aug 26, 2010 at 6:37 AM, Andrew Nacin <span dir="ltr"><<a href="mailto:wp@andrewnacin.com" target="_blank">wp@andrewnacin.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<span style="font-family:arial, sans-serif;font-size:13px;border-collapse:collapse"><span style="border-collapse:separate;font-family:arial;font-size:small"><div>I see no problem with a theme being approved with notices/deprecated calls, if that's the only thing wrong with it.</div>
</span></span></blockquote><div><br></div></div><div>An addendum. There are a few deprecated functionality issues that should be weighted more heavily. Specifically, the use of user levels instead of capabilities (since 2.0). In general, a function that was deprecated somewhere around 2.5 or earlier is probably a good time to evaluate what that function does and whether it is important that the theme does not use it.</div>
</div>
</blockquote></div><br><div>Which is easier to manage, both for Theme developers and for Theme testers?</div><div><br></div><div>1) A list of specific, deprecated functions that are acceptable vs. unacceptable</div><div>
2) A rule that states that no deprecated functions may be used</div><div><br></div><div>We're trying to make this process *easier* for all involved, not *harder*. Trying to maintain, from one WordPress version release to another, which deprecated functions are still acceptable and which ones are not, adds no benefit to the process or parties involved - at least that I can discern.</div>
<div><br></div><div>What are the compelling reasons to allow certain deprecated functions to remain?</div><div><br></div><div>Chip</div>