<html><body><div style="color:#000; background-color:#fff; font-family:HelveticaNeue, Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif;font-size:12pt">Yeah as Srikanth said, this month it seems it's going to be tough. But I have seen that some theme reveiwers grabbing all the tickets to them selves as soon as the ticket comes in theme updates. Is this allowed? Shouldn't one make a review on one theme then jump into another. I think whether it's theme update or new theme, one should make complete review and then only jump into another ticket instead of grabbing all at once. What do you have to say about this?<br><div><span><br></span></div><div style="display: block;" class="yahoo_quoted"> <div style="font-family: HelveticaNeue, Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif; font-size: 12pt;"> <div style="font-family: HelveticaNeue, Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif; font-size: 12pt;"> <div dir="ltr">
<font face="Arial" size="2"> On Tuesday, April 8, 2014 7:40 AM, Srikanth Koneru <tskk79@gmail.com> wrote:<br> </font> </div> <div class="y_msg_container"><div id="yiv8022438095"><div dir="ltr">yep, good problem but how do we get new themes submitted and how does lack of tickets effect the incentive program, its going to be hard to get 1/10 or 1/4th this month for many of us. I am watching my queue all day and cutting back on sleep and still find it hard to catch a ticket :(<br>
</div><div class="yiv8022438095gmail_extra"><br><br><div class="yiv8022438095gmail_quote">On Tue, Apr 8, 2014 at 3:31 AM, Chip Bennett <span dir="ltr"><<a href="" rel="nofollow" ymailto="mailto:chip@chipbennett.net" target="_blank">chip@chipbennett.net</a>></span> wrote:<br>
<blockquote class="yiv8022438095gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"><div dir="ltr">All,<div><br></div><div>A couple requests: </div><div><br></div><div><b>Please do not "bump" comments in open tickets</b>. I follow-up on on open/assigned tickets based on age of the ticket, as determined by latest activity. Generally, I follow up on tickets that have had no activity for over one week, and then close tickets that have not had activity for another week. So, if you "bump" the comments in the tickets, by asking for updates, it "resets" the clock on admin follow-up activity, meaning that abandoned tickets will stay open for longer.</div>
<div><br></div><div>Also, except for extreme circumstances, <b>please do not close tickets as "not approved"</b>. Per our current workflow, we leave the ticket open to allow for developer response. We want the ticket to stay open if the developer is responsive, so that all updates take place in the same ticket. If the developer fails to respond, I'll catch it in the ticket follow-up, and will take care of closing them.</div>
<div><br></div><div>Thanks for all of your contributions. We're currently running out of tickets to be assigned, which is a very good problem!</div><span class="yiv8022438095HOEnZb"><font color="#888888"><div><br></div><div>Chip</div>
</font></span></div>
<br>_______________________________________________<br>
theme-reviewers mailing list<br>
<a href="" rel="nofollow" ymailto="mailto:theme-reviewers@lists.wordpress.org" target="_blank">theme-reviewers@lists.wordpress.org</a><br>
<a href="" rel="nofollow" target="_blank">http://lists.wordpress.org/mailman/listinfo/theme-reviewers</a><br>
<br></blockquote></div><br></div></div><br>_______________________________________________<br>theme-reviewers mailing list<br><a href="" ymailto="mailto:theme-reviewers@lists.wordpress.org">theme-reviewers@lists.wordpress.org</a><br><a href="" target="_blank">http://lists.wordpress.org/mailman/listinfo/theme-reviewers</a><br><br><br></div> </div> </div> </div> </div></body></html>