[theme-reviewers] Clarifying trac process

Edward Caissie edward.caissie at gmail.com
Sat Feb 18 02:38:14 UTC 2012


@Caroline - The oldest ticket is still open holding your place in the
queue. I went in and noted the newest ticket on it ... then closed two of
the three "middle" tickets yesterday, IIRC.

The standard process, which you followed was to note each new version on
the older ticket(s). To simplify, just note the newest ticket on the oldest
ticket when there are multiple tickets that have not been reviewed.

I hope that makes a bit more sense.


Cais.

PS: @Emil - No worries (*grin*) EAC.

On Fri, Feb 17, 2012 at 9:31 PM, Caroline Moore <calobee at gmail.com> wrote:

> Sure, Cais, it's #6355
>
> On Feb 17, 2012, at 9:22 PM, Edward Caissie wrote:
>
> @Caroline, which tickets are you referring to? I'd like to look into it ...
>
>
> Cais.
>
>
> On Fri, Feb 17, 2012 at 7:05 PM, Emil Uzelac <emil at themeid.com> wrote:
>
>> I see no harm however what I would do instead is to note the closed
>> ticket and nicely request that newest Theme should be reviewed when the old
>> one is closed. When I started little over year ago @Cais was kind enough to
>> explain this and we're passing that onto newer reviewers.
>>
>> Emil
>>
>>
>> On Fri, Feb 17, 2012 at 5:47 PM, Caroline Moore <calobee at gmail.com>wrote:
>>
>>> Thanks Emil, that's what I thought. Am I Ok to reopen the old ticket
>>> then?
>>>
>>> Sent from my iPhone
>>>
>>> On Feb 17, 2012, at 6:23 PM, Emil Uzelac <emil at themeid.com> wrote:
>>>
>>> Reviewer needs to review your latest Theme when older version is closed.
>>> On Feb 17, 2012 4:58 PM, "Caroline Moore" <calobee at gmail.com> wrote:
>>>
>>>> Hi all,
>>>>
>>>> I recently uploaded a new version of one of my not-yet-approved themes
>>>> and commented on the old ticket with a link to the new version. Another
>>>> reviewer closed the old ticket before the new one was accepted, so my theme
>>>> dropped back to the bottom of the review queue.
>>>>
>>>> I was under the impression we should wait to mark older tickets as
>>>> closed-newer-version-uploaded until the latest version of the theme was
>>>> accepted for review, so themes more or less kept their place in the queue
>>>> and devs weren't penalized for updating their themes. (This is what I've
>>>> been doing as a reviewer, at least... maybe I'm wrong?) Can someone clarify?
>>>>
>>>> Better yet, is there a formal trac process written somewhere? Is there
>>>> a need for something like that, with the sudden influx of new reviewers
>>>> (like myself)?
>>>>
>>>>
>>>> Thanks,
>>>> Caro
>>>> _______________________________________________
>>>> theme-reviewers mailing list
>>>> theme-reviewers at lists.wordpress.org
>>>> http://lists.wordpress.org/mailman/listinfo/theme-reviewers
>>>>
>>> _______________________________________________
>>> theme-reviewers mailing list
>>> theme-reviewers at lists.wordpress.org
>>> http://lists.wordpress.org/mailman/listinfo/theme-reviewers
>>>
>>>
>>> _______________________________________________
>>> theme-reviewers mailing list
>>> theme-reviewers at lists.wordpress.org
>>> http://lists.wordpress.org/mailman/listinfo/theme-reviewers
>>>
>>>
>>
>> _______________________________________________
>> theme-reviewers mailing list
>> theme-reviewers at lists.wordpress.org
>> http://lists.wordpress.org/mailman/listinfo/theme-reviewers
>>
>>
> _______________________________________________
> theme-reviewers mailing list
> theme-reviewers at lists.wordpress.org
> http://lists.wordpress.org/mailman/listinfo/theme-reviewers
>
>
>
> _______________________________________________
> theme-reviewers mailing list
> theme-reviewers at lists.wordpress.org
> http://lists.wordpress.org/mailman/listinfo/theme-reviewers
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.wordpress.org/pipermail/theme-reviewers/attachments/20120217/94878f60/attachment.htm>


More information about the theme-reviewers mailing list