Doh ... forgot the BuddyPress themes.<br><br><br clear="all">Cais.<br>
<br><br><div class="gmail_quote">On Mon, Jan 23, 2012 at 2:41 PM, Doug Stewart <span dir="ltr"><<a href="mailto:zamoose@gmail.com">zamoose@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<a href="http://wordpress.org/extend/themes/elbee-elgee" target="_blank">http://wordpress.org/extend/themes/elbee-elgee</a>. Should be at 1.3.5,<br>
1.3.4 is showing in the repo.<br>
<div class="HOEnZb"><div class="h5"><br>
On Mon, Jan 23, 2012 at 2:18 PM, Edward Caissie<br>
<<a href="mailto:edward.caissie@gmail.com">edward.caissie@gmail.com</a>> wrote:<br>
> I sync'd everything this morning ... which theme are you referring to?<br>
><br>
><br>
> Cais.<br>
><br>
><br>
><br>
> On Mon, Jan 23, 2012 at 2:11 PM, Doug Stewart <<a href="mailto:zamoose@gmail.com">zamoose@gmail.com</a>> wrote:<br>
>><br>
>> Slightly O/T:<br>
>> Can we get a repo sync sometime soon? I think there are a few theme<br>
>> updates (including one of my own) stuck in the approved-but-not-synced<br>
>> Purgatory.<br>
>><br>
>> On Mon, Jan 23, 2012 at 12:57 PM, Kirk Wight <<a href="mailto:kwight@kwight.ca">kwight@kwight.ca</a>> wrote:<br>
>> > Good point about checking previous tickets before grabbing one - thanks.<br>
>> ><br>
>> ><br>
>> > On 23 January 2012 12:53, Chip Bennett <<a href="mailto:chip@chipbennett.net">chip@chipbennett.net</a>> wrote:<br>
>> >><br>
>> >> This will require reviewer attention, but should also be facilitated by<br>
>> >> the current/previous reviewer, and the developer. When uploading a<br>
>> >> revision,<br>
>> >> the developer needs to post a link to the new ticket as a comment to<br>
>> >> the<br>
>> >> old/current ticket, and then the reviewer should then assign himself<br>
>> >> the new<br>
>> >> ticket, and close the old/current ticket as "newer-version-uploaded".<br>
>> >><br>
>> >> Also, when assigning yourself a new ticket, quickly check the status of<br>
>> >> the previous ticket, just to be sure.<br>
>> >><br>
>> >> Thanks,<br>
>> >><br>
>> >> Chip<br>
>> >><br>
>> >> On Mon, Jan 23, 2012 at 11:33 AM, Kirk Wight <<a href="mailto:kwight@kwight.ca">kwight@kwight.ca</a>> wrote:<br>
>> >>><br>
>> >>> Chip recently outlined a new policy:<br>
>> >>><br>
>> >>> "...any review-based Theme revision that is submitted within two days<br>
>> >>> of<br>
>> >>> the previous review will be assigned to the previous-ticket reviewer,<br>
>> >>> and<br>
>> >>> the review continued on the new ticket."<br>
>> >>><br>
>> >>> (<a href="http://make.wordpress.org/themes/2011/12/15/getting-the-review-queue-back-on-track/" target="_blank">http://make.wordpress.org/themes/2011/12/15/getting-the-review-queue-back-on-track/</a>)<br>
>> >>><br>
>> >>> Does this require reviewer attention, or is it automated by Trac (I've<br>
>> >>> no<br>
>> >>> idea what Trac is capable of)? I just realized I was able to step<br>
>> >>> on SeizedPropaganda's toes by grabbing the next unassigned ticket in<br>
>> >>> priority #1, which was a new version uploaded<br>
>> >>> (<a href="http://themes.trac.wordpress.org/ticket/6250" target="_blank">http://themes.trac.wordpress.org/ticket/6250</a>) within a day of the<br>
>> >>> original<br>
>> >>> ticket already assigned<br>
>> >>> to SeizedPropaganda (<a href="http://themes.trac.wordpress.org/ticket/6183" target="_blank">http://themes.trac.wordpress.org/ticket/6183</a>).<br>
>> >>><br>
>> >>> Thanks!<br>
>> >>><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>
>> >><br>
>> >><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>
>> ><br>
>> ><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>
>><br>
>><br>
>><br>
>> --<br>
>> -Doug<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>
><br>
><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>
<br>
<br>
<br>
--<br>
-Doug<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>
</div></div></blockquote></div><br>