<div dir="ltr">Mario,<div><br></div><div style>I'm not sure I'm completely following your question.</div><div style><br></div><div style>I'm talking specifically about two cases:</div><div style><br></div><div style>
1. Where in the current ticket, the reviewer says, "hey, I found these one or two, really minor, but required issues; I'm approving the Theme, but please fix them in the next revision"</div><div style>2. Where in the current ticket, the reviewer says, "hey, you missed this required thing; please fix it and re-submit. I'll hold your ticket open so you don't have to wait in line again"</div>
<div style><br></div><div style>Both of these things do help expedite the process, and make it less frustrating for the developer. But, we have to make sure that we verify that the *required* issues identified in each case are resolved in the subsequent ticket.</div>
<div style><br></div><div style>I *think* you're talking about "holding open" tickets in general? If so, that's not something that we've really addressed. Might be worth a discussion, perhaps?</div><div style>
<br></div><div style>Thanks,</div><div style><br></div><div style>Chip</div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Mon, Jan 7, 2013 at 9:59 AM, Mario Peshev <span dir="ltr"><<a href="mailto:mario@peshev.net" target="_blank">mario@peshev.net</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Chip, isn't it 'good to have' to keep tickets open? In my opinion most themes need approx. 3-4 iterations to get in and given the stats, that might take few months even though fixes might take a few hours.<div>
<br></div><div>IMO theme authors that prioritize theme submissions should have a fast lane open when the feedback could apparently be resolved in a few hours. This is in case reviewers conduct a complete review and not a quick look only.<span class="HOEnZb"><font color="#888888"><br clear="all">
<div><br>Mario Peshev<br>WordPress Engineer, Open Source Consultant<br><a href="http://www.linkedin.com/in/mpeshev" target="_blank">http://www.linkedin.com/in/mpeshev</a><br><div><a href="http://me.peshev.net/" target="_blank">http://me.peshev.net</a></div>
<div><br></div></div></font></span><div class="im">
<br><br><div class="gmail_quote">On Mon, Jan 7, 2013 at 4:11 PM, 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>This is especially important for previously approved (Priority #1) tickets, since such tickets already receive an expedited, diff-only review.</div><div><br></div><div>Two, we have a great system in place, that allows a reviewer to hold a ticket open if only minor issues need to be addressed, such that once a revision is submitted, the reviewer can continue the current review in the new ticket. If the previous ticket is still open, the new ticket should be left for the reviewer of the previous ticket, so that the previous review may be continued.</div>
<div><br></div><div>I had two such tickets over the weekend: both had previous-ticket "required" issues that were not addressed. I left the tickets open to allow for a review continuation. Both developers uploaded revisions, but when I went in this morning to take the tickets, both had been assigned, reviewed, and closed. Unfortunately, in both cases, the review failed to indicate whether previous-ticket "required" issues had been addressed.</div>
<div></div></blockquote></div><br></div></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><br></div>