I would suggest that the choice to do the diff-review is the prerogative of the reviewer. The diff-review is mostly a courtesy to the Theme developer, to expedite the review. It is NOT a hard-and-fast rule. If the reviewer thinks that sufficient time has elapsed since the previous review, or that the diff is complex enough to warrant a full review, or even just wants to perform a full review, then the reviewer can certainly perform a more thorough review.<div>
<br></div><div>Thanks,</div><div><br></div><div>Chip<br><br><div class="gmail_quote">On Fri, Mar 9, 2012 at 2:27 AM, Konstantin Obenland <span dir="ltr"><<a href="mailto:obenland@gmx.de">obenland@gmx.de</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">On a more general note:<br>
Birchware was wondering why his theme "got a "not approved" review [...], because none of the things remarked upon have been changed since the previous version were approved, with no mentions of those things."<br>
Emil suggested, that "This Theme also did not have enough changes for a complete review".<br>
<br>
I was under the impression, Themes must be kept up to date once they are accepted into the repository.<br>
Does that not include adhering to standards that have changed since the last submission? (i.e. the comment-reply business)<br>
How are Theme Reviewers supposed to look for those changes when only making a diff review?<br>
<br>
Thanks,<br>
Konstantin<br>
<div class="HOEnZb"><div class="h5">_______________________________________________<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>
</div></div></blockquote></div><br></div>