<meta http-equiv="content-type" content="text/html; charset=utf-8"><div>Each of us has a slightly different approach. In my case, rather than merely outputting everything from Theme-Check, I separate the Theme-Check output into "Required" and "Recommended". I try to keep all the "Required" issues together, and then put any recommendations after. And then I close out the review with some boilerplate text/links.</div>
<div><br></div>As long as we're communicating effectively with the Theme developers regarding what needs to be fixed in order to approve the Theme, that's what ultimately matters.<div><br></div><div>Your review comments are all good comments. I like the way that you offered suggested fixes, especially since, as you noted, all of the outstanding issues are minor/easy to fix.<div>
<br></div><div>For a review such as that one, where the outstanding issues are all minor and easy to fix, I have been experimenting with a new approach: I keep the ticket open, and state that if an updated Theme with fixes is submitted within a day or two, I'll close the current ticket as "newer version uploaded" and proceed to review/approve the update with fixes.</div>
<div><br></div><div>(This approach seems to be doing well in my thus-far limited trial.)</div><div><br></div><div>Chip<br><div><br><div class="gmail_quote">On Wed, Mar 23, 2011 at 11:39 PM, Emil Uzelac <span dir="ltr"><<a href="mailto:emil@themeid.com">emil@themeid.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"><font size="2"><font face="tahoma,sans-serif">You're welcome!</font></font><div><div class="im"><font size="2"><font face="tahoma,sans-serif"><br clear="all">
</font></font><div><strong>Emil Uzelac</strong> | ThemeID | T: 224-444-0006 | Twitter: @EmilUzelac | E: <a href="mailto:emil@themeid.com" target="_blank">emil@themeid.com</a> | <a href="http://themeid.com/" target="_blank">http://themeid.com</a></div>
<div><font color="#999999">Make everything as simple as possible, but not simpler. - Albert Einstein</font></div><br>
<br><br></div><div><div></div><div class="h5"><div class="gmail_quote">On Wed, Mar 23, 2011 at 11:25 PM, Ian Stewart <span dir="ltr"><<a href="mailto:ian@iandanielstewart.com" target="_blank">ian@iandanielstewart.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div>On 2011-03-23, at 11:15 PM, Emil Uzelac wrote:<br>
<br>
> Looks good Ian, well the only one thing that I would add to this would be some references to WordPress guides such as:<br>
> • <a href="http://codex.wordpress.org/Theme_Review" target="_blank">http://codex.wordpress.org/Theme_Review</a><br>
<br>
</div>Thanks! I just added in a link to the Theme Unit Test right after my mention of it.<br>
<div><div></div><div><br>
Ian<br>
_______________________________________________<br>
theme-reviewers mailing list<br>
<a href="mailto:theme-reviewers@lists.wordpress.org" target="_blank">theme-reviewers@lists.wordpress.org</a><br>
<a href="http://lists.wordpress.org/mailman/listinfo/theme-reviewers" target="_blank">http://lists.wordpress.org/mailman/listinfo/theme-reviewers</a><br>
</div></div></blockquote></div><br></div></div></div>
<br>_______________________________________________<br>
theme-reviewers mailing list<br>
<a href="mailto:theme-reviewers@lists.wordpress.org">theme-reviewers@lists.wordpress.org</a><br>
<a href="http://lists.wordpress.org/mailman/listinfo/theme-reviewers" target="_blank">http://lists.wordpress.org/mailman/listinfo/theme-reviewers</a><br>
<br></blockquote></div><br></div></div></div>