<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META content="text/html; charset=iso-8859-1" http-equiv=Content-Type>
<META name=GENERATOR content="MSHTML 8.00.6001.18928">
<STYLE></STYLE>
</HEAD>
<BODY bgColor=#ffffff>
<DIV><FONT size=2 face=Arial>Yeah not sure your following, there's a list of all
the versions for that theme on the ticket, if that ticket has a note on it to
"see ticket #whatever" then we know to close it off with newer version uploaded
and move to the latest that was uploaded, which we all pretty much do if there's
a note. It's up to the theme reviewer to move to the latest, not a
policy. Policy is first come first serve.</FONT></DIV>
<DIV><FONT size=2 face=Arial></FONT> </DIV>
<DIV><FONT size=2 face=Arial>If there's no note, then when flagged 'newer
version uploaded' thats all it is, flagged that; it's still in the system just
not on the reports. The person's theme will just have to wait in
line like everyone else has to.</FONT></DIV>
<DIV><FONT size=2 face=Arial></FONT> </DIV>
<DIV><FONT size=2 face=Arial>This raises some concern that I feel your making
that it should be policy. It has been discussed several times before and
to be fair to everyone who doesn't need to upload a newer version that it stays
consistent with this methodology. The important thing is to
keep it fair to everyone, not just the person who uploads a newer
version. So giving the leeway to do it for those who make an effort
to point out the newest upload gives us the a-ok to go ahead and move to the
latest upload. Which again, is the fair thing to do.</FONT></DIV>
<DIV><FONT size=2 face=Arial></FONT> </DIV>
<DIV> </DIV>
<DIV><FONT size=2 face=Arial></FONT> </DIV>
<DIV><FONT size=2 face=Arial></FONT> </DIV>
<DIV><FONT size=2 face=Arial></FONT> </DIV>
<DIV><FONT size=2 face=Arial></FONT> </DIV>
<BLOCKQUOTE
style="BORDER-LEFT: #000000 2px solid; PADDING-LEFT: 5px; PADDING-RIGHT: 0px; MARGIN-LEFT: 5px; MARGIN-RIGHT: 0px">
<DIV style="FONT: 10pt arial">----- Original Message ----- </DIV>
<DIV
style="FONT: 10pt arial; BACKGROUND: #e4e4e4; font-color: black"><B>From:</B>
<A title=satish.iitg@gmail.com href="mailto:satish.iitg@gmail.com">Satish
Gandham</A> </DIV>
<DIV style="FONT: 10pt arial"><B>To:</B> <A
title=theme-reviewers@lists.wordpress.org
href="mailto:theme-reviewers@lists.wordpress.org">theme-reviewers@lists.wordpress.org</A>
</DIV>
<DIV style="FONT: 10pt arial"><B>Sent:</B> Friday, December 17, 2010 10:33
AM</DIV>
<DIV style="FONT: 10pt arial"><B>Subject:</B> Re: [theme-reviewers] How does
the theme review queue work</DIV>
<DIV><BR></DIV><B>>No, old tickets don't disappear. Every new upload
creates a ticket.<BR>>Old tickets with new uploads will get (manually)
marked as "new<BR>>version uploaded" and closed in favor of the new
version.</B><BR><BR>Yes, but the closed tickets are never looked again. Only
the order in priority #2 queue is followed as is, with out referring to the
closed tickets.<BR><A
href="http://themes.trac.wordpress.org/report/3">http://themes.trac.wordpress.org/report/3</A><BR><BR>The
oldest ticket in the above queue is 3 weeks old, if the developer uploads a
new ticket before its accepted by a reviewer, his current ticket will be
closed manually and the new ticket will be at the bottom of the queue and he
has to wait again for another 3 weeks.<BR><BR>Can something be done about it,
or should i wait till a reviewer picks up my theme for review and then upload
the new version before he closes it.<BR><BR><BR><BR><BR>
<P>
<HR>
<P></P>_______________________________________________<BR>theme-reviewers
mailing
list<BR>theme-reviewers@lists.wordpress.org<BR>http://lists.wordpress.org/mailman/listinfo/theme-reviewers<BR></BLOCKQUOTE></BODY></HTML>