<div class="gmail_quote">On Wed, Sep 1, 2010 at 1:21 PM, Otto <span dir="ltr"><<a href="mailto:otto@ottodestruct.com">otto@ottodestruct.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="im">On Wed, Sep 1, 2010 at 12:12 PM, Philip M. Hofer (Frumph)<br>
<<a href="mailto:philip@frumph.net">philip@frumph.net</a>> wrote:<br>
> Everyone who has done as such never had their theme reviewed in the first<br>
> place to be blocked.<br>
><br>
> - Phil<br>
<br>
</div>True, but the WordPress theme updater works equally well for themes<br>
that have never been in the extend repository before now. All it cares<br>
about is version numbering, which can be whatever you like.</blockquote><div><br></div><div>If I'm reading him correctly, I think Phil's point was that we're not seeing Theme developers trying to assign-and-accept their own Theme tickets in order to facilitate a faster review for an updated Theme, but rather to bypass the review process entirely.</div>
<div><br></div><div>Just FYI: as of Sunday, the average age of New/Unassigned tickets was only 3.76 days. We're getting *much* better at turning reviews around in a more timely manner.</div><div><br></div><div>Chip </div>
</div>