Subject: [cross-project-issues-dev] p2 download stats ... again
Hi
all,
just a couple of
things that I learned enabling my download stats - for more details
see
1. It is better to
tie stats to a FEATURE rarther than a bundle. Because bundles
come
in 2 variants (.pack.gz / .jar) so with a bundle you have duplicate work adding
the
stats tracker (and, the app from bug 310132 which auto-generates stats
properties
doesn't support it).
1a) Note though that
a commercial product which uses a different feature
structure than Eclipse Open Source (and so just gets your bundle)
won't
be counted when you count feature access. That's likely not
relevant.
2. If you have a
feature and bundle with the same ID, don't add the
p2.downloadStats
property to both. Since it would count each download
twice.
3. It may be
adviseable to version your stats ID somehow. For instance,
use
"org.eclipse.rse.core_tm320" or "org.eclipse.wst.ui_helios_sr0"
or
"org.eclipse.ptp_4.0". If you dont' version the stats ID you are
tracking,
you may run into troubles when we do Helios SR1 which will re-use
the
same repo location (/releases/helios).
4. Maybe obvious.
the stats tracker will not catch people updating from Galileo
to
Helios. Because the Galileo p2 impl did not have the stats code enabled.
You'll
only count p2 downloads that happen with Eclipse 3.6.
5. I'm wondering whether the helios aggregator's
access to my project
repository already counts as a download? Probably not too
relevant
after all.
So... if I just
confused hell out of you, best forget what I just wrote. In
the
end, as has been
stated before, download stats are only good for trends
and not for absolute
numbers anyways. So it's not worth putting too much
effort
in.
I'd hope though that
some of you found this helpful :)
Thanks,
--
Martin Oberhuber, Senior Member of Technical
Staff, Wind River
direct
+43.662.457915.85 fax +43.662.457915.6
