[theme-reviewers] Frequent Updates

Sat Jul 26 02:53:20 UTC 2014

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?

On Sat, Jul 26, 2014 at 8:03 AM, Emil Uzelac <emil at uzelac.me> wrote:

> Justin pays attention and is correct!
>
> No nothing new or something I am doing alone late on Friday, please see:
> http://lists.wordpress.org/pipermail/theme-reviewers/2014-June/018873.html
> and we have been contacting authors to either combine or stop meaningless
> updates.
>
> I wasn't naming names, or calling for discussion, but I am glad that we
> got your attention now ;)
>
>
>
> On Fri, Jul 25, 2014 at 9:13 PM, Justin Tadlock <justin at justintadlock.com>
> wrote:
>
>> 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.
>>
>> 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.
>>
>> 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.
>>
>>
>>
>> On Fri, Jul 25, 2014 at 8:17 PM, Srikanth Koneru <tskk79 at gmail.com>
>> wrote:
>>
>>> 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.
>>>
>>>
>>> On Sat, Jul 26, 2014 at 6:42 AM, Trent Lapinski <trent at cyberchimps.com>
>>> wrote:
>>>
>>>> What about biweekly updates?
>>>>
>>>> We need some kind of structure that we can agree on.
>>>>
>>>> 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.
>>>>
>>>> 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?
>>>>
>>>> I know you admins have a lot on your plates, but limiting the
>>>> communities contributions is counterintuitive is it not?
>>>>
>>>> --Trent Lapinski
>>>> CyberChimps.com
>>>> Sent from my iPhone
>>>>
>>>> On Jul 25, 2014, at 5:30 PM, Srikanth Koneru <tskk79 at gmail.com> wrote:
>>>>
>>>> I add new skin every week and try to be resource neutral by reviewing
>>>> more than I submit.
>>>> 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.
>>>>
>>>>
>>>> On Sat, Jul 26, 2014 at 5:45 AM, Justin Tadlock <
>>>> justin at justintadlock.com> wrote:
>>>>
>>>>> This was briefly discussed on the mailing list last month.  For
>>>>> reference:
>>>>>
>>>>> http://lists.wordpress.org/pipermail/theme-reviewers/2014-June/thread.html#18864
>>>>>
>>>>> 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.
>>>>>
>>>>> 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.
>>>>>
>>>>> 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?
>>>>>
>>>>> 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.
>>>>>
>>>>>
>>>>> On Fri, Jul 25, 2014 at 7:07 PM, <tskk79 at gmail.com> wrote:
>>>>>
>>>>>> Sorry too subjective, where is the definition of how small is too
>>>>>> small.  don't you guys have better things to do :)
>>>>>> Sent from BlackBerry® on Airtel
>>>>>>
>>>>>> -----Original Message-----
>>>>>> From: Jose Castaneda <jomcastaneda at gmail.com>
>>>>>> Sender: "theme-reviewers" <
>>>>>> theme-reviewers-bounces at lists.wordpress.org>Date: Fri, 25 Jul 2014
>>>>>> 16:37:30
>>>>>> To: Discussion list for WordPress theme reviewers.<
>>>>>> theme-reviewers at lists.wordpress.org>
>>>>>> Reply-To: "Discussion list for WordPress theme reviewers."
>>>>>>  <theme-reviewers at lists.wordpress.org>
>>>>>> Subject: Re: [theme-reviewers] Frequent Updates
>>>>>>
>>>>>> _______________________________________________
>>>>>> 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
>>>
>>>
>>
>> _______________________________________________
>> 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/20140726/136fb0a6/attachment-0001.html>