On 15.06.2014 13:20, Daniel Molkentin wrote:
> Because we still want to await feedback before pushing (a major) version
> onto everyone.
> It's always been that way, but I wanted to be more conservative for a
> major release.
when 1.6._0_ had gotten released - made all the sense to me.
I now wonder when you will push 1.6._1_ to upgrade 1.5.4 clients.
Am 04.07.2014 um 14:00 schrieb Daniel Molkentin <[hidden email]>:
> Again, as soon as we were sure nothing major was impacting a broad rollout. For 1.6.0, that was a rather bad memleak.
> Also, we had to modify the updater to ensure it does not advertise the update to Mac OS 10.6 users, since 1.6 now
> requires a minimum version of 1.6.
this is well understood - and very much appreciated.
> That said, the updater should now advertise 1.6.1.
One last question: what is the average period of time you let pass by
before you let the updater announce a new version? Just to avoid nagging
you too early...
On 04.07.2014 16:58, Carsten Schiefner wrote:
> One last question: what is the average period of time you let pass by
> before you let the updater announce a new version? Just to avoid
> nagging you too early...
It's mostly based on the influx on the bug tracker and the time it takes
to triage the initial bugs (i.e. assess if they are isolated cases or if
they can cause general problems). Usually that should be done after a
week or so.
www.owncloud.com - Your Data, Your Cloud, Your Way!