[
https://issues.apache.org/jira/browse/DERBY-2428?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12479463
]
Jean T. Anderson commented on DERBY-2428:
-----------------------------------------
Below is a chat Jean and Andrew had on #derby. Relevant points (I think) are:
- All releases are automatically copied to the archives; we just need to update
the web pages pointing to them.
- Everything but the current release is a candidate for being pointed at the
archives.
- Download pages can be updated one by one (no need to do all in one blast).
- Andrew identified these steps for updating a download page:
1) remove the mirror selection section and form from the HTML page,
2) replace [preferred] with http://archive.apache.org/, and
3) then make the derby_downloads page link directly to the HTML and not the
cgi.
4) And then remove the cgi script for that release.
Also, once the dowload page for a release has been updated, we need to
physically remove the release from /www/www.apache.org/dist/db/derby on
people.a.o.
Below is the complete chat:
samcintyre jta: now that I think about it, 10.2.1.6 should probably be archived
as well. There's no reason anyone should download 10.2.1.6 instead of 10.2.2.0.
jta sure -- why not archive everything previous to the most current release?
jta dumb question: are archives mirrored?
jta more the question is: how big is the update to the download pages for the
older releases?
samcintyre jta: seems like a good idea to keep the most recent release per
active branch.
samcintyre hmm.
jta that sounds fine -- just moving the oldest to the archives would help free
space
samcintyre Except can't really call the 10.1 branch active, since we can't
release from it without overhauling all the license headers, and I don't think
there'd be much interest in doing that.
jta :-)
samcintyre Anyway, keeping latest on branch for current_branch +
(current_branch - 1) seems like a good policy.
samcintyre 10.2.1.6 itself is almost a hundred megs.
samcintyre keeping just 10.1.3.1 and 10.2.0.0 would drop derby's disk usage
from 380M to 175M
samcintyre (meant 10.2.2.0 there)
jta any reason to keep 10.1.3.1 on the mirrors? if it's available from the
archives?
samcintyre oh, as for your other question: "are archives mirrored?"
samcintyre no, it's more like the mirrors are archived. Anything put into
/www/www.apache.org/dist is automatically copied to /www/archive.apache.org/dist
jta that would be an issue if there were vast downloads for a release in the
archives, but that seems unlikely for a 10.1 release
samcintyre nah, i guess not, people mostly just want the latest, i would
assume.jta I'd expect the highest download hits against the latest
jta maybe an occasional hit against the archives. if a problem came up and we
anticipated lots of downloads for a prior release, we could always move it back
to the mirrors, right?
samcintyre true
samcintyre so the changes would be pretty straightforward, though there are
several: remove the mirror selection section and form from the HTML page,
replace [preferred] with http://archive.apache.org/, and then make the
derby_downloads page link directly to the HTML and not the cgi. And then remove
the cgi script for that release.
jta at least it could be reviewed before being published. :-)
jta There's some work, which won't be instantaneous. want me to open a jira
issue?
samcintyre yes, please. that'll give others an opportunity to pick it up.
jta sounds good
samcintyre (not much time to do it today, probably wouldn't get to it until
late next week if it were left up to me)
jta and they don't have to be moved all at once
samcintyre although, i'd have time to review if somebody posted a patch.
samcintyre true
jta I opened DERBY-2428, I'll attach our IRC chat to a comment
> Move older releases from www.apache.org/dist/ to archive.apache.org/dist
> ------------------------------------------------------------------------
>
> Key: DERBY-2428
> URL: https://issues.apache.org/jira/browse/DERBY-2428
> Project: Derby
> Issue Type: Task
> Components: Web Site
> Affects Versions: 10.1.1.0, 10.1.2.1, 10.1.3.1
> Reporter: Jean T. Anderson
>
> Derby releases are consuming much space on the Apache mirrors. It's time to
> move older releases to the archives.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
