Every time we release we need to generate quite a few files related to the release.
Here's the list I know of: 1) The ASC/SHA/MD5 hashes and signature files, one for every released file 2) A CWiki page listing all the built files with hyperlinks to hashes, etc. https://cwiki.apache.org/confluence/display/OOOUSERS/Development+Snapshot+Builds#DevelopmentSnapshotBuilds-AOOSnapshot This is used when voting on a Release Candidate. 3) release_matrix.js, used by the download page's logic to decide what file to recommend based on user's locale: http://www.openoffice.org/download/release_matrix.js 4) The other.html page that has a table listing all release files: http://www.openoffice.org/download/other.html 5) Another download page, on openoffice.apache.org, listing the source and SDK links, along with hashes: https://openoffice.apache.org/downloads.html 6) A flat list of all download URLs, used by the download stats script: http://svn.apache.org/repos/asf/openoffice/devtools/aoo-stats/401.lst 7) The XML files used by the upgrade notification server, one XML file per release: https://svn.apache.org/repos/asf/openoffice/ooo-site/trunk/content/projects/update38/ProductUpdateService/check.Update I imagine this list will grow over time. Certainly new releases and new translations cause us to update these files. And to the extent they are manually created they will contain errors. Even if created by automation, if we don't have a canonical data set that we're all working from there is the opportunity for error. So the big question: What can we do to improve on this? 1) Can we have a single, published, canonical, machine-readable description of what is contained in a release, or even what is contained in each build: a) base URL of where the files live b) based URL to where the hashes and signatures live c) list of all language codes and platforms included in the build d) defined rules for creating the full paths and file names given this information. 2) Have such a data file for every past release, at least back to 3.4.0. 3) Write scripts to generate our other files from these canonical files. 4) Check this all in to a central place so when a new release comes out we can generate these needed files automatically, with much lower chance for errors. 5) Spend our extra time drinking beer and imagining how rich we'd all be if we each received $0.01 for every download of AOO. How close are we to this? Is any part of this automated already today? Regards, -Rob --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
