Generally speaking, no. I can't think of anything. Themes are expected to conform to the current Guidelines at the time of submission. The reason that Theme Name is "grandfathered" is that changing the Theme Name changes the Theme Slug, which in turn breaks automatic update notification for end users.<div>
<br></div><div>I would recommend to just go ahead and review some Themes. If you observe a "required" issue, note it in the review. If the developer pushes back on any of the review comments, just try to work it out in-ticket. And if you need assistance, don't hesitate to ask another reviewer or an admin to offer a second opinion on the ticket.</div>
<div><br></div><div>Thanks,</div><div><br></div><div>Chip<br><br><div class="gmail_quote">On Wed, Aug 1, 2012 at 10:09 AM, Chandra Maharzan <span dir="ltr"><<a href="mailto:maharzan@gmail.com" target="_blank">maharzan@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">So, is there anything else that can skip the guidelines apart from<br>
name for already hosted themes? I am interested in reviewing themes so<br>
want to understand this better. Thanks for your responses Chip.<br>
<div class="HOEnZb"><div class="h5"><br>
On Wed, Aug 1, 2012 at 8:49 PM, Chip Bennett <<a href="mailto:chip@chipbennett.net">chip@chipbennett.net</a>> wrote:<br>
> "For obvious reasons, we are quite reluctant to ask a Theme already hosted<br>
> in the WPORG repository to change its name."<br>
><br>
> I'm not sure how that statement can be misconstrued to mean that we would<br>
> allow a Theme to use deprecated functions.<br>
><br>
> Chip<br>
><br>
><br>
> On Wed, Aug 1, 2012 at 10:01 AM, Chandra Maharzan <<a href="mailto:maharzan@gmail.com">maharzan@gmail.com</a>><br>
> wrote:<br>
>><br>
>> I am emailing because I saw this (new version) being approved just 3<br>
>> days ago. Does that mean, when the theme is updated, you guys don't<br>
>> review the all the guidelines ? only the difference ? even if uses<br>
>> deprecated functions and may not work with new WP versions ?<br>
>><br>
>> On Wed, Aug 1, 2012 at 8:41 PM, Chip Bennett <<a href="mailto:chip@chipbennett.net">chip@chipbennett.net</a>> wrote:<br>
>> > That Theme was first approved in 2009, and therefore predates the<br>
>> > current<br>
>> > Theme Review guidelines, including the Theme Name requirement.<br>
>> ><br>
>> > For obvious reasons, we are quite reluctant to ask a Theme already<br>
>> > hosted in<br>
>> > the WPORG repository to change its name.<br>
>> ><br>
>> > Chip<br>
>> ><br>
>> > On Wed, Aug 1, 2012 at 9:33 AM, Chandra Maharzan <<a href="mailto:maharzan@gmail.com">maharzan@gmail.com</a>><br>
>> > wrote:<br>
>> >><br>
>> >> Hi Guys,<br>
>> >><br>
>> >> I have been looking into the theme review guidelines and been finding<br>
>> >> few things such as the Twenty Eleven error. :) Now I found another<br>
>> >> one. iStudio Theme: <a href="http://wordpress.org/extend/themes/istudio-theme" target="_blank">http://wordpress.org/extend/themes/istudio-theme</a><br>
>> >><br>
>> >> While the guidelines say you can't add a theme in the name:<br>
>> >> <a href="http://codex.wordpress.org/Theme_Review#Theme_Name" target="_blank">http://codex.wordpress.org/Theme_Review#Theme_Name</a>, this theme still<br>
>> >> has it and I saw it was just approved in the Most recently updated<br>
>> >> themes. Perhaps, this can go in their next update. Just a heads up to<br>
>> >> the Review Team.<br>
>> >><br>
>> >> Thanks,<br>
>> >> Chandra<br>
>> >><br>
>> >> --<br>
>> >> cmans<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>
>> ><br>
>> ><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>
>><br>
>><br>
>><br>
>> --<br>
>> cmans<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>
><br>
><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>
<br>
<br>
<br>
--<br>
cmans<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>
</div></div></blockquote></div><br></div>