On 1/31/16 6:30 PM, Bryan Pendleton wrote:
The mirrored (most current) releases always have two files governing
them:
1) An html file which you DON'T click on.
2) A cgi file. That's what you DO click on.
Thanks, Rick, this makes sense.
And thanks very much for cleaning up the issues that Infra found and
logged.
I think that I got myself confused because this page:
http://db.apache.org/derby/releases/
shows both the html and the cgi, and it isn't obvious which to click on.
Ha! I've never visited that page. Do we link to that page from somewhere
on our website? I always navigate to releases from
http://db.apache.org/derby/derby_downloads.html.
Infrastructure suggested that we put an "index.html" into this
directory, which would list ONLY the files that we are supposed
to click on, NOT the files that we DON'T click on.
It seems to me that the (small) downside is that if we had an index.html
in this directory, then each time we make a new release, we'd have to
update our index.html.
We'd put that in our release checklist.
What do you think?
Either that or remove any website references to that directory. Any
reason why we should support navigating to that directory directly
rather than coming in through the official download page?
An extra step in the release process isn't a deal killer, particularly
if we could find a way to automate this step. Over the last 10 years
we've gradually paired down the number of manual interventions (aka
places where the release manager could mess up).
Thanks,
-Rick
thanks,
bryan
