Yes, the "known starting point" is not as feasible as it was before with multiple admins tending to the work now, but a straight up comparison of the existing themes open in Extend/Admin against Trac report #19 sorted by "Subject" does work well enough as I see it.<br>
<br><br>Cais.<br><br><div class="gmail_quote">On Mon, May 23, 2011 at 12:25 PM, Chip Bennett <span dir="ltr"><<a href="mailto:chip@chipbennett.net">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;">
Actually, I did a sync sometime early/mid-week last week.<div><br></div><div>The issue is, there's no reason the process should take an hour. And with multiple people tending to the list, keeping track of the known "starting" point is essentially impossible, while working backward through the list doesn't work all that easily.</div>
<div><br></div><div><font color="#888888">Chip</font><div><div></div><div class="h5"><br><br><div class="gmail_quote">On Mon, May 23, 2011 at 11:17 AM, Edward Caissie <span dir="ltr"><<a href="mailto:edward.caissie@gmail.com" target="_blank">edward.caissie@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
I just completely brought it into sync in less than an hour ... not so sure where the issues are if from what I am reading it was almost two weeks out of sync.<br><br><br>Cais.<div><div></div><div><br><br><div class="gmail_quote">
On Mon, May 23, 2011 at 11:39 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">I disagree that the current workflow is efficient or feasibly able to be maintained. This might make a good agenda item for our upcoming meeting.<div>
<br></div><div><font color="#888888">Chip</font><div><div></div><div><br><br><div class="gmail_quote">On Mon, May 23, 2011 at 10:36 AM, Edward Caissie <span dir="ltr"><<a href="mailto:edward.caissie@gmail.com" target="_blank">edward.caissie@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">The current workflow works, as long as it is attended to every day ... unfortunately I have been very busy with other projects to keep it within the maximum 24 hour turn-around I expected/maintained.<br>
<br>As my plans to day have been completely blown out of the water, I'll go in and make sure everything is back in sync (approved, not-approved, etc.)<br>
<br><br>Cais.<div><div></div><div><br><br><div class="gmail_quote">On Mon, May 23, 2011 at 8:52 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">
Synching is not only a manual process, it is a rather tedious manual process. Extend has no knowledge of a given ticket's resolution, and we currently have no way in Trac of queueing tickets that require resolution.<div>
<br></div><div>I have an idea, that we can try. It may or may not work, but it's worth a shot.</div><div><br></div><div>REVIEWERS: when you close a ticket as APPROVED, add the following keyword to the ticket: "syncapproved". That way, we can add a Trac report around this keyword, and won't have to search for approved Themes that need to be synced. This way, whomever does the sync can just remove the keyword from the ticket.</div>
<div><br></div><div>(If you want to be extra helpful, for tickets closed as not-approved or newer-version-uploaded, add this keyword to the ticket: "synchold". But getting the *approved* Themes synced as quickly as possible is far more important than syncing *old* (i.e. not-approved or newer-version-uploaded) tickets.)</div>
<div><br></div><div>After having helped with the Trac-Extend sync for a few weeks now, I'm fairly convinced that this method would be more efficient than the current workflow.</div><div><br></div><div><font color="#888888">Chip<br>
<br></font><div class="gmail_quote"><div>
On Mon, May 23, 2011 at 6:36 AM, Otto <span dir="ltr"><<a href="mailto:otto@ottodestruct.com" target="_blank">otto@ottodestruct.com</a>></span> wrote:<br></div><div><div></div><div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div>On Mon, May 23, 2011 at 5:55 AM, Daniel Tara <<a href="mailto:contact@onedesigns.com" target="_blank">contact@onedesigns.com</a>> wrote:<br>
> Is there anything wrong with the synch operation?<br>
> Otto, do you know anything about this?<br>
<br>
</div>There is no sync operation, all the themes have to be approved<br>
manually by the mods of the theme system, which is basically Chip,<br>
Pross, Cais, and Emil.<br>
<font color="#888888"><br>
-Otto<br>
</font><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>
</div></div></blockquote></div></div></div><br></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><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><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">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>