Closed
Bug 406302
Opened 18 years ago
Closed 18 years ago
Add Lightning 0.3.1, 0.5 and 0.7 releases to bouncer
Categories
(Release Engineering :: General, defect, P3)
Release Engineering
General
Tracking
(Not tracked)
RESOLVED
WONTFIX
People
(Reporter: sipaq, Unassigned)
Details
I'd like the following builds added to bouncer as this will help in tracking our download metrics.
Here are the links:
0.3.1:
http://releases.mozilla.org/pub/mozilla.org/calendar/lightning/releases/0.3.1/lightning-0.3.1.linux-i686.xpi
http://releases.mozilla.org/pub/mozilla.org/calendar/lightning/releases/0.3.1/lightning-0.3.1.mac.xpi
http://releases.mozilla.org/pub/mozilla.org/calendar/lightning/releases/0.3.1/lightning-0.3.1.win32.xpi
0.5:
http://releases.mozilla.org/pub/mozilla.org/calendar/lightning/releases/0.5/lightning-0.5.linux-i686.xpi
http://releases.mozilla.org/pub/mozilla.org/calendar/lightning/releases/0.5/lightning-0.5.mac.xpi
http://releases.mozilla.org/pub/mozilla.org/calendar/lightning/releases/0.5/lightning-0.5.win32.xpi
0.7:
http://releases.mozilla.org/pub/mozilla.org/calendar/lightning/releases/0.7/lightning-0.7.linux-i686.xpi
http://releases.mozilla.org/pub/mozilla.org/calendar/lightning/releases/0.7/lightning-0.7.mac.xpi
http://releases.mozilla.org/pub/mozilla.org/calendar/lightning/releases/0.7/lightning-0.7.win32.xpi
Comment 1•18 years ago
|
||
Not sure I understand how this will help you, particularly for the older releases. In general we're trying to trim old releases out of bouncer, as it makes the mirror checks take longer. Can you provide more explanation ?
Also, I see you currently link to AMO. Does that provide download and active user stats ?
Priority: -- → P3
| Reporter | ||
Comment 2•18 years ago
|
||
(In reply to comment #1)
> Not sure I understand how this will help you, particularly for the older
> releases. In general we're trying to trim old releases out of bouncer, as
> it makes the mirror checks take longer. Can you provide more explanation?
We currently have bouncer statistics for Lightning 0.1 and 0.3. Those account
for over 300,000 downloads in total. We would of course be interested in
knowing the numbers for 0.3.1, 0.5 and 0.7 as well.
> Also, I see you currently link to AMO. Does that provide download and active
> user stats ?
It provides basic download stats. However, we believe that at least a few
percent of our user base are still downloading directly from ftp.m.o. Therefore
AMO alone is likely giving us an incomplete picture. Hence the bug report.
Comment 3•18 years ago
|
||
(In reply to comment #2)
> We currently have bouncer statistics for Lightning 0.1 and 0.3. Those account
> for over 300,000 downloads in total. We would of course be interested in
> knowing the numbers for 0.3.1, 0.5 and 0.7 as well.
Hmm, I'm still confused. Bouncer increments a simple counter for each request it receives for a product. So if we put those three later releases in, and you switched your website links to point to download.m.o, then you'd find out who was downloading it from your website now, rather than any historical information.
So, if a product isn't in bouncer when you ship it, then the boat has sailed on getting useful data later. You only monitor the much lower level of downloads after the release.
> > Also, I see you currently link to AMO. Does that provide download and active
> > user stats ?
>
> It provides basic download stats. However, we believe that at least a few
> percent of our user base are still downloading directly from ftp.m.o. Therefore
> AMO alone is likely giving us an incomplete picture. Hence the bug report.
Direct d/l's from ftp.m.o aren't logged by bouncer either. I think the coming improvements to AMO (mockups at http://people.mozilla.com/~jscott/devcp/latest/) are really the answer for extensions, because it gives you both d/l and active user data with historical trends.
| Reporter | ||
Comment 4•18 years ago
|
||
-> WONTFIX per discussion with cf.
Status: NEW → RESOLVED
Closed: 18 years ago
Resolution: --- → WONTFIX
| Assignee | ||
Updated•13 years ago
|
Product: mozilla.org → Release Engineering
You need to log in
before you can comment on or make changes to this bug.
Description
•