<p dir="ltr">Absolutely not. It stays as is :-)</p>
<div class="gmail_quote">On Oct 30, 2013 2:11 PM, "Jasper Kips" <<a href="mailto:jasper@planetkips.nl">jasper@planetkips.nl</a>> wrote:<br type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="auto"><div>So, punishing theme authors....<br><br>Jasper Kips,<div>Always waiting for the ricochet</div></div><div><br>Op 30 okt. 2013 om 19:54 heeft Srikanth Koneru <<a href="mailto:tskk79@gmail.com" target="_blank">tskk79@gmail.com</a>> het volgende geschreven:<br>
<br></div><blockquote type="cite"><div><div dir="ltr">If Otto/Nacin can lock down #2/#3/#4 till #1 is empty, that may work too.<br></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Thu, Oct 31, 2013 at 12:21 AM, Chip Bennett <span dir="ltr"><<a href="mailto:chip@chipbennett.net" target="_blank">chip@chipbennett.net</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">I would hate to have to put a stipulation on the review incentive, along the lines of requiring that the daily average # of Themes in Priority #1 queue must be less than the daily average # of Themes in the Priority #3/4 queues, but if Priority #1 keeps getting bypassed, we may have to go that route.<div>
<br></div><div>As much as I would love to add a second incentive to the Priority #1 queue, it shouldn't be *required* to do so, just to ensure that reviewers adhere to the ticket prioritization.</div></div><div>
<div><div class="gmail_extra">
<br><br><div class="gmail_quote">On Wed, Oct 30, 2013 at 2:35 PM, Emil Uzelac <span dir="ltr"><<a href="mailto:emil@uzelac.me" target="_blank">emil@uzelac.me</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="ltr">#1 Priority should always be prioritized and that's something we have been<div>preaching for awhile now. </div><div><br></div><div>At the same time once assigned it should be reviewed asap, not tomorrow, </div>
<div>not within 7 days.</div><div><br></div><div>The past few #1 assignments might be new reviewers, however they're </div><div>experienced themers and as far as I know we do not assign #1 to newbies.</div><div><br></div>
<div>System is not broken and we just need to give some time, that's all :)</div></div><div><div><div class="gmail_extra"><br><br><div class="gmail_quote">On Wed, Oct 30, 2013 at 1:21 PM, Bruce Wampler <span dir="ltr"><<a href="mailto:weavertheme@gmail.com" target="_blank">weavertheme@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div><div><div><div><div><div><div>It turns out the reviewer did not have his notifications set properly, and didn't even know he had been assigned the theme.<br>
<br></div>And I was not talking about standard theme reviews - but reviews for Priority 1 themes. As I noted, these often contain important bug fixes (although that should probably be pointed out when the theme is submitted), and I didn't think Priority 1 themes were supposed to get the same treatment as the rest of the themes in the queue. That is why Priority 1 was created.<br>
<br></div>And at one point, I thought only experienced reviewers were supposed to handle Priority 1 themes - there was a big push not that long ago to try to get Priority 1 themes pushed through. But it seems now that with all the incentives, the new themes are getting pushed through faster than existing themes that are simply updating.<br>
<br></div>I think this need fixing. I understand everyone is a volunteer, but all the previous efforts for the Priority 1 themes seems to be broken now:<br><br></div>1. Apparently new reviewers are now getting assigned Priority 1 themes. In at least my case, this led to a several days delay because the new reviewer was not yet totally familiar with the process.<br>
<br></div>2. But Priority 1 reviews are now the slowest to get reviews. New themes seem to be flowing smoothly through the process faster than existing themes.<br><br></div>3. Maybe there needs to be a mechanism for indicating critical bug updates. It happens, and what is now about a two week turnaround for a theme update seems too long - especially given new themes are getting through faster.<br>
<br></div>I appreciate everyone's effort - and I'm perfectly happy to wait my turn. It just seems that things are broken for Priority 1 themes.<br><br><br><div><div><div><div><div><div><div><div><div><div class="gmail_extra">
<br><br><div class="gmail_quote"><div>On Wed, Oct 30, 2013 at 10:32 AM, Christine Rondeau <span dir="ltr"><<a href="mailto:christine@bluelimemedia.com" target="_blank">christine@bluelimemedia.com</a>></span> wrote:<br>
</div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div>
<div dir="ltr">That's happened to me before as well. Once someone takes your site and reviews it, doesn't mean they will do it in a day. I once had to wait for a week for someone to complete the review. <div><br>
</div>
<div>I think that's normal, we all have things to do. </div></div><div class="gmail_extra"><br clear="all"><div><i><b></b></i>Christine Rondeau<br>Bluelime Media<a href="http://www.bluelimemedia.com" target="_blank"></a><br>
</div></div></div><div>_______________________________________________<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>
<br></div></blockquote></div><br></div></div></div></div></div></div></div></div></div></div></div>
<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>
<br></blockquote></div><br></div>
</div></div><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>
<br></blockquote></div><br></div>
</div></div><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>
<br></blockquote></div><br></div>
</div></blockquote><blockquote type="cite"><div><span>_______________________________________________</span><br><span>theme-reviewers mailing list</span><br><span><a href="mailto:theme-reviewers@lists.wordpress.org" target="_blank">theme-reviewers@lists.wordpress.org</a></span><br>
<span><a href="http://lists.wordpress.org/mailman/listinfo/theme-reviewers" target="_blank">http://lists.wordpress.org/mailman/listinfo/theme-reviewers</a></span><br></div></blockquote></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>