On Sat, 10 Feb 2018 11:52:24 +0000, sebb wrote:
The 3rd party mirrors all offer their services for free.
Although storage is cheap these days, it is not free, so we should
not
burden the mirrors with unnecessary files (*).
So would RMs please remember to remove old releases once a new
release
has been announced.
And when preparing for a new release, please check if the existing
download page still carries any obsolete releases. [It is OK to link
to older release on the archive server]
What are the criteria for "old", "obsolete", "unnecessary"?
In CM for example, we used to add links to the "apidocs" of
previous releases, even though the consensus was that they
were not supported.
If there is a well-defined requirement, can the actions be
automated? [Check for obsolete files, send a warning/reminder
to the ML, move them to the appropriate location.]
Regards,
Gilles
Thanks!
(*) I know Commons packages are generally small, but there are a lot
of them.
Also each file generates network traffic (e.g. to check if it is
up-to-date).
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org
