Otto and I discussed automation briefly earlier today ... not likely to happen, but I will let Otto explain the reasons (again).<br><br><br>Cais.<br><br><div class="gmail_quote">On Mon, May 23, 2011 at 5:40 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;">I would also suggest that, if we have such a workflow in place, it might be entirely possible to *automate* the process, through some sort of script. That's a question for Otto.<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 4:39 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">
I think it's worth a trial run. The efficiency losses due to having to modify each ticket upon Sync will be far outweighed by the efficiency gains of not having to do the back-and-forth scanning between the Extend Sync list, and the "Every Theme Under the Sun" Trac report.<div>
<br></div><div>The workflow becomes something like this:</div><div><br></div><div>1) Open Extend/Admin</div><div>2) Open Trac Report: Tickets to sync</div><div>3) Find Trac ticket in Extend; Mark as Live or Old</div><div>
4) Open Trac ticket in new tab, remove modifier, Save, close tab</div><div><br></div><div>Which is much easier than the workflow you've published a couple times. :)</div><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 4:31 PM, 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">
Dang ... I forgot about that. Using the method of adding an action or process to indicate the Theme *needs* to be sync'd also dictates an additional action is required to say the Theme *has been* sync'd.<br><br>Given the above, I do not agree with the benefits of this method, now.<br>
<br><br>Cais.<div><div></div><div><br><br><div class="gmail_quote">On Mon, May 23, 2011 at 5:21 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">
I would think that the report simply needs to look for the modifier. When the Theme is synched, the modifier is changed, so that the ticket no longer shows up in the list.<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 4:08 PM, 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">
That may work, perhaps in conjunction with a report of Themes modified in the last (arbitrary number) 7 days?<br><br><br>Cais<div><div></div><div><br><br><div class="gmail_quote">On Mon, May 23, 2011 at 3:24 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">That would work, too.<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 12:28 PM, Otto <span dir="ltr"><<a href="mailto:otto@ottodestruct.com" target="_blank">otto@ottodestruct.com</a>></span> wrote:<br>
<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 7:52 AM, Chip Bennett <<a href="mailto:chip@chipbennett.net" target="_blank">chip@chipbennett.net</a>> wrote:<br>
</div><div>> REVIEWERS: when you close a ticket as APPROVED, add the following keyword to<br>
> the ticket: "syncapproved". That way, we can add a Trac report around this<br>
> keyword, and won't have to search for approved Themes that need to be<br>
> synced. This way, whomever does the sync can just remove the keyword from<br>
> the ticket.<br>
><br>
> (If you want to be extra helpful, for tickets closed as not-approved or<br>
> newer-version-uploaded, add this keyword to the ticket: "synchold". But<br>
> getting the *approved* Themes synced as quickly as possible is far more<br>
> important than syncing *old* (i.e. not-approved or newer-version-uploaded)<br>
> tickets.)<br>
><br>
> After having helped with the Trac-Extend sync for a few weeks now, I'm<br>
> fairly convinced that this method would be more efficient than the current<br>
> workflow.<br>
<br>
</div>I think there's probably a better way than using keywords for this.<br>
It's kind of a loose field, not suitable for everything.<br>
<br>
While we're not using them on theme's trac at the moment, there are<br>
other fields we can use for this. Priority and severity and component<br>
spring to mind. These are just dropdowns with items we can put in<br>
them.<br>
<br>
What if I changed the Priority field to have "normal" and "needs-sync"<br>
as options? Then reviewers could mark the ticket as in need of syncing<br>
when they approve it and such.<br>
<div><div></div><div><br>
-Otto<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>
</div></div></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" 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>
</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>