I'm not sure it's really necessary to tell the reader what the reasons might be that they would want to download older releases. I think most readers who contemplate doing this would have their own reasons :-).
Nevertheless, I'm trying to think up reasons (not sure they're "very good" ones). One reason might be because some segment of the population downloading things aren't ready to move to Java 7. Or, a user might discover what they believe to be a bug, or some other issue (e.g. performance) in 2.7.0 and want to revert to 2.6.0, or at least try 2.6.0 to compare. ================= I'm guessing (but may be wrong) that another complaint about this page is that it looks disorganized and haphazard. Perhaps another way to reorganize this page so it doesn't appear so fragmented, is to change the "pivot" attribute - that is, for instance: Have the top-level box be a bunch of links to 2nd level boxes, one per super-artifact. (Super-artifact is the big thing we release, such as uimaFIT, Ruta, UIMA Java framework and SDK, UIMA-AS, DUCC, etc.). The 2nd level box would be, for that "super-artifact", a list of a few of the last releases. So for instance, there would be a box for UIMA Java framework and SDK, and inside that box would be entries for version 2.7.0, 2.6.0, (and maybe 2.5.0). We could add a column for linking to the JavaDocs (which are shown in a separate section at the moment). That way, the clutter on the page would be reduced, and people could easily see the current release, and perhaps a release or 2 back-level, if needed. As I said in my previous comment, I think this web-page design is separate from where the artifacts are actually sourced from, so at anytime we could stop using the Apache mirror system for these artifacts that are older releases. WDYT? -Marshall On 5/26/2015 4:19 PM, Richard Eckart de Castilho (JIRA) wrote: > [ > https://issues.apache.org/jira/browse/UIMA-4431?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14559790#comment-14559790 > ] > > Richard Eckart de Castilho commented on UIMA-4431: > -------------------------------------------------- > > I think unless there is a very good reason to prominently offer an old > release, we should not do it. Mind that the page explicitly says "Latest > Official Downloads" and not "Assortment of stuff that people might still be > using". > If we have a good reason, it should be clearly stated on the downloads page > what the reason is. > > What would be the reason for you still to offer 2.6.0 - it being the last > Java 5 release? > >> Clean up downloads page >> ----------------------- >> >> Key: UIMA-4431 >> URL: https://issues.apache.org/jira/browse/UIMA-4431 >> Project: UIMA >> Issue Type: Task >> Components: Website >> Reporter: Richard Eckart de Castilho >> Assignee: Richard Eckart de Castilho >> Priority: Minor >> Attachments: UIMA-4431.patch >> >> >> Btw, we are having stuff accumulating on the downloads page... imho >> it should only list the latest versions of our packages and for older >> versions only offer a generic reference to the Apache archive. >> I think the following changes should be made: >> - Remove DUCC 1.0.0 >> - Remove UIMA 2.6.0 >> - Factor UIMA-AS 2.6.0 out into a separate download section >> and mention that it is compatible with UIMA 2.7.0 >> (I guess that's what we tell people on the list, so it might >> as well be made official on the downloads page). >> - Remove Apache UIMA Version 2.5.0 >> - Remove Apache UIMA Version 2.4.2 >> - Remove Apache UIMA Version 2.4.0 > > > -- > This message was sent by Atlassian JIRA > (v6.3.4#6332) >
