<div dir="ltr">Hey, all: can we please use some common sense here? What Emil is saying has nothing to do with one-off, quick releases. We've all had to do that. (Oops; missed a bug...) Think instead about *long-term* and *average* release rate. <div>
<br></div><div>Over the long term, and for a mature Theme, once-weekly releases are absolutely too frequent. Are there exceptions? Sure. Something like adding a new color scheme/skin weekly might be a valid exception (since that was mentioned). But to reiterate what Justin said: if your Theme is so buggy that it needs *long-term* bugfixes once per week, then I'm not sure the Theme was reviewed properly to begin with. And at some point, you run out of features to add.</div>
<div><br></div><div>What Emil said isn't about setting a hard-and-fast cap, or setting a concrete rule. If you need to release an update, release an update. But if and when those updates become too frequent and too frivolous, we're probably going to say something to you about it. Whether it's a case of trying to game the download counts, or merely using the Theme directory as a VCS or a quality control system, when it happens (and currently, it does happen *rarely*), it's putting unnecessary burden on the Theme Review Team.</div>
<div><br></div><div>Currently, this is not a significant problem. Think of Emil's comments as an early attempt to pre-empt any future problems.</div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Fri, Jul 25, 2014 at 10:00 PM, Emil Uzelac <span dir="ltr"><<a href="mailto:emil@uzelac.me" target="_blank">emil@uzelac.me</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div class="gmail_default" style="font-family:arial,helvetica,sans-serif">As long as, yes you are absolutely correct :)</div>
</div><div class="gmail_extra"><br><br><div class="gmail_quote"><div><div class="h5">On Fri, Jul 25, 2014 at 9:53 PM, Srikanth Koneru <span dir="ltr"><<a href="mailto:tskk79@gmail.com" target="_blank">tskk79@gmail.com</a>></span> wrote:<br>
</div></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div class="h5"><div dir="ltr">So to wrap it up, updates have to be meaningful/of substance like Otto said but Emil's fiat of 1 month gap is voided?<br>
</div><div class="gmail_extra"><br><br><div class="gmail_quote"><div><div>On Sat, Jul 26, 2014 at 8:03 AM, Emil Uzelac <span dir="ltr"><<a href="mailto:emil@uzelac.me" target="_blank">emil@uzelac.me</a>></span> wrote:<br>
</div></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div><div dir="ltr"><div class="gmail_default" style="font-family:arial,helvetica,sans-serif">
Justin pays attention and is correct! </div>
<div class="gmail_default" style="font-family:arial,helvetica,sans-serif"><br></div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif">
No nothing new or something I am doing alone late on Friday, please see: <a href="http://lists.wordpress.org/pipermail/theme-reviewers/2014-June/018873.html" target="_blank">http://lists.wordpress.org/pipermail/theme-reviewers/2014-June/018873.html</a> and we have been contacting authors to either combine or stop meaningless updates. </div>
<div class="gmail_default" style="font-family:arial,helvetica,sans-serif"><br></div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif">I wasn't naming names, or calling for discussion, but I am glad that we got your attention now ;)</div>
<div class="gmail_default" style="font-family:arial,helvetica,sans-serif"> </div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Fri, Jul 25, 2014 at 9:13 PM, Justin Tadlock <span dir="ltr"><<a href="mailto:justin@justintadlock.com" target="_blank">justin@justintadlock.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">I'm OK with weekly releases (4 releases a month) if they're actually bug fixes and/or enhancements. I wouldn't knock anyone for that. I really wouldn't want to set some type of "time rule" either.<div>
<br></div><div>This is nothing the admins have discussed. Other than the thread I mentioned, this is the first I'm hearing of this too. I just wanted to clarify what I believe Emil was getting at.</div><div><br></div>
<div>What some of us have observed are probably a small fraction of people who might be submitting some updates for the sole purpose of upping their download counts. If we start noticing a trends like this, it's going to be a problem. I believe Emil wanted to preemptively help stop some of these types of problems before they got started.</div>
<div><br></div></div><div><div><div class="gmail_extra"><br><br><div class="gmail_quote">On Fri, Jul 25, 2014 at 8:17 PM, Srikanth Koneru <span dir="ltr"><<a href="mailto:tskk79@gmail.com" target="_blank">tskk79@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">There should be no time gap rule at all, Theme authors need not have to wait to release their next substantial update because of some arbitrary time limit.<br>
</div><div><div><div class="gmail_extra"><br><br><div class="gmail_quote">
On Sat, Jul 26, 2014 at 6:42 AM, Trent Lapinski <span dir="ltr"><<a href="mailto:trent@cyberchimps.com" target="_blank">trent@cyberchimps.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="auto"><div>What about biweekly updates?</div><div><br></div><div>We need some kind of structure that we can agree on. </div><div><br></div><div>Radically deciding on a Friday night to change everyone's release schedules is a little drastic is it not? I thought this was an open source community? How is this open source if I'm limited to how much I can change the code I submit? Sounds pretty closed to me.</div>
<div><br></div><div>It's not like this policy is even going to be enforceable let alone reduce tickets. This is simply a result of more theme authors and companies, which is what the WordPress Foundation wanted. Now that there's more of us submitting regularly suddenly we have to discontinue our release schedules, and no longer be able to maintain our themes?</div>
<div><br></div><div>I know you admins have a lot on your plates, but limiting the communities contributions is counterintuitive is it not?</div><div><div><br><div>--Trent Lapinski</div><div><a href="http://CyberChimps.com" target="_blank">CyberChimps.com</a></div>
Sent from my iPhone</div></div><div><div><div><br>On Jul 25, 2014, at 5:30 PM, Srikanth Koneru <<a href="mailto:tskk79@gmail.com" target="_blank">tskk79@gmail.com</a>> wrote:<br><br></div><blockquote type="cite">
<div><div dir="ltr"><div>I add new skin every week and try to be resource neutral by reviewing more than I submit.<br></div>Last week you were all dead set on avoiding subjective matters saying trying to judge those matters are a waste of your time and this week you drive straight into it.<br>
</div><div class="gmail_extra"><br><br><div class="gmail_quote">On Sat, Jul 26, 2014 at 5:45 AM, Justin Tadlock <span dir="ltr"><<a href="mailto:justin@justintadlock.com" target="_blank">justin@justintadlock.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div>This was briefly discussed on the mailing list last month. For reference: </div><div><a href="http://lists.wordpress.org/pipermail/theme-reviewers/2014-June/thread.html#18864" target="_blank">http://lists.wordpress.org/pipermail/theme-reviewers/2014-June/thread.html#18864</a></div>
<div><br></div><div>Otto made it pretty clear that frequent and meaningless updates are not allowed, so I don't think that should be a problem. This is something that's also done with plugins.</div><div><br></div>
<div>Basically, the idea though is to just add updates when there's something of significance like a new feature or a bug fix. Don't send updates to us when you're changing code formatting or updating your documentation.</div>
<div><br></div><div>If someone is sending in weekly bug fixes, then I don't think we're doing a very good job with the initial reviews. If you're sending in weekly enhancements, what more could you possibly be adding?</div>
<div><br></div><div>I do agree with Trent that it is a healthy dev strategy for some people/companies to have, but we also have to balance that with the facts of the situation. The situation is that we do human-powered theme reviews and still lack the manpower to handle them all. If we're constantly having to go through the priority update queue, it leaves little time for reviews on new themes. I don't like the situation, but this is where we're at. I might be starting to get into another discussion, so I'll just stop there.</div>
</div><div><div><div class="gmail_extra"><br><br><div class="gmail_quote">On Fri, Jul 25, 2014 at 7:07 PM, <span dir="ltr"><<a href="mailto:tskk79@gmail.com" target="_blank">tskk79@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Sorry too subjective, where is the definition of how small is too small. don't you guys have better things to do :)<br>
Sent from BlackBerry® on Airtel<br>
<div><div><br>
-----Original Message-----<br>
From: Jose Castaneda <<a href="mailto:jomcastaneda@gmail.com" target="_blank">jomcastaneda@gmail.com</a>><br>
Sender: "theme-reviewers" <<a href="mailto:theme-reviewers-bounces@lists.wordpress.org" target="_blank">theme-reviewers-bounces@lists.wordpress.org</a>>Date: Fri, 25 Jul 2014 16:37:30<br>
To: Discussion list for WordPress theme reviewers.<<a href="mailto:theme-reviewers@lists.wordpress.org" target="_blank">theme-reviewers@lists.wordpress.org</a>><br>
Reply-To: "Discussion list for WordPress theme reviewers."<br>
<<a href="mailto:theme-reviewers@lists.wordpress.org" target="_blank">theme-reviewers@lists.wordpress.org</a>><br>
Subject: Re: [theme-reviewers] Frequent Updates<br>
<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>
_______________________________________________<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></blockquote><blockquote type="cite"><div><span>_______________________________________________</span><br><span>theme-reviewers mailing list</span><br><span><a href="mailto:theme-reviewers@lists.wordpress.org" target="_blank">theme-reviewers@lists.wordpress.org</a></span><br>
<span><a href="http://lists.wordpress.org/mailman/listinfo/theme-reviewers" target="_blank">http://lists.wordpress.org/mailman/listinfo/theme-reviewers</a></span><br></div></blockquote></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></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>
<br></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>
<br></blockquote></div><br></div>
<br></div></div><div class="">_______________________________________________<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></div></blockquote></div><br></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></div>