[
https://issues.jboss.org/browse/JBIDE-15335?page=com.atlassian.jira.plugi...
]
Nick Boldt edited comment on JBIDE-15335 at 8/13/13 10:58 AM:
--------------------------------------------------------------
OK, I'll allow that the zips are useful for archiving old releases.
The purpose of this JIRA is to look at ways to simplify and streamline what we offer,
based on *what our users actually use*. Sure, a _few people_ download the zips for offline
install, but look at the frequency of those compared to those that use the online update
sites.
Consider too that to use the zip you need to be online because not all the deps are
included in the zip, unless you *ALSO download the 766M target platform zip*.
-----
Do we still need the Hibernate Tools zip [1], given that its content is ALSO provided in
the site AND the site zip, and therefore is installable 3 other ways:
* Marketplace from
http://download.jboss.org/jbosstools/updates/stable/kepler/
* JBT update site from
http://download.jboss.org/jbosstools/updates/stable/kepler/
* JBT update site zip from
http://sourceforge.net/projects/jboss/files/JBossTools/JBossTools4.1.x/jb...
[1]
http://sourceforge.net/projects/jboss/files/JBossTools/JBossTools4.1.x/hi...
I would argue no, since for JBT 4.0, it's only gotten 900 downloads in 4 months,
compared to 39,134 installs from Eclipse Marketplace in the same period. That's
{color:red}*43x*{color} as many!
was (Author: nickboldt):
OK, I'll allow that the zips are useful for archiving old releases.
The purpose of this JIRA is to look at ways to simplify and streamline what we offer,
based on *what our users actually use*. Sure, a _few people_ download the zips for offline
install, but look at the frequency of those compared to those that use the online update
sites.
Consider too that to use the zip you need to be online because not all the deps are
included in the zip, unless you *ALSO download the 766M target platform zip*.
-----
Do we still need the Hibernate Tools zip [1], given that its content is ALSO provided in
the site AND the site zip, and therefore is installable 3 other ways:
* Marketplace from
http://download.jboss.org/jbosstools/updates/stable/kepler/
* JBT update site from
http://download.jboss.org/jbosstools/updates/stable/kepler/
* JBT update site zip from
http://sourceforge.net/projects/jboss/files/JBossTools/JBossTools4.1.x/jb...
[1]
http://sourceforge.net/projects/jboss/files/JBossTools/JBossTools4.1.x/hi...
I would argue no, since for JBT 4.0, it's only gotten 900 downloads in 4 months,
compared to 39,134 installs from Eclipse Marketplace in the same period. That's
{color:red}*43x{color}* as many!
Consider removing update site zips from
jboss.org/tools
-------------------------------------------------------
Key: JBIDE-15335
URL:
https://issues.jboss.org/browse/JBIDE-15335
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: updatesite
Affects Versions: 4.0.1.Final, 4.1.0.Final
Reporter: Nick Boldt
Assignee: Max Rydahl Andersen
Based on anecdotal evidence, it would appear that JBT 4.x is downloaded MANY MORE TIMES
from Eclipse Marketplace than from
jboss.org/tools:
As of 2013-08-12 12:48pm:
* Download stats from
http://jboss.org/tools/download/stable/4_1 : 378 + 140 = *518
installs* (could be more if the zip's passed around w/in an org?)
* Install stats for JBT 4.1.0 from Eclipse Marketplace for 2013/08: *3,678 installs*
({color:red}*7.1x*{color} as many)
* Download stats from
http://jboss.org/tools/download/stable/4_0 : 2441 + 899 = *3,340
installs* (could be more if the zip's passed around w/in an org?)
* Install stats for JBT 4.0.1 from Eclipse Marketplace for 2013/04 - 2013/08: 11280 +
10421 + 9552 + 6246 + 1635 = *39,134 installs* ({color:red}*11.7x*{color} as many)
So, is it time to stop providing a zip of the JBT update site? Seems like very few users
want JBT delivered via zip.
Note too that the stats collected above include a partial month (August 2013) during
which many people are on vacation. To get a real sense of the download rates we ought to
check these numbers again in September and October.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:
http://www.atlassian.com/software/jira