Return-Path: X-Original-To: apmail-incubator-ooo-dev-archive@minotaur.apache.org Delivered-To: apmail-incubator-ooo-dev-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id B705EDE9F for ; Thu, 27 Sep 2012 05:03:38 +0000 (UTC) Received: (qmail 75969 invoked by uid 500); 27 Sep 2012 05:03:38 -0000 Delivered-To: apmail-incubator-ooo-dev-archive@incubator.apache.org Received: (qmail 75754 invoked by uid 500); 27 Sep 2012 05:03:37 -0000 Mailing-List: contact ooo-dev-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: ooo-dev@incubator.apache.org Delivered-To: mailing list ooo-dev@incubator.apache.org Received: (qmail 75722 invoked by uid 99); 27 Sep 2012 05:03:36 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 27 Sep 2012 05:03:36 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=5.0 tests=RCVD_IN_DNSWL_LOW,SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (athena.apache.org: local policy) Received: from [74.125.82.43] (HELO mail-wg0-f43.google.com) (74.125.82.43) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 27 Sep 2012 05:03:28 +0000 Received: by wgbdq11 with SMTP id dq11so822208wgb.0 for ; Wed, 26 Sep 2012 22:03:06 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding :x-gm-message-state; bh=weuKuQkBDmzUjpa5gkNsgXQHVLPk43uIvp9LIrvTgZQ=; b=a2+RFkjTT5wmOe8t/f4zRKcr6sU09G6dNzC6bxTr/c0qPpTDWsFZNWW3gI9NV1MuNu oACc6AJmzrhqvQ9T4YxK1Sph7rkIvys6HuMH5U8aXrGXhLB4O6JAqV2C7d9xXU7k5IyH ig97STCzpvmiqZFQPZlYFQr94GkZZ5TfROpnaDbn/cBTP5pamf8ZwXaAP9TCCn2ID/hu V37G/iwljXT96CQlapuWa0rQN14XZB4g8vAB/KC7x1nNI081c+sPqYYgNoVKGkKjSh5f LlFY8wceykVY51Sl6/ymDc/IzYLpLqvjP/IPye3WYbeSjWMO1cCdi727rPV+C0mIfxgX llcA== Received: by 10.180.99.99 with SMTP id ep3mr5694444wib.15.1348722186879; Wed, 26 Sep 2012 22:03:06 -0700 (PDT) Received: from [192.168.3.124] ([213.57.39.151]) by mx.google.com with ESMTPS id l6sm29250003wiz.4.2012.09.26.22.03.04 (version=SSLv3 cipher=OTHER); Wed, 26 Sep 2012 22:03:05 -0700 (PDT) Message-ID: <5063DE04.4020403@volo-net.com> Date: Thu, 27 Sep 2012 07:03:00 +0200 From: Issac Goldstand User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:15.0) Gecko/20120907 Thunderbird/15.0.1 MIME-Version: 1.0 To: ooo-dev@incubator.apache.org Subject: Re: Some stats and observations on OpenOffice upgrades References: In-Reply-To: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Gm-Message-State: ALoCoQnrsfVxaHdaJ07XrXU6b6dOuseW4hsWbNum7rdBOYPzEr5pZvLbCgWUcrzq+3F/pK4i3oRl X-Virus-Checked: Checked by ClamAV on apache.org In general, when dealing with web-analytics opened in a browser window, remember that there are a lot of users (often it's hard to believe how many!) who, rather than closing the tab, leave it open. With modern browsers opening all of the old tabs after re-opening the browser (browser upgrade, browser crash, reboot, or even the rare case of someone intentionally closing the browser and re-opening it), you get a lot of duplicates. For one-time events, make sure that you're only counting absolutely unique hits, which I believe you can get with google... For anything else, just read analytics with a grain of salt... All the best, Issac On 25/09/2012 21:06, Rob Weir wrote: > I've been looking at the upgrade numbers, the downloads that are > triggered from upgrade notifications in the OpenOffice client. > Although we are not tracking how many times such notifications pop up > in the OpenOffice client we do know from Google Analytics how many > users click the link to get more information on the update, and how > many of these users actually download the upgrade. > > The trends have been pretty steady, a slight peak when a release is > initially made, but a lingering steady state of upgrade requests even > several weeks later. > > For example, let's look at the status for a single day, last > Wednesday, Sept. 19th. > > On that date we had 164,752 total downloads of AOO. Of those > downloads, it looks like 54% of them come from upgrading users. The > remainder are either from new users, or existing users that went to > the website directly rather than from an upgrade notification. (No > easy way of distinguishing these two). > > The interesting thing is the breakdown by OpenOffice client version. > > For the upgrade installs on Sept 19th we see: > > 31% of upgrades were from AOO 3.4.0 > > 52% of upgrades were from OOo 3.3.0 > > 15% of upgrades were from OOo 3.2.1 > > 3% of upgrades were from OOo 3.2.0 > > Note the OOo 3.3.0 numbers. Nearly 4 months after AOO 3.4 was > released we are still getting large numbers of OOo 3.3.0 users > receiving and responding to upgrade notifications, nearly 20,000/day. > > I'm not sure how to explain this. Upgrade notifications should > surface once a week. > > Maybe: > > A) Some users are sporadically connected to the internet and the > upgrade check rarely is successful > > B) Some users ignore/defer the upgrade notifications until a later > time, in some cases months later > > C) Some user run OpenOffice rarely, sometimes at an interval of several months > > D) Someone, some web site, some organization, etc., is still > distributing OpenOffice.org 3.3.0 to users, and after they install > they get the AOO upgrade notification. > > If D), this is somewhat a concern, since users running OOo 3.3.0 are > exposed to several security flaws. > > > -Rob