I agree that the oorexx.org/download.html page has gotten a little
long, but it would be quite manageable if it reflected only the latest
version of ooRexx. I'd put the older versions on a separate page and
link to that from the main download page.
I don't think I'm alone in finding Sourceforg
> 1. Listing the individual files for download is error prone
>at best. A simple typo can make the link useless.
Any page like that is best automated .. part of release/publish process.
Shouldn't be any need for manual update.
> 2. Listing details for the old releases is not very useful.
I've seen some sites where just the current release is listed, an at the bottom
is a link to an "older releases" page. People usually want the current
release, unless they have a very specific reason to get something else.
Bruce
On Mar 11, 2014, at 8:37 AM, David Ashley wrote:
> All -
>
> The
Hi David,
My view, which is not in favor with others, is that we should just point
people to the files page on SourceForge. So whatever you want to do is
fine with me.
I don't see much point in listing all the previous versions. I would
suggest just giving this URL:
https://sourceforge.net/pro
Greetings David,
David Ashley wrote:
> So I suggest we only list each version as a link to the SourceForge
> repository
Seems reasonable to me. Yes, there are significant custom flavors of ooRexx...
if the SF site is down, one is unable to download anything at the specific
time. One link per ma
All -
The download page on the main ooRexx web site is getting a little too
crowded with the old releases. I was about to update it with the new
4.2.0 release when I changed my mind and decided it was time to do
something else with this page.
First, I have some observations.
1. Listing the indiv
