Node.js just experienced build failures requiring a change to our scripts to adjust to the move of openssl-fips-2.0.9.tar.gz to old/fips/, see nodejs/node#13172 (comment)
Would it be possible to keep the .tar.gz files in a permanent directory structure, or in some other way arrange for them to have a permanent URI? Perhaps they could be organized by the top two numbers in the release stream to avoid so many files in one directory that its impossible to find the latest ones? The Web pages would still just point to the most recent, to make it easy for humans to find the latest with a browser.
Node has done this, see https://nodejs.org/dist/, and the stable URLs have enabled a set of thirdparty tools for downloading, building, installing, etc that automatically notice new releases, and don't require patching as archives are demoted from "current" to "old".
cf. nodejs/node#13219
Node.js just experienced build failures requiring a change to our scripts to adjust to the move of
openssl-fips-2.0.9.tar.gztoold/fips/, see nodejs/node#13172 (comment)Would it be possible to keep the .tar.gz files in a permanent directory structure, or in some other way arrange for them to have a permanent URI? Perhaps they could be organized by the top two numbers in the release stream to avoid so many files in one directory that its impossible to find the latest ones? The Web pages would still just point to the most recent, to make it easy for humans to find the latest with a browser.
Node has done this, see https://nodejs.org/dist/, and the stable URLs have enabled a set of thirdparty tools for downloading, building, installing, etc that automatically notice new releases, and don't require patching as archives are demoted from "current" to "old".
cf. nodejs/node#13219